Verified Handles
REMOTE · VERIFIEDHANDLES.ORG
Look up people, organisations and things, and their official social media accounts and identifiers.
Available components
Last scanned (6 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 58% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +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.
- 4 Nov 26 0
- Server version: 1.85.0 → 1.87.0 functional
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.84.0 → 1.85.0 functional
- 1 Nov 26 +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.
- 29 Oct 26 +1
- Server version: 1.78.0 → 1.84.0 functional
- 28 Oct 26 0
- Server version: 1.76.0 → 1.78.0 functional
- 27 Oct 26 +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.
- 26 Oct 26 0
- Server version: 1.74.0 → 1.76.0 functional
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 5 Nov 2026 · Probed https://verifiedhandles.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=verifiedhandles.org | CN=WR3,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | afc1a5368f69766a0a14cfef0b75d77b |
| SANs: verifiedhandles.org | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of verifiedhandles.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 725, 26974 | 8, 8 | Verified |
| verifiedhandles.org. | 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; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'sha256-Q2KTUGPiqZkWBfduIChFQsfjlNzwwr4T0aORMhl4oFU='; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-action 'self'; style-src 'self' 'sha256-+gzxvb/d9pcPNiPsy1wp+QwIFnWtN/SIitElcG7OZy4=' 'sha256-s3I7318YnfAqBhvRJ6/M57iMWqk6uhcTaqBXlrlkBj8='; font-src 'self'; connect-src 'self' https://upload.wikimedia.org; img-src 'self' blob:; require-trusted-types-for 'script'; trusted-types vh-html vh-script-url default; report-uri /csp-report |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verifiedhandles.org/mcp | Verified | 200 | |
| http (plaintext) | http://verifiedhandles.org/mcp | HTTPS enforced | 301 | https://verifiedhandles.org/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_by_handle Find entries by handle ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | The platform looked on: the one asked, or the one whose address `url` is. |
| results | array | yes | Verified handles first, then by VHID; at most 50. Empty when no public entry lists it. |
| value | string | yes | The handle looked up, as the site stores one: from `url`, what follows the platform’s address. |
No examples provided.
get_entries Get many entries ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | yes | The entries: each a VHID (11 digits) or a short name. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | One element per key asked for, in the order asked, a repeated key once (where it first appears). |
No examples provided.
get_entry Get an entry ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entry | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | yes | 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 | yes | The entry’s VHID: 11 digits, permanent. |
No examples provided.
get_entry_history Entry history ~88
An entry’s public edit history, newest first (`next_offset` pages on). A merged entry’s key gives its own history.
| Name | Type | Req | Description |
|---|---|---|---|
| entry | string | yes | The entry: its VHID (11 digits), its short name (as in verifiedhandles.org/<short>), or its Wikidata QID (Q42). |
| limit | integer | – | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| history | array | yes | Newest first. |
| limit | integer | yes | 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 | – | yes | The `offset` of the next page, or null when this is the last one. Follow it rather than computing it. |
| offset | integer | yes | The offset used: the `offset` asked for, clamped to 0–10,000. |
| vhid | string | yes | The entry’s VHID: 11 digits, permanent. |
No examples provided.
search_entries Search entries ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The query as it was read: trimmed and cut to 100 characters. |
| results | array | yes | Best match first. |
| total | integer | yes | How many entries matched in all. |
No examples provided.
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.
remote · verifiedhandles.org
claude mcp add --transport http org-verifiedhandles-verified-handles 'https://verifiedhandles.org/mcp'
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.