Server definition

Hash: sha256:f5dd650b76fded92427ec2017720cb713b25d67f1f4299ed0f63571aa66b68ff
What it is: What a remote MCP server returned when asked what it offers: 7 tools

The blob, as servednamed by its sha256

{
  "instructions": "Normalized RDAP (the official successor to WHOIS) domain registration lookups.\n\n- `domain-lookup` — registrar, status, key dates, nameservers and contact\n  entities for a domain name. Set `follow` to true when you need\n  registrar-level detail on thin registries such as .com and .net. For the\n  ccTLDs IANA lists no RDAP server for, the answer is read from the\n  registry's WHOIS server instead and returned in the same shape; `meta`\n  carries `source` (`rdap` or `whois`) and `server`. A WHOIS registry may\n  publish fewer fields — several give no dates, some no registrar — and\n  anything it withholds is null rather than inferred.\n- `bulk-domain-lookup` — the same data for several domains in one pooled\n  call, which is far faster than looping `domain-lookup`. Pro and Business\n  plans only.\n- `ip-lookup` — network range, holder, country, status and geofeed URL for\n  an IPv4 or IPv6 address, optionally with a CIDR prefix length.\n- `asn-lookup` — holder, country and registration dates for an autonomous\n  system number.\n- `nameserver-lookup` — IP addresses, status and sponsoring registrar for a\n  nameserver hostname.\n- `entity-lookup` — an organization or contact by RIR handle, e.g. \"GOGL\"\n  (ARIN) or \"ORG-RIEN1-RIPE\" (RIPE). ARIN, RIPE, APNIC, LACNIC and AFRINIC\n  only; a domain's registrar or registrant comes from `domain-lookup`.\n- `tlds` — which TLDs are supported, which server answers for one, and how\n  reliably that server fills each field. Each entry carries `protocol`;\n  field availability is measured from RDAP responses, so a `whois` entry\n  has none. Metadata: no quota cost.\n\nAuthentication uses your API key as a bearer token. Each successful lookup\n(and each \"not found\", which is still a real answer) counts against your\nmonthly plan quota, exactly like the REST API — one unit per domain in a\nbulk batch. `tlds` is metadata and is never charged.",
  "tools": [
    {
      "description": "Look up normalized RDAP data (holder, country, status, registration dates) for an autonomous system number.",
      "inputSchema": {
        "properties": {
          "asn": {
            "description": "Autonomous system number, e.g. \"15169\" or \"AS15169\".",
            "type": "string"
          }
        },
        "required": [
          "asn"
        ],
        "type": "object"
      },
      "name": "asn-lookup",
      "outputSchema": null
    },
    {
      "description": "Look up normalized RDAP registration data for several domain names in one pooled call. Requires a Pro or Business plan; every domain in the batch counts against the quota.",
      "inputSchema": {
        "properties": {
          "domains": {
            "description": "The domain names to look up, e.g. [\"example.com\", \"example.net\"]. Between 1 and 10 per call. Unicode (IDN) names are accepted.",
            "items": {
              "type": "string"
            },
            "maxItems": 10,
            "minItems": 1,
            "type": "array"
          },
          "follow": {
            "default": false,
            "description": "Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.",
            "type": "boolean"
          },
          "whois": {
            "default": true,
            "description": "Set false to refuse the WHOIS fallback for every domain in the batch, so a TLD with no RDAP server returns not_supported. Defaults to true.",
            "type": "boolean"
          }
        },
        "required": [
          "domains"
        ],
        "type": "object"
      },
      "name": "bulk-domain-lookup",
      "outputSchema": null
    },
    {
      "description": "Look up normalized RDAP registration data (registrar, status, dates, nameservers, contacts) for a domain name.",
      "inputSchema": {
        "properties": {
          "domain": {
            "description": "The domain name to look up, e.g. \"example.com\". Unicode (IDN) names are accepted.",
            "type": "string"
          },
          "follow": {
            "default": false,
            "description": "Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.",
            "type": "boolean"
          },
          "whois": {
            "default": true,
            "description": "Set false to refuse the WHOIS fallback, so a TLD with no RDAP server errors instead of answering over port 43. Defaults to true.",
            "type": "boolean"
          }
        },
        "required": [
          "domain"
        ],
        "type": "object"
      },
      "name": "domain-lookup",
      "outputSchema": null
    },
    {
      "description": "Look up normalized RDAP data for an RIR entity handle — an organization or contact identifier such as \"GOGL\" or \"ORG-RIEN1-RIPE\". Only ARIN, RIPE, APNIC, LACNIC and AFRINIC handles resolve; a domain's registrar or registrant comes from domain-lookup instead.",
      "inputSchema": {
        "properties": {
          "handle": {
            "description": "RIR entity handle, e.g. \"GOGL\" (ARIN) or \"ORG-RIEN1-RIPE\" (RIPE).",
            "type": "string"
          }
        },
        "required": [
          "handle"
        ],
        "type": "object"
      },
      "name": "entity-lookup",
      "outputSchema": null
    },
    {
      "description": "Look up normalized RDAP allocation data (network range, holder, country, status, geofeed URL) for an IP address or CIDR block.",
      "inputSchema": {
        "properties": {
          "ip": {
            "description": "IPv4 or IPv6 address, e.g. \"8.8.8.8\" or \"2001:4860:4860::8888\".",
            "type": "string"
          },
          "prefix": {
            "description": "Optional CIDR prefix length, e.g. 24. Must be 0-32 for IPv4 or 0-128 for IPv6.",
            "type": "integer"
          }
        },
        "required": [
          "ip"
        ],
        "type": "object"
      },
      "name": "ip-lookup",
      "outputSchema": null
    },
    {
      "description": "Look up normalized RDAP data (IP addresses, status, sponsoring registrar) for a nameserver hostname.",
      "inputSchema": {
        "properties": {
          "host": {
            "description": "Nameserver hostname, e.g. \"ns1.example.com\".",
            "type": "string"
          }
        },
        "required": [
          "host"
        ],
        "type": "object"
      },
      "name": "nameserver-lookup",
      "outputSchema": null
    },
    {
      "description": "List the TLDs this API can query, or describe one: which RDAP server answers for it, since when it has been supported, and how often that server fills each field. Metadata, so it never counts against the monthly quota.",
      "inputSchema": {
        "properties": {
          "server": {
            "description": "List only the TLDs served by this host, RDAP or WHOIS, e.g. \"rdap.verisign.com\". Ignored when \"tld\" is given.",
            "type": "string"
          },
          "since": {
            "description": "List only the TLDs added after this ISO 8601 date, e.g. \"2026-01-01\". Ignored when \"tld\" is given.",
            "type": "string"
          },
          "tld": {
            "description": "A single TLD to describe, e.g. \"com\" or \".io\". Omit to list every supported TLD by name.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "tlds",
      "outputSchema": null
    }
  ]
}

Verify it yourself

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