# FeatQ (remote · featq.com)

Feature-request board for software teams: users vote, your coding agent pulls top requests over MCP

- Trust score: 85/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `featq.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-featq-featq/api-mcp.md), [page](https://verifymcp.io/servers/com-featq-featq/api-mcp)

## Channel facts

- Endpoint: `https://featq.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 296 tokens (~42/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the FeatQ MCP server?

FeatQ is a hosted endpoint at https://featq.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-featq-featq 'https://featq.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-featq-featq": {
      "url": "https://featq.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-featq-featq": {
      "type": "http",
      "url": "https://featq.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-featq-featq]
url = "https://featq.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-featq-featq": {
      "type": "remote",
      "url": "https://featq.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-featq-featq --url 'https://featq.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-featq-featq:
    url: "https://featq.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-featq-featq": {
      "Transport": "http",
      "Url": "https://featq.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-featq-featq -t streamable-http -u 'https://featq.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-featq-featq": {
      "type": "http",
      "url": "https://featq.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 85, 0)

- [security] Stability: 0.97 → pass

### 2026-11-18 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 79, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (7)

### `list_requests` (~40 tokens)

List feature requests

List feature requests for the connected FeatQ board.

Input parameters:

- `limit` (integer)
- `sort` (string)
- `status` (string)

### `get_request` (~30 tokens)

Get feature request

Get one feature request with its comments for the connected FeatQ board.

Input parameters:

- `id` (string, required)

### `get_board_stats` (~27 tokens)

Get board stats

Get request counts, vote totals, and top requests for the connected FeatQ board.

### `get_ranked_requests` (~80 tokens)

Get ranked feature requests

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.

Input parameters:

- `limit` (integer)

### `generate_spec` (~27 tokens)

Generate implementation spec

Generate an agent-ready markdown implementation spec for one feature request.

Input parameters:

- `id` (string, required)

### `update_request_status` (~45 tokens)

Update request status

Update the status of a feature request. Marking a request done makes it appear in the public changelog.

Input parameters:

- `id` (string, required)
- `status` (string, required)

### `list_competitor_claims` (~47 tokens)

List competitor claims

List what watched competitor comparison pages say about this product. Read only. Claims are signals, not votes.

Input parameters:

- `limit` (integer)
- `state` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-featq-featq/api-mcp#diagnostics

## Score history

- 2026-11-21: 85
- 2026-11-20: 85
- 2026-11-19: 85
- 2026-11-18: 85
- 2026-11-17: 84
- 2026-11-16: 84
- 2026-11-15: 83
- 2026-11-14: 83
- 2026-11-13: 82
- 2026-11-12: 82
- 2026-11-11: 81
- 2026-11-10: 81
- 2026-11-09: 81
- 2026-11-08: 80
- 2026-11-07: 80
- 2026-11-06: 79
- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 23
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 74
- 2026-10-24: 73
- 2026-10-23: 73

## Common questions

### What is the FeatQ MCP server?

FeatQ is an MCP server listed in the public MCP registry as com.featq/featq. Feature-request board for software teams: users vote, your coding agent pulls top requests over MCP. This page covers its hosted endpoint (https://featq.com/api/mcp).

### Is the FeatQ MCP server safe to use?

FeatQ scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the FeatQ MCP server expose?

FeatQ exposes 7 tools: list_requests, get_request, get_board_stats, get_ranked_requests, generate_spec, and 2 more. Their descriptions and schemas cost roughly 296 tokens of context every time the server is loaded.

### Does the FeatQ MCP server require authentication?

Yes. FeatQ asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the FeatQ MCP server still maintained?

FeatQ is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the FeatQ MCP server?

VerifyMCP ran 13 checks on FeatQ, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://featq.com/api/mcp
- Authorisation metadata: https://featq.com/.well-known/oauth-protected-resource/api/mcp
- Website: https://featq.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-featq-featq/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-featq-featq/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-featq-featq/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-featq-featq/api-mcp
