# Verified Handles (remote · verifiedhandles.org)

Look up people, organisations and things, and their official social media accounts and identifiers.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `verifiedhandles.org`: 86/100 (this document), [markdown](https://verifymcp.io/servers/org-verifiedhandles-verified-handles/verifiedhandles.md), [page](https://verifymcp.io/servers/org-verifiedhandles-verified-handles/verifiedhandles)

## Channel facts

- Endpoint: `https://verifiedhandles.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.59.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 816 tokens (~163/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 58% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Verified Handles MCP server?

Verified Handles is a hosted endpoint at https://verifiedhandles.org/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.

### Claude

```bash
claude mcp add --transport http org-verifiedhandles-verified-handles 'https://verifiedhandles.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-verifiedhandles-verified-handles": {
      "url": "https://verifiedhandles.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-verifiedhandles-verified-handles": {
      "type": "http",
      "url": "https://verifiedhandles.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-verifiedhandles-verified-handles]
url = "https://verifiedhandles.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-verifiedhandles-verified-handles": {
      "type": "remote",
      "url": "https://verifiedhandles.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-verifiedhandles-verified-handles --url 'https://verifiedhandles.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-verifiedhandles-verified-handles:
    url: "https://verifiedhandles.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-verifiedhandles-verified-handles": {
      "Transport": "http",
      "Url": "https://verifiedhandles.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-verifiedhandles-verified-handles -t streamable-http -u 'https://verifiedhandles.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-verifiedhandles-verified-handles": {
      "type": "http",
      "url": "https://verifiedhandles.org/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-11-05 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 85, 0)

- [functional] Server version: 1.85.0 → 1.87.0

### 2026-11-03 (score 85, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.84.0 → 1.85.0

### 2026-11-01 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 83, +1)

- [functional] Server version: 1.78.0 → 1.84.0

### 2026-10-28 (score 82, 0)

- [functional] Server version: 1.76.0 → 1.78.0

### 2026-10-27 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 81, 0)

- [functional] Server version: 1.74.0 → 1.76.0

## MCP tools (5)

### `get_entry` (~169 tokens)

Get an entry

One entry, by VHID, short name or Wikidata QID: its public record (title, description, handles, image, URL) and, as `editing`, what the editor would load for this key — the current revision, the editable fields, every handle with who manages it (the Wikidata sync or the site), which fields the sync manages, and whether this key may edit it live. Without an API key, the public record alone.

Input parameters:

- `entry` (string, required): The entry: its VHID (11 digits), its short name (as in verifiedhandles.org/<short>), or its Wikidata QID (Q42).
- `include_platforms` (boolean): Also list every platform a handle can be on (id, name, URL prefix). Needs an API key.

Output parameters:

- `editing` (object): With an API key: what the editor loads for this key (GET /api/editor/{vhid}): `baseRevisionId`, `capabilities` (whether it may edit live or propose), `editable`, `handles`, `provenance` (which fields…
- `entry`: The entry’s public record, as GET /api/v1/entities/{vhid} answers it. Null for a VHID that is not public (a deleted entry): `editing` says more.
- `vhid` (string): The entry’s VHID: 11 digits, permanent.

### `search_entries` (~72 tokens)

Search entries

Search the entries as the site search does: words match titles, subtitles and descriptions; a Wikidata QID finds the entries linked to it; a VHID finds that entry and the entries that link to it.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `query` (string, required)

Output parameters:

- `limit` (integer): The page size used: the `limit` asked for, clamped to the endpoint’s range.
- `next_offset`: The `offset` of the next page, or null when this is the last one. Follow it rather than computing it.
- `offset` (integer): The offset used: the `offset` asked for, clamped to 0–10,000.
- `query` (string): The query as it was read: trimmed and cut to 100 characters.
- `results` (array): Best match first.
- `total` (integer): How many entries matched in all.

### `find_by_handle` (~185 tokens)

Find entries by handle

Which public entries list a handle: “is x.com/someone an official account, and whose?”. Give a profile’s address as url (https://x.com/someone), or platform (its catalog id: twitter, instagram, youtube, …) and value (someone or @someone). Answers each entry’s VHID, title and URL, the handle as the entry lists it, and whether that handle is verified; an empty list when no entry lists it. Case is ignored where the platform ignores it. Email addresses are not looked up.

Input parameters:

- `platform` (string): The platform’s catalog id, such as twitter. With value.
- `url` (string): A profile’s address, such as https://x.com/someone. Instead of platform and value.
- `value` (string): The handle on that platform, such as someone or @someone.

Output parameters:

- `platform` (string): The platform looked on: the one asked, or the one whose address `url` is.
- `results` (array): Verified handles first, then by VHID; at most 50. Empty when no public entry lists it.
- `value` (string): The handle looked up, as the site stores one: from `url`, what follows the platform’s address.

### `get_entry_history` (~88 tokens)

Entry history

An entry’s public edit history, newest first (`next_offset` pages on). A merged entry’s key gives its own history.

Input parameters:

- `entry` (string, required): The entry: its VHID (11 digits), its short name (as in verifiedhandles.org/<short>), or its Wikidata QID (Q42).
- `limit` (integer)
- `offset` (integer)

Output parameters:

- `history` (array): Newest first.
- `limit` (integer): The page size used: the `limit` asked for, clamped to the endpoint’s range.
- `merged_into` (string): Present when the entry was merged into another: that entry’s VHID. The history is still the merged entry’s own.
- `next_offset`: The `offset` of the next page, or null when this is the last one. Follow it rather than computing it.
- `offset` (integer): The offset used: the `offset` asked for, clamped to 0–10,000.
- `vhid` (string): The entry’s VHID: 11 digits, permanent.

### `get_entries` (~98 tokens)

Get many entries

Up to 50 entries’ public records in one call, by VHID or short name (not a Wikidata QID: get_entry or search_entries finds an entry by its item), each answered as get_entry answers it signed out — the entry, or not_found — in the order given. A name given twice is answered once.

Input parameters:

- `entries` (array, required): The entries: each a VHID (11 digits) or a short name.

Output parameters:

- `results` (array): One element per key asked for, in the order asked, a repeated key once (where it first appears).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-verifiedhandles-verified-handles/verifiedhandles#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-10: 74
- 2026-10-09: 73

## Common questions

### What is the Verified Handles MCP server?

Verified Handles is an MCP server listed in the public MCP registry as org.verifiedhandles/verified-handles. Look up people, organisations and things, and their official social media accounts and identifiers. This page covers its hosted endpoint (https://verifiedhandles.org/mcp).

### Is the Verified Handles MCP server safe to use?

Verified Handles scores 86 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 Verified Handles MCP server expose?

Verified Handles exposes 5 tools: get_entry, search_entries, find_by_handle, get_entry_history, get_entries. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.

### Does the Verified Handles MCP server require authentication?

No. We connected to Verified Handles without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Verified Handles MCP server still maintained?

Verified Handles 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.

### What did VerifyMCP test on the Verified Handles MCP server?

VerifyMCP ran 13 checks on Verified Handles, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://verifiedhandles.org/mcp
- Repository: https://github.com/jameshaworthcs/verifiedhandles-mcp
- Website: https://verifiedhandles.org/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-verifiedhandles-verified-handles/verifiedhandles.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-verifiedhandles-verified-handles/verifiedhandles/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-verifiedhandles-verified-handles/verifiedhandles.json
- HTML version of this page: https://verifymcp.io/servers/org-verifiedhandles-verified-handles/verifiedhandles