Usero
REMOTE · USERO.IO · 2 COMPONENTS
Your user feedback in your agent: read the inbox, build forms, file issues, open an AI PR.
Available components
Last scanned (1 hour ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Project Management
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1066 tokens (~533/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 0
- Server version: 1.32.0 → 1.33.0 functional
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.30.0 → 1.32.0 functional
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.28.0 → 1.30.0 functional
- 19 Oct 26 0
- Server version: 1.26.1 → 1.28.0 functional
- 15 Oct 26 0
- Server version: 1.26.0 → 1.26.1 functional
- 14 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.25.0 → 1.26.0 functional
- 13 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.24.0 → 1.25.0 functional
- 12 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.23.2 → 1.24.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://usero.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usero.io | CN=WE1,O=Google Trust Services,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e72df9365c109bb90eea949561bb7007 |
| SANs: usero.io, tracker.usero.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of usero.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usero.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://usero.io/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://usero.io/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://usero.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://usero.io/mcp |
| Authorisation server | https://usero.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://usero.io/mcp | Verified | 200 | |
| http (plaintext) | http://usero.io/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_signup Check Signup Status ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pollToken | string | yes | The pollToken returned by start_signup. |
No output schema declared.
No examples provided.
start_signup Start Signup ~187
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 types the userCode this tool returns and presses "Yes, connect" on the page that opens (opening the page alone does nothing). Show the user the userCode exactly as returned. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| string | yes | The user's email address. Ask for it if you do not have it. |
No output schema declared.
No examples provided.
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.
remote · usero.io
claude mcp add --transport http io-usero-usero 'https://usero.io/mcp'
What is the Usero MCP server?
Usero is an MCP server listed in the public MCP registry as io.usero/usero. Your user feedback in your agent: read the inbox, build forms, file issues, open an AI PR. This page covers its hosted endpoint (https://usero.io/mcp).
Is the Usero MCP server safe to use?
Usero scores 84 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 319 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.