Skip to content

Usero MCP server

io.usero/userousero.iostreamable-httpv1.28.1Scanned

Your user feedback in your agent: read the inbox, build forms, file issues, open an AI PR.

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Sign-in required, OAuth metadata published. 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.
Govern this server →

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 Usero MCP server can do

The Usero MCP server is published by usero.io, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: start_signup and check_signup), but cannot delete data. None of its tools only reads.

1 tool brings in text other people can write (start_signup).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Oct 21, 2026, version 1.28.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.

2 tools

Changes things 2Claude Code: ask
  • check_signupPoll after start_signup.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check Signup Status
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • start_signupStart signup without leaving the agent.Reads text others writeNo findings

    Why it is in this group

    • The name "start_signup" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Start Signup
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true

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.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 19:14 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://usero.io/.well-known/oauth-protected-resource/mcp/oauth
RFC 9728 protected resource metadata
https://usero.io/.well-known/oauth-protected-resource/mcp/oauth
Authorization servers
https://usero.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 13, 2026
    • resource_metadata in WWW-Authenticate: https://usero.io/.well-known/oauth-protected-resource to https://usero.io/.well-known/oauth-protected-resource/mcp/oauth
    • RFC 9728 protected resource metadata: https://usero.io/.well-known/oauth-protected-resource to https://usero.io/.well-known/oauth-protected-resource/mcp/oauth
  2. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://usero.io/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://usero.io/.well-known/oauth-protected-resource/mcp to https://usero.io/.well-known/oauth-protected-resource

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.

  1. PostureRemote posture changed. resource_metadata in WWW-Authenticate: https://usero.io/.well-known/oauth-protected-resource -> https://usero.io/.well-known/oauth-protected-resource/mcp/oauth; RFC 9728 protected resource metadata: https://usero.io/…View diff
    • resource_metadata in WWW-Authenticate: https://usero.io/.well-known/oauth-protected-resource to https://usero.io/.well-known/oauth-protected-resource/mcp/oauth
    • RFC 9728 protected resource metadata: https://usero.io/.well-known/oauth-protected-resource to https://usero.io/.well-known/oauth-protected-resource/mcp/oauth
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 4 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://usero.io/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://usero.io/.well-known/oauth-protected-resource/mcp to https://usero.io/.well-known/oauth-protected-resource

Install

Pinned to version 1.28.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http usero https://usero.io/mcp/oauth
claude mcp add --transport http usero https://usero.io/mcp/oauth

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.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__usero__start_signup",
      "mcp__usero__check_signup"
    ],
    "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 usero. Review it before you use it.

Capability tags behind 1 rule
  • mcp__usero__start_signup 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/io.usero/usero/verify?hash=be3d62e6e1063ed68e6d4a4bcb444d12d7581145087cb6dbcff2bbdda79a125b" | jq -e '.changed == false'

Pinned hash be3d62e6e106, from Oct 21, 2026, 19:14 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usero/usero/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usero/usero
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usero/usero.svg)](https://radar.anlyon.com/servers/io.usero/usero)

Source: MCP Registry · repository. Synced Nov 10, 2026, 01:17 UTC.

Usero MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Usero MCP server safe?

No scan can promise that. What its definitions show: 2 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 Usero MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Usero 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 Usero MCP server have?

2 tools: 2 write. start_signup and check_signup.

Does the Usero MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Usero MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Usero MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.