Other · Remote MCP server
VerifiedDR
Website authority and AI visibility tools for DR, TrueDR, keywords, backlinks, and partnerships.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.VerifiedDR/verifieddr- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- VerifiedDR (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/VerifiedDR) · how
- Website
- verifieddr.com/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://verifieddr.com/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect VerifiedDR
VerifiedDR is a remote MCP server: there is nothing to install. Its endpoint is https://verifieddr.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Verificar CURPValida, coteja y verifica CURPs mexicanas en el registro de RENAPO. | Local · stdio |
| Verified FeedContradiction-verified, freshness-SLA'd signed feed: per-record status + as-of date + receipt. | Remote · HTTPLive check: ✓ handshake |
| Verified Googledocs MCPMCP server for Google Docs with verified writes - every mutation returns before/after proof. | Local · stdio |
| Verified WagesCurrent source-cited US minimum wage, tipped wage, and FLSA constants for AI agents; cites DOL. | Remote · HTTPLive check: sign-in required |
| VerifierMCP tool observatory: do registry servers answer, and are their answers true? No key. | Remote · HTTPLive check: ✓ handshake |
| VerifiMind PEAS - RefleXion TrinityX-Z-CS AI validation with auditable reasoning. 8 active tools; 5 in maintenance. v0.5.64. | Remote · HTTPLive check: ✓ handshake |
| VerifyIndependent x402 observatory on Base. Sealed decomposition + endpoint audits paid over x402 itself. | Local · stdio |
| Verify ApiAI claim verification MCP endpoint with x402 payments and stealth web fetch. | Remote · HTTP, SSELive check: ✓ handshake |