MCP Servers

Verify an MCP-server claim via DNS TXT

Looks up the origin domain apex TXT records over a fixed DoH resolver (Cloudflare 1.1.1.1) for mnemom-verification=<token>. Found → the claim is marked verified. Not found → {claimed:false, reason:"txt-not-found"} (HTTP 200; retry after DNS propagation). A successful verify by a different owner transfers control (anti-squat). The {id} path parameter is the URL-encoded server endpoint URL. Rate-limited per user and per IP.

post/mcp-servers/{id}/verify

Request

  • Base URL: https://api.mnemom.ai/v1
  • URL: https://api.mnemom.ai/v1/mcp-servers/{id}/verify
  • Auth: one of:
    • API key in cookie mnemom_session
    • HTTP bearer

Path parameters

idstring required

The URL-encoded MCP server endpoint URL being verified.

Response

Verification result (verified, or a friendly retryable not-found).

claimedboolean required
verified_atstring date-time nullable
reason'txt-not-found' nullable

Changes

No recorded changes to this operation across all 1 revision of this API.