Upstream
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_api_statusA | Check if an AI or developer API provider (OpenAI, Anthropic, Gemini, Mistral, Groq, GitHub, Stripe, Cloudflare, Vercel, Supabase, Twilio... ~40 total) is up, degraded or down right now. Use BEFORE calling a provider's API, or right after you get 5xx/429/timeout errors, to decide whether to retry, wait or switch to a fallback. Returns a one-line summary first, then verdict, recommended_action, open incidents, affected components, checked_at and freshness (checked every ~4 min). Example: {"provider":"openai"}. Free within the daily quota, then $0.003 via x402. Alias: get_status. |
| check_model_deprecationA | Check if an LLM model id is active, deprecated or retired, its shutdown date, and the recommended replacement, from the provider's own deprecation page (OpenAI, Anthropic, Google, etc.). Use before hard-coding or calling a model, or when a model call fails with "model not found / deprecated". Returns summary first, then verdict, recommended_action (keep_using | plan_migration | switch_now | verify_with_provider), replacement, shutdown_date, evidence rows and freshness. Example: {"model":"gpt-4-0613"}. Free within the daily quota, then $0.003 via x402. Alias: get_model (param "id"). |
| list_recent_api_changesA | List recent breaking or notable changes across AI and developer APIs: outages and recoveries, deprecation-page edits, model retirements and pricing-page edits. Use to answer "did anything change that could break my integration?" or to explain sudden errors. Returns summary first, then the change list with timestamps and source links. Example: {"provider":"anthropic","kind":"model_retirement"}. Free within the daily quota, then $0.01 via x402. Alias: get_changes. |
| list_providersA | List the ~40 AI and developer API providers Upstream tracks with their current state (operational/degraded/outage) and checked_at. Use to find the right provider id for check_api_status, or for a quick all-providers health overview. Free. |
| get_digestA | Daily digest (free) of AI/dev API incidents, model deprecations/retirements, pricing-page changes and breaking MCP server changes. Use for a once-a-day catch-up instead of polling. Example: {} for the latest, or {"date":"2026-10-14"}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The two check_* tools cleanly split provider-level health from model-level lifecycle, and list_providers is clearly the index helper for check_api_status. The main overlap is between list_recent_api_changes and get_digest, which both surface incidents/deprecations; the descriptions distinguish them (on-demand change feed vs once-a-day catch-up), so confusion is minor.
All names are snake_case verb_noun, with aliases documented (get_status, get_model, get_changes). Three verb families appear (check_, list_, get_), which is readable and mostly predictable, though not a single uniform verb pattern.
Five tools is a tight, well-scoped surface for an API/model monitoring service: status check, deprecation check, provider index, change feed, and digest. Each tool earns its place with no redundancy bloat.
Provider health, model deprecation, the provider index, recent changes and a daily digest cover the core monitoring lifecycle including lookups and alerts. A minor gap is the absence of a dedicated query for the MCP-server breaking changes mentioned in the digest, forcing agents to use the generic change feed.