Server definition

Hash: sha256:6d4540227b18a7b33c30ce338ab1e637da46dc2a0f326e2969564cd32afb43d4
What it is: What a remote MCP server returned when asked what it offers: 1 tools

The blob, as servednamed by its sha256

{
  "instructions": null,
  "tools": [
    {
      "description": "Check whether a domain name is registered, using real-time RDAP data\n(the IETF-standardized successor to WHOIS). Use for \"is domain-x.com\navailable/registered\", \"who is domain-x.com registered with\", or \"when\ndoes domain-x.com expire\" style questions.\n\n`domain` is a bare domain like \"example.com\" -- no protocol prefix, no\npath, no spaces.\n\nIf the domain is NOT registered, returns `{\"domain\": ..., \"registered\":\nfalse}` -- this is a normal, meaningful answer (the domain is\navailable), not an error.\n\nIf the domain IS registered, returns `{\"domain\", \"registered\": true,\n\"status\", \"registered_date\", \"expiration_date\", \"last_changed_date\",\n\"registrar\"}`. `status` is a list of RDAP status codes (e.g. \"active\",\n\"client transfer prohibited\"). Dates are ISO 8601. `registrar` is the\nregistrar's name, or null if the registry redacts it for privacy.\n\nFor obviously malformed input (not a domain -- e.g. missing a dot, has\nspaces, or includes a protocol like \"https://\"), returns a clean\n`{\"error\": ...}` instead of calling the API.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "domain": {
            "type": "string"
          }
        },
        "required": [
          "domain"
        ],
        "type": "object"
      },
      "name": "check_domain",
      "outputSchema": {
        "additionalProperties": true,
        "type": "object"
      }
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:6d4540227b18a7b33c30ce338ab1e637da46dc2a0f326e2969564cd32afb43d4 | sha256sum