Yo MCP server
io.github.alfongj-com/yoalfongj-comstreamable-httpv1.0.1Scanned
Let agents send content-free push notifications to a paired phone via MCP.
5 tools: 2 can delete or cancel things, 1 do something that can't be undone and 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 1 does something that can't be undone. 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 Yo MCP server can do
The Yo MCP server is published by the GitHub account alfongj-com. It has 5 tools. It can delete or cancel things (2 tools: cancel_registration and revoke_self), do things that cannot be undone, such as sending, paying or publishing (yo) and create or change data (2 tools: register_agent and check_registration). None of its tools only reads.
1 tool can send data out of your system (yo).
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 16, 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.
5 tools
Deletes or cancels 2Claude Code: deny
cancel_registrationAbort a pairing you started with register_agent.No findings
Why it is in this group
- The name "cancel_registration" says "cancel": a word for removing or ending something.
Description, as the server wrote it Abort a pairing you started with register_agent. Works while pending and after approval: an already-approved connection is revoked (the API key stops working) so a pairing approved by the wrong account can be undone. Available until the pairing expires, and for 15 minutes after you pick up the API key; later than that, use revoke_self. Then call register_agent again.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
revoke_selfPermanently revoke THIS agent using its API key as the Bearer token.No findings
Why it is in this group
- The name "revoke_self" says "revoke": a word for removing or ending something.
Description, as the server wrote it Permanently revoke THIS agent using its API key as the Bearer token. Use when you discover (at any time) that paired_with is not your owner’s account and cancel_registration no longer works. The key stops working immediately; call register_agent to start over.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
Can't be undone 1Claude Code: ask
yoSend a Yo push notification to your owner.Can send data outNo findings
Why it is in this group
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe description's first verb is "send": it sends or publishes something to other people.
Description, as the server wrote it Send a Yo push notification to your owner. Recommended: include a short subject explaining what the notification is about, and a context_url when there is a useful link to open. The subject appears on the lock screen and in the app; avoid secrets. Requires an agent API key as the Bearer token.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
Changes things 2Claude Code: ask
check_registrationCheck the status of a pairing code from register_agent.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 Check the status of a pairing code from register_agent. On the first poll after the user approves, the response includes the api_key exactly once — store it immediately in your secret mechanism — plus paired_with, the account the agent is now connected to, which you MUST show the user.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
register_agentRegister this agent with Yo (unauthenticated).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 Register this agent with Yo (unauthenticated). Returns a pairing URL and code to show the user, who approves the connection in the Yo app. Then poll check_registration to obtain the API key.
Annotations the server declares
- readOnlyHint: false
- openWorldHint: false
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 untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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, 19:01 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
- 5
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (2 destructive, 1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://getyo.dev/mcp: tools/list returned 5 tools to an anonymous client, including cancel_registration (destructive), revoke_self (destructive), yo (irreversible), register_agent (write), check_registration (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 yo https://getyo.dev/mcpclaude mcp add --transport http yo https://getyo.dev/mcpRun 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": [],
"ask": [
"mcp__yo__register_agent",
"mcp__yo__check_registration",
"mcp__yo__yo"
],
"deny": [
"mcp__yo__cancel_registration",
"mcp__yo__revoke_self"
]
}
}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 yo. Review it before you use it.
Capability tags behind 1 rule
- mcp__yo__yo outbound
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.github.alfongj-com/yo/verify?hash=66cee17984c1c03e3aac754e45eef714eebefe0fd6dd2b2e3860998dce828f23" | jq -e '.changed == false'Pinned hash 66cee17984c1, from Nov 16, 2026, 09:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.alfongj-com/yo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.alfongj-com/yo)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:22 UTC.
Yo MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Yo MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 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 Yo MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: cancel_registration and revoke_self.
Can the Yo MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: yo.
What tools does the Yo MCP server have?
- 5 tools: 2 destructive, 1 irreversible, 2 write. cancel_registration, revoke_self, yo, register_agent and check_registration.
Does the Yo MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Yo MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): yo.
Has the Yo MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.