Yo
REMOTE · GETYO.DEV · SCANNED AUG 17
Let agents send content-free push notifications to a paired phone via MCP.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 569 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · getyo.dev
claude mcp add --transport http alfongj-com-yo https://getyo.dev/mcp
[mcp_servers.alfongj-com-yo] url = "https://getyo.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alfongj-com-yo": {
"type": "remote",
"url": "https://getyo.dev/mcp",
"enabled": true
}
}
} openclaw mcp add alfongj-com-yo --url https://getyo.dev/mcp --transport streamable-http
mcp_servers:
alfongj-com-yo:
url: "https://getyo.dev/mcp" {
"mcpServers": {
"alfongj-com-yo": {
"type": "http",
"url": "https://getyo.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 16 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_registration” rewrote its description, which is the text the model reads security
- Schema quality: 97 → 113 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- New tool “cancel_registration” functional
- New tool “revoke_self” functional
- “check_registration” added an optional parameter “claim_token” cosmetic
- 9 Aug 26 64
First indexed and scored.
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 17 Aug 2026 · Probed https://getyo.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.getyo.dev | CN=YR2,O=Let's Encrypt,C=US | 8 Aug 2026 | 6 Nov 2026 | RSA 2048 | SHA256-RSA | 6a2939d58dcfe47dda50d48c40b34ce2cf2 |
| SANs: *.getyo.dev, getyo.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of getyo.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| getyo.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; manifest-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://getyo.dev/mcp | Verified | 200 | |
| http (plaintext) | http://getyo.dev/mcp | HTTPS enforced | 308 | https://getyo.dev/mcp |
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.
cancel_registration ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | string | yes | The claim_token returned by register_agent (authorizes the cancellation) |
| pairing_code | string | yes | The pairing code returned by register_agent |
No output schema declared.
No examples provided.
check_registration ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | string | – | The claim_token returned by register_agent; required to receive the api_key |
| pairing_code | string | yes | The pairing code returned by register_agent |
No output schema declared.
No examples provided.
register_agent ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Short description of what this agent does |
| platform | string | – | Agent platform (e.g. "cursor", "devin", "claude-code") |
| proposed_name | string | yes | Proposed display name for the agent (e.g. "banana", "devin-home-repo") |
No output schema declared.
No examples provided.
revoke_self ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true — revocation is immediate and irreversible |
No output schema declared.
No examples provided.
yo ~67
Send a Yo — a content-free push notification — to your owner. Requires an agent API key as the Bearer token. Optionally include a context_url the notification tap-through will open.
| Name | Type | Req | Description |
|---|---|---|---|
| context_url | string | – | Optional https or app deep-link URL opened when the user taps the notification |
No output schema declared.
No examples provided.