Other · Remote MCP server
Verify Api
AI claim verification MCP endpoint with x402 payments and stealth web fetch.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.drain54/verify-api- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- drain54 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/drain54) · how
- Repository
- github.com/drain54/verify-api
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://verify.drain54.my.id | None |
| SSE (HTTP + Server-Sent Events) | https://verify.drain54.my.id | None |
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.
- Endpoint
https://verify.drain54.my.id(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- io.github.drain54/verify-api 1.0.0 · protocol 2025-06-18
- Tools discovered
- 8:
verify_ai_claim,check_endpoint_health,solve_captcha,get_captcha_pricing,read_web_page,search_web,extract_json_from_web,fetch_stealth_web - Checked on
- 2026-10-05
- Endpoint
https://verify.drain54.my.id(SSE)- Reachable
- Yes (HTTP 200)
- SSE stream
- HTTP 200 but not an event stream
- Checked on
- 2026-10-05
How to connect Verify Api
Verify Api is a remote MCP server: there is nothing to install. Its endpoint is https://verify.drain54.my.id, 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.
It also lists an endpoint on the older SSE transport https://verify.drain54.my.id. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 |
|---|---|
| VerifiedDRWebsite authority and AI visibility tools for DR, TrueDR, keywords, backlinks, and partnerships. | 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 China Supplier | Supplier CheckVerify a Chinese supplier before you pay: company identity, status, risk signals. x402 per call. | Remote · HTTPLive check: ✗ no handshake |
| Verify MCPOffline Ed25519 verification of signed receipts, bundles, and trust artifacts. | Local · stdio |
| verify-atomSigned proof of web observations for AI agents: Ed25519 proof packets for any URL. | Local · stdio |
| VerifyAPI - fact-check with signed receiptsFact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations. | Local · stdio |