# Usero (remote · usero.io)

Read your Usero feedback inbox and clusters, file feedback, build forms, and open an AI PR.

- Trust score: 77/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `usero.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-usero-usero/usero.md), [page](https://verifymcp.io/servers/io-usero-usero/usero)

## Channel facts

- Endpoint: `https://usero.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.3.0`

## 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-09-20.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 835 tokens (~417/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Usero MCP server?

Usero is a hosted endpoint at https://usero.io/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 io-usero-usero 'https://usero.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usero-usero": {
      "url": "https://usero.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usero-usero": {
      "type": "http",
      "url": "https://usero.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usero-usero]
url = "https://usero.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-usero-usero --url 'https://usero.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usero-usero:
    url: "https://usero.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usero-usero": {
      "Transport": "http",
      "Url": "https://usero.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usero-usero -t streamable-http -u 'https://usero.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usero-usero": {
      "type": "http",
      "url": "https://usero.io/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-09-20 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 360 → 417
- [functional] Server version: 1.15.0 → 1.20.0

### 2026-09-19 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.13.0 → 1.15.0

### 2026-09-18 (score 77, +1)

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

### 2026-09-15 (score 76, +1)

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

### 2026-09-13 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.11.0 → 1.13.0

### 2026-09-12 (score 75, +1)

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

### 2026-09-10 (score 74, +3)

- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_signup” rewrote its description, which is the text the model reads
- [security] Tool “start_signup” rewrote its description, which is the text the model reads
- [functional] Server version: 1.10.0 → 1.11.0

### 2026-09-09 (score 71, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_signup” rewrote its description, which is the text the model reads
- [security] Tool “start_signup” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 395 → 295
- [functional] Server version: 1.8.0 → 1.10.0

## MCP tools (2)

### `start_signup` (~168 tokens)

Start signup without leaving the agent. Ask for the user's email, do not invent one. Sends an email with a Review connection button; the user presses that button, then "Yes, connect" on the page that opens (opening the page alone does nothing). That lets check_signup return an API key for this MCP client. Returns a pollToken for check_signup. No key is shown in the browser. 5 per email per hour; the link expires in 15 minutes.

Input parameters:

- `clientName` (string): The agent client you are running in, e.g. "Claude Code", "Cursor", "Windsurf". Shown in the email and used as the API key name.
- `email` (string, required): The user's email address. Ask for it if you do not have it.

### `check_signup` (~132 tokens)

Poll after start_signup. Returns { status: "pending" } until the user presses the button in the email, then { status: "ready", apiKey, setup } exactly once; the pollToken is dead after that. The setup field holds the exact config or command for this client plus what to tell the user (restart, or remove-and-re-add on Desktop). Poll every 5 seconds for up to 15 minutes without ending your turn. On ready, apply the setup snippet at once, then call create_client for the product.

Input parameters:

- `pollToken` (string, required): The pollToken returned by start_signup.

## Diagnostics

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

## Score history

- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 77
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 71
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 70

## Common questions

### What is the Usero MCP server?

Usero is an MCP server listed in the public MCP registry as io.usero/usero. Read your Usero feedback inbox and clusters, file feedback, build forms, and open an AI PR. This page covers its hosted endpoint (https://usero.io/mcp).

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

Usero scores 77 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 Usero MCP server expose?

Usero exposes 2 tools: start_signup, check_signup. Their descriptions and schemas cost roughly 300 tokens of context every time the server is loaded.

### Does the Usero MCP server require authentication?

Yes. Usero 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 Usero MCP server still maintained?

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

## Links

- Remote endpoint: https://usero.io/mcp
- Authorisation metadata: https://usero.io/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/usero-feedback/claude-plugin
- Website: https://usero.io/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usero-usero/usero.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usero-usero/usero.json
- HTML version of this page: https://verifymcp.io/servers/io-usero-usero/usero