FeatQ MCP server
com.featq/featqfeatq.comstreamable-httpv1.0.1Scanned
Feature-request board for software teams: users vote, your coding agent pulls top requests over MCP
7 tools: 2 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the FeatQ MCP server can do
The FeatQ MCP server is published by featq.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: generate_spec and update_request_status), but cannot delete data. 5 tools only read.
1 tool brings in text other people can write (get_request).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 2Claude Code: ask
generate_specGenerate an agent-ready markdown implementation spec for one feature request.No findings
Why it is in this group
- The name "generate_spec" says "generate": a word for a change.
Description, as the server wrote it Generate an agent-ready markdown implementation spec for one feature request.
update_request_statusUpdate the status of a feature request.No findings
Why it is in this group
- The name "update_request_status" says "update": a word for a change.
Description, as the server wrote it Update the status of a feature request. Marking a request done makes it appear in the public changelog.
Only reads 5Show 5 read-only tools
get_board_statsGet request counts, vote totals, and top requests for the connected FeatQ board.No findings
Why it is in this group
- The name "get_board_stats" says "get": a word for reading.
Description, as the server wrote it Get request counts, vote totals, and top requests for the connected FeatQ board.
get_ranked_requestsGet the top feature requests by demand score, excluding requests already marked done.No findings
Why it is in this group
- The name "get_ranked_requests" says "get": a word for reading.
Description, as the server wrote it 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.
get_requestGet one feature request with its comments for the connected FeatQ board.Reads text others writeNo findings
Why it is in this group
- The name "get_request" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "comment": it reads comments, which other people can write.
Description, as the server wrote it Get one feature request with its comments for the connected FeatQ board.
list_competitor_claimsList what watched competitor comparison pages say about this product.No findings
Why it is in this group
- The name "list_competitor_claims" says "list": a word for reading.
Description, as the server wrote it List what watched competitor comparison pages say about this product. Read only. Claims are signals, not votes.
list_requestsList feature requests for the connected FeatQ board.No findings
Why it is in this group
- The name "list_requests" says "list": a word for reading.
Description, as the server wrote it List feature requests for the connected FeatQ board.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://featq.com/api/mcp: tools/list returned 7 tools to an anonymous client, including generate_spec (write), update_request_status (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http featq https://featq.com/api/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http featq https://featq.com/api/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__featq__list_requests",
"mcp__featq__get_request",
"mcp__featq__get_board_stats",
"mcp__featq__get_ranked_requests",
"mcp__featq__list_competitor_claims"
],
"ask": [
"mcp__featq__generate_spec",
"mcp__featq__update_request_status"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as featq. Review it before you use it.
Capability tags behind 1 rule
- mcp__featq__get_request untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.featq/featq/verify?hash=639977d2d5069e0d31591db7302925f673b33c7cf9ec34a508cc0846493dd9b7" | jq -e '.changed == false'Pinned hash 639977d2d506, from Nov 13, 2026, 05:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.featq/featq/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.featq/featq)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
FeatQ MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the FeatQ MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the FeatQ MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the FeatQ MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the FeatQ MCP server have?
- 7 tools: 2 write, 5 read. generate_spec, update_request_status, list_requests, get_request, get_board_stats, get_ranked_requests and list_competitor_claims.
Does the FeatQ MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the FeatQ MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the FeatQ MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.