mcp-registry/com.featq/featq · registry v1.0.1 · server reports v0.1.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 19:25 UTC, the FeatQ MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 3 minutes.
Feature-request board for software teams: users vote, your coding agent pulls top requests over MCP
Point your MCP client at this streamable-http endpoint: https://featq.com/api/mcp
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
10 parameter(s) across 6 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.featq%2Ffeatq/fixes
{
"name": "get_board_stats",
"description": "Get request counts, vote totals, and top requests for the connected FeatQ board.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get board stats"
}{
"name": "get_ranked_requests",
"description": "Get the top feature requests by demand score, excluding requests already marked done. Requests are ranked by demand: each vote counts as one point and each comment as half a point, with scores gradually decaying as a request ages (90-day scale) so recent demand ranks higher, and ties going to the newer request.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"default": 5,
"maximum": 20,
"minimum": 1
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get ranked feature requests"
}{
"name": "get_request",
"description": "Get one feature request with its comments for the connected FeatQ board.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get feature request"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.featq/featq"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.featq/featq"}) over MCP.
get_ranked_requests ~154 tokenslist_requests ~123 tokenslist_competitor_claims ~120 tokensupdate_request_status ~120 tokensgenerate_spec ~84 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fcom.featq%2Ffeatq?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.featq%2Ffeatq?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.featq%2Ffeatq.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ab2bbc0dedaf2269…, first seen 2026-10-21, included at leaf 36370 of 384,974. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable data servers · most reliable research servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 19:25 UTC, the FeatQ MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 3 minutes.
FeatQ MCP server advertises 7 tools, including generate_spec, get_board_stats, get_ranked_requests, get_request, list_competitor_claims.
Point your MCP client at this streamable-http endpoint: https://featq.com/api/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.