Server definition

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

The blob, as servednamed by its sha256

{
  "instructions": "MyMCPTools is a live-verified directory of Model Context Protocol servers. Use search_mcp_servers to discover servers by keyword, category or integration, get_mcp_server for full install details on one server, and get_server_status / get_server_history / list_server_incidents to check whether a server is actually reachable before recommending it. Every uptime figure comes from real MCP handshakes against the server's remote endpoint, not from self-reported metadata.",
  "tools": [
    {
      "description": "Aggregate health of the whole MCP population: verdict breakdown, share of probeable servers actually serving, transport mix, handshake latency percentiles, tool counts and probe freshness. This is the 'how healthy is MCP right now?' headline number.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {},
        "type": "object"
      },
      "name": "get_catalog_stats",
      "outputSchema": null
    },
    {
      "description": "Full catalog entry for one MCP server by slug: description, author, install command, repo, supported clients, current probe verdict, static repo-freshness signal for local servers, and related servers in the same categories.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "slug": {
            "description": "Catalog slug, e.g. 'filesystem' or 'github'.",
            "type": "string"
          }
        },
        "required": [
          "slug"
        ],
        "type": "object"
      },
      "name": "get_mcp_server",
      "outputSchema": null
    },
    {
      "description": "Trailing probe history for one server plus a daily uptime sparkline — the reliability signal behind the badge on mymcptools.com. Returns per-day uptime buckets and the raw probe points (timestamp, verdict, latency).",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "days": {
            "description": "Uptime window width in days (default 14, max 90).",
            "maximum": 90,
            "minimum": 1,
            "type": "integer"
          },
          "limit": {
            "description": "Max raw probe points returned (default 30, max 200).",
            "maximum": 200,
            "minimum": 1,
            "type": "integer"
          },
          "slug": {
            "description": "Catalog slug.",
            "type": "string"
          }
        },
        "required": [
          "slug"
        ],
        "type": "object"
      },
      "name": "get_server_history",
      "outputSchema": null
    },
    {
      "description": "Current live-probe status for one server: verdict (GOOD / WARN / AUTH_REQUIRED / DOWN / UNPROBEABLE), exposed tool count, handshake latency, negotiated protocol version, remote endpoint, and when it was last seen healthy. Omit the slug to get the catalog-wide verdict summary instead.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "slug": {
            "description": "Catalog slug. Omit for the catalog-wide verdict rollup.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "get_server_status",
      "outputSchema": null
    },
    {
      "description": "Every category and client integration in the MyMCPTools catalog, with the number of servers in each. The slugs returned here are the valid values for the category and integration filters on search_mcp_servers.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {},
        "type": "object"
      },
      "name": "list_categories",
      "outputSchema": null
    },
    {
      "description": "Tool-schema and protocol-version drift events detected between successive probes — which servers added, removed or changed tools, and when. Use this to spot breaking changes in a server you depend on. Newest first.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "limit": {
            "description": "Max drift events returned (default 20, max 100).",
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          },
          "slug": {
            "description": "Restrict to one server.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "list_schema_drift",
      "outputSchema": null
    },
    {
      "description": "Reconstructed outage incidents (contiguous runs of failed probes) across the catalog, newest first. Each incident has a start, an end (or ongoing), a duration and the failure reason. Filter to one server with slug, or to open outages with status='ongoing'.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "limit": {
            "description": "Max incidents returned (default 20, max 100).",
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          },
          "slug": {
            "description": "Restrict to one server.",
            "type": "string"
          },
          "status": {
            "description": "Restrict by resolution state.",
            "enum": [
              "ongoing",
              "resolved"
            ],
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "list_server_incidents",
      "outputSchema": null
    },
    {
      "description": "Search the MyMCPTools catalog of Model Context Protocol servers. Filter by free-text query, category slug, integration slug (claude-desktop, cursor, vs-code, ...), install type, or official status. Set only_verified to restrict to servers that answered a live MCP handshake on the most recent probe. Results carry the live verdict for each server.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "category": {
            "description": "Category slug, e.g. 'database'. See list_categories.",
            "type": "string"
          },
          "install_type": {
            "description": "Restrict to one install mechanism.",
            "enum": [
              "npm",
              "pip",
              "binary",
              "docker",
              "source",
              "remote"
            ],
            "type": "string"
          },
          "integration": {
            "description": "Integration slug, e.g. 'claude-desktop' or 'cursor'.",
            "type": "string"
          },
          "limit": {
            "description": "Max results (default 10, max 50).",
            "maximum": 50,
            "minimum": 1,
            "type": "integer"
          },
          "official": {
            "description": "Only first-party/official servers.",
            "type": "boolean"
          },
          "only_verified": {
            "description": "Only servers whose latest probe verdict is GOOD or WARN.",
            "type": "boolean"
          },
          "query": {
            "description": "Free-text query matched against name, description, author and category.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "search_mcp_servers",
      "outputSchema": null
    }
  ]
}

Verify it yourself

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