# Verified Handles [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/jameshaworthcs/verifiedhandles-mcp  
**GitHub Stars:** 31  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/verified-handles

## Description
Look up people, organisations and things, and their verified social handles and identifiers.

## Tools
Capabilities this server exposes over MCP:

- **get_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.
- **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.
- **find_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.
- **get_entry_history** — An entry’s public edit history, newest first (`next_offset` pages on). A merged entry’s key gives its own history.
- **get_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.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What the Verified Handles MCP server does

The Verified Handles MCP server gives an AI agent access to records from verifiedhandles.org, a service that lists people, organisations, and things alongside verified social handles and other identifiers. The public, no-key interface is read-only and can search records, retrieve individual entries, check which entries list a particular handle, read edit history, and fetch several records in one request.

The service is relevant to the 🌐 Social Media category when an agent needs to distinguish an organisation’s listed account from an unverified or unrelated profile. It can also provide the identifiers and URLs associated with a record, rather than limiting lookups to social usernames.

## How it works

The Verified Handles MCP server is hosted remotely at `https://verifiedhandles.org/mcp` and uses MCP Streamable HTTP. Requests are stateless: each message is sent as a `POST` and receives a JSON response, so the client does not maintain a session with the service.

Without an authorization header, the server exposes public reads. An API key limits the agent to the permissions assigned to that key and the account’s current role. Clients that support OAuth can instead connect through `https://verifiedhandles.org/mcp/account` and let the account holder approve a role ceiling, read-only access, and an expiry period.

## Setup and configuration

For a public, read-only connection, configure an MCP client with the main endpoint and no authorization header. Account access can use an API key or the OAuth endpoint. API keys are created in the Verified Handles account console, shown only when created, and can be revoked there. Keys may be read-only, limited by role, and set to expire between 1 and 90 days.

The repository documents configurations for Claude Desktop, Claude Code, VS Code, Cursor, ChatGPT, and other clients. A Claude Desktop extension is also provided by the project. OAuth examples use the `/mcp/account` address; clients that cannot complete that flow can use an API key instead.

## Tools and capabilities

The Verified Handles MCP server exposes these public tools:

- `get_entry` retrieves a record by VHID, short name, or Wikidata QID. With suitable authorization, it can also return editing information.
- `search_entries` searches titles, subtitles, descriptions, linked Wikidata items, and VHID relationships.
- `find_by_handle` finds entries listing a supplied social profile URL, platform and value, or handle. It reports the entry, listed handle, and verification status. Email addresses are not searched.
- `get_entry_history` returns an entry’s public edit history, newest first, with offset-based pagination.
- `get_entries` fetches up to 50 records by VHID or short name in one call, preserving the requested order and reporting missing entries.

With an account or key, additional tools may be available according to the user’s role, although the supplied listing specifies the public tools above.

## Limitations and notes

A no-key connection returns public records only. An invalid, expired, or revoked key is rejected rather than treated as an unauthenticated request. Access cannot exceed the key’s role ceiling or the account’s current permissions.

`get_entries` does not accept Wikidata QIDs directly; use `get_entry` or `search_entries` to locate an entry by that identifier. Handle matching follows the case rules of the relevant platform, and an unlisted handle produces an empty result. The server does not cache answers, according to the provided documentation.

_Full upstream README: https://allmcps.com/mcp/verified-handles/readme_