Server definition

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

The blob, as servednamed by its sha256

{
  "instructions": "Live and historical availability for public APIs and developer platforms. Use get_api_status when the user hits an error from a third-party API and you need to tell an outage apart from a bug in their own code. Statuses from list_apis and list_down_apis are a published snapshot that can be up to a day old and carry a monitorCheckedAt timestamp — read it before relying on them; get_api_status probes the endpoint at call time. For past behaviour rather than the present, use get_incident_history (the vendor’s own published incidents) and rank_reliability (cross-vendor scorecard — incidents, downtime minutes and MTTR for several services at once, which no single vendor’s tooling can answer). Both report covered:false for services we hold no archive on; treat that as unknown, never as zero.",
  "tools": [
    {
      "description": "Probe a monitored API endpoint at call time and return up/degraded/down with the response time. This is the tool to reach for when a user asks \"is X down?\" — it makes a real request rather than reading the hourly cache.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "slug": {
            "description": "API slug, e.g. \"openai\". Use search_apis to resolve a name.",
            "minLength": 1,
            "type": "string"
          }
        },
        "required": [
          "slug"
        ],
        "type": "object"
      },
      "name": "get_api_status",
      "outputSchema": null
    },
    {
      "description": "Real incidents a vendor published on its own status page, newest first, with start/end times, duration, severity, affected components and a link to the vendor’s incident page. Use this for \"has X been flaky lately?\" — it is the vendor’s own record, not our probes. Services without a public Statuspage endpoint return covered:false rather than an empty list.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "limit": {
            "description": "Max incidents (default 25).",
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          },
          "service": {
            "description": "API slug, e.g. \"openai\". Use search_apis to resolve a name.",
            "minLength": 1,
            "type": "string"
          },
          "window": {
            "description": "Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d).",
            "enum": [
              "7d",
              "30d",
              "90d",
              "180d",
              "365d",
              "all"
            ],
            "type": "string"
          }
        },
        "required": [
          "service"
        ],
        "type": "object"
      },
      "name": "get_incident_history",
      "outputSchema": null
    },
    {
      "description": "Uptime percentages, response-time stats and recorded data points for one API over a time range. History is retained for 30 days; an API added recently will have few or no data points, which reads as null percentages rather than 100%.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "range": {
            "description": "Window to return data points for (default 24h).",
            "enum": [
              "24h",
              "7d",
              "30d"
            ],
            "type": "string"
          },
          "slug": {
            "description": "API slug, e.g. \"openai\".",
            "minLength": 1,
            "type": "string"
          }
        },
        "required": [
          "slug"
        ],
        "type": "object"
      },
      "name": "get_uptime_history",
      "outputSchema": null
    },
    {
      "description": "List the APIs and developer platforms this service monitors, optionally filtered by category. Statuses come from the most recently published monitor snapshot, not a live probe, and can be up to a day old — check monitorCheckedAt, and call get_api_status when the caller needs the status right now.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "category": {
            "description": "Category slug to filter by, e.g. \"ai\" — omit for all categories.",
            "type": "string"
          },
          "limit": {
            "description": "Max results (default 25).",
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          }
        },
        "type": "object"
      },
      "name": "list_apis",
      "outputSchema": null
    },
    {
      "description": "Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {},
        "type": "object"
      },
      "name": "list_categories",
      "outputSchema": null
    },
    {
      "description": "Everything the most recent monitor run found down or degraded, across all categories. Returns an empty list when the monitor snapshot is missing or stale — an empty list is therefore not proof that everything is healthy; check monitorLastRun.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {},
        "type": "object"
      },
      "name": "list_down_apis",
      "outputSchema": null
    },
    {
      "description": "Given several service slugs, return a scorecard ranked worst-first: incident count, total downtime minutes, mean time to resolve, and the longest incident over a window. Use this to answer \"which vendor in my stack is least reliable?\" — it compares services across vendors, which a vendor’s own monitoring tool cannot. Services with no archive are listed separately as uncovered instead of being ranked as flawless.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "services": {
            "description": "API slugs to compare, e.g. [\"openai\",\"anthropic\",\"vercel\"].",
            "items": {
              "minLength": 1,
              "type": "string"
            },
            "maxItems": 25,
            "minItems": 1,
            "type": "array"
          },
          "window": {
            "description": "Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d).",
            "enum": [
              "7d",
              "30d",
              "90d",
              "180d",
              "365d",
              "all"
            ],
            "type": "string"
          }
        },
        "required": [
          "services"
        ],
        "type": "object"
      },
      "name": "rank_reliability",
      "outputSchema": null
    },
    {
      "description": "Find monitored APIs by name, slug, category or description. Use this to resolve a product name the user mentioned into the slug the other tools take.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "limit": {
            "description": "Max results (default 25).",
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          },
          "query": {
            "description": "Free-text query, e.g. \"openai\" or \"payments\".",
            "minLength": 1,
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "type": "object"
      },
      "name": "search_apis",
      "outputSchema": null
    }
  ]
}

Verify it yourself

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