Server definition

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

The blob, as servednamed by its sha256

{
  "instructions": "Ask this server whether an MCP server in the official registry can actually be used.\n\nA registry listing is a claim the publisher typed, not a connection anybody verified. This\nmakes one `initialize` call to the endpoint the listing names, with no credential, and says\nwhat a stock client gets: `usable`, `needs_credential`, `charged`, `unreachable`,\n`local_only`, or `not_listed`.\n\nOn a `needs_credential` answer it follows the discovery chain the spec defines — RFC 9728\nprotected-resource metadata, RFC 8414 authorization-server metadata, RFC 7591 dynamic\nclient registration — and reports whether a client nobody has heard of could register\nitself, or whether a person has to go and create one. Those two are both HTTP 401 and the\nregistry lists them identically.\n\nA second question this server answers is whether a listing is still what it was. Monthly\nsnapshots of every reachable server's tool catalogue start in September 2026, and\n`mcp_liveness_drift` diffs one server between a month you name and the latest — which\ntools were added, removed, or changed their description or schemas. Nobody can backfill a\nmonth they did not record, which is why an answer here can say `unchanged` and mean it.\n\nEvery answer carries a `next` field, `{ what, url, why }` or null: when a product we run\ntoday would tell you something this one call cannot — agentcheck, which monitors a server\nyou publish and warns you when it stops answering — `next` names it; otherwise it is null.\n\nIt never sends a credential, never registers a client and never retries a refusal.",
  "tools": [
    {
      "description": "Given a server's exact name in the official MCP registry, make one `initialize` call to\nthe endpoint its listing names and report what a client with no credential gets.\n\nOutcomes: `usable` (it connected and negotiated a protocol version), `needs_credential`\n(401 or 403 — the answer then says whether a credential can be obtained in-band or\nwhether a person has to create one), `charged` (402, access is for sale), `unreachable`\n(the listed endpoint is not an MCP server: wrong URL, dead host, or a 200 that is not\nJSON-RPC), `local_only` (no remote endpoint; it must be spawned as a process), and\n`not_listed` (no server with that exact name).\n\nCall this before spending a call on a server you found in the catalogue. Roughly two in\nfive remote listings do not answer a stock client.",
      "inputSchema": {
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "additionalProperties": false,
        "properties": {
          "name": {
            "description": "Exact registry name, namespaced — e.g. `io.github.owner/server`. Not a URL and not a title.",
            "minLength": 1,
            "type": "string"
          },
          "skipCredentialCheck": {
            "description": "Skip the OAuth discovery chain on a 401. Faster (one request instead of up to five) but the answer then cannot say whether a credential is obtainable.",
            "type": "boolean"
          }
        },
        "required": [
          "name"
        ],
        "type": "object"
      },
      "name": "mcp_liveness_check",
      "outputSchema": null
    },
    {
      "description": "Given a server's exact name in the official MCP registry, report which of its tools were\nadded, removed, or had their description, input schema or output schema change between\nthe month you name and the latest monthly snapshot.\n\nCall this when a server worked before and is behaving differently now, when a prompt or\nan integration written against its tools has started failing, or before trusting a tool\ndescription you cached. A liveness check says it answers today; this says whether it is\nstill the same server your code was written against.\n\nThe answer names the changed tools and the kind of change. It does not diff the schemas\nthemselves: the snapshots keep content hashes, not bodies, so `detail` hands back the\nrelease-asset location of both full months for a caller that needs the exact diff.\n\nA month with no snapshot for that server gets an error naming the months that do have\none, never an empty diff that would read as `nothing changed`.",
      "inputSchema": {
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "additionalProperties": false,
        "properties": {
          "name": {
            "description": "Exact registry name, namespaced — e.g. `io.github.owner/server`. Not a URL and not a title.",
            "minLength": 1,
            "type": "string"
          },
          "since": {
            "description": "The month to diff from, as `YYYY-MM`. Omit it to diff from the earliest month this server appears in, which is the stable choice — a hard-coded month goes wrong as soon as the next snapshot lands.",
            "pattern": "^\\d{4}-\\d{2}$",
            "type": "string"
          }
        },
        "required": [
          "name"
        ],
        "type": "object"
      },
      "name": "mcp_liveness_drift",
      "outputSchema": null
    },
    {
      "description": "Return the six outcomes this server can report, what each means for an agent choosing a server from the registry, and what to do next for each. Makes no request and costs nothing; call it once to interpret mcp_liveness_check results.",
      "inputSchema": {
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "mcp_liveness_explain_outcomes",
      "outputSchema": null
    }
  ]
}

Verify it yourself

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