# Yo (remote · getyo.dev)

Let agents send content-free push notifications to a paired phone via MCP.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

- remote · `getyo.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/alfongj-com-yo/getyo.md), [page](https://verifymcp.io/servers/alfongj-com-yo/getyo)

## Channel facts

- Endpoint: `https://getyo.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-08-17.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 569 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http alfongj-com-yo https://getyo.dev/mcp
```

### Codex

```toml
[mcp_servers.alfongj-com-yo]
url = "https://getyo.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alfongj-com-yo": {
      "type": "remote",
      "url": "https://getyo.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alfongj-com-yo --url https://getyo.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  alfongj-com-yo:
    url: "https://getyo.dev/mcp"
```

### Other

```json
{
  "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.

## 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-08-16 (score 70, +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.

### 2026-08-14 (score 69, +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.

### 2026-08-12 (score 68, +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.

### 2026-08-11 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 66, +2)

- [security] 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
- [functional regression] Schema quality: 97 → 113
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] New tool “cancel_registration”
- [functional] New tool “revoke_self”
- [cosmetic] “check_registration” added an optional parameter “claim_token”

### 2026-08-09 (score 64)

First indexed and scored.

## MCP tools (5)

### `register_agent` (~113 tokens)

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.

Input parameters:

- `description` (string): Short description of what this agent does
- `platform` (string): Agent platform (e.g. "cursor", "devin", "claude-code")
- `proposed_name` (string, required): Proposed display name for the agent (e.g. "banana", "devin-home-repo")

### `check_registration` (~102 tokens)

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.

Input parameters:

- `claim_token` (string): The claim_token returned by register_agent; required to receive the api_key
- `pairing_code` (string, required): The pairing code returned by register_agent

### `cancel_registration` (~117 tokens)

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.

Input parameters:

- `claim_token` (string, required): The claim_token returned by register_agent (authorizes the cancellation)
- `pairing_code` (string, required): The pairing code returned by register_agent

### `revoke_self` (~78 tokens)

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.

Input parameters:

- `confirm` (boolean, required): Must be true — revocation is immediate and irreversible

### `yo` (~67 tokens)

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.

Input parameters:

- `context_url` (string): Optional https or app deep-link URL opened when the user taps the notification

## Diagnostics

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

## Score history

- 2026-08-17: 70
- 2026-08-16: 70
- 2026-08-15: 69
- 2026-08-14: 69
- 2026-08-13: 68
- 2026-08-12: 68
- 2026-08-11: 67
- 2026-08-10: 66
- 2026-08-09: 64

## Links

- Remote endpoint: https://getyo.dev/mcp
- Repository: https://github.com/alfongj-com/yo-plugin
- Website: https://getyo.dev/
- Changelog RSS feed: https://verifymcp.io/servers/alfongj-com-yo/getyo.xml
- Changelog JSON feed: https://verifymcp.io/servers/alfongj-com-yo/getyo.json
- HTML version of this page: https://verifymcp.io/servers/alfongj-com-yo/getyo