# Upstream (remote · upstream.toolweather.workers.dev)

Is this AI/dev API down? Is this model deprecated, what replaces it? Live status for ~40 APIs.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `upstream.toolweather.workers.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/toolweather-upstream/upstream.md), [page](https://verifymcp.io/servers/toolweather-upstream/upstream)

## Channel facts

- Endpoint: `https://upstream.toolweather.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1503 tokens (~300/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Upstream MCP server?

Upstream is a hosted endpoint at https://upstream.toolweather.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http toolweather-upstream 'https://upstream.toolweather.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "toolweather-upstream": {
      "url": "https://upstream.toolweather.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "toolweather-upstream": {
      "type": "http",
      "url": "https://upstream.toolweather.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.toolweather-upstream]
url = "https://upstream.toolweather.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "toolweather-upstream": {
      "type": "remote",
      "url": "https://upstream.toolweather.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add toolweather-upstream --url 'https://upstream.toolweather.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  toolweather-upstream:
    url: "https://upstream.toolweather.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "toolweather-upstream": {
      "Transport": "http",
      "Url": "https://upstream.toolweather.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add toolweather-upstream -t streamable-http -u 'https://upstream.toolweather.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "toolweather-upstream": {
      "type": "http",
      "url": "https://upstream.toolweather.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 66, 0)

- [functional] Server version: 0.2.0 → 0.2.1

### 2026-10-16 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_api_status” rewrote its description, which is the text the model reads
- [security] Tool “check_model_deprecation” rewrote its description, which is the text the model reads
- [security] Tool “get_digest” rewrote its description, which is the text the model reads
- [security] Tool “list_providers” rewrote its description, which is the text the model reads
- [security] Tool “list_recent_api_changes” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 169 → 300
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “check_api_status” reworded the description of “provider”
- [cosmetic] “check_model_deprecation” reworded the description of “id”
- [cosmetic] “check_model_deprecation” reworded the description of “model”
- [cosmetic] “get_digest” reworded the description of “date”
- [cosmetic] “list_recent_api_changes” reworded the description of “kind”
- [cosmetic] “list_recent_api_changes” reworded the description of “limit”
- [cosmetic] “list_recent_api_changes” reworded the description of “provider”
- [cosmetic] “list_recent_api_changes” reworded the description of “since”

### 2026-10-15 (score 66)

First indexed and scored.

## MCP tools (5)

### `check_api_status` (~247 tokens)

Is this API / provider down right now?

Check whether one 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 that provider, or right after 5xx/429/timeouts, to choose retry, wait, or a fallback. Not for a model id (check_model_deprecation), the filtered change feed (list_recent_api_changes), or the daily rollup (get_digest). Returns summary, verdict (up|degraded|partially down|down|unknown), recommended_action, incidents, affected_components, checked_at, and freshness; status is rechecked about every 5 minutes. An unknown provider id returns 404 unknown_provider. Example: {"provider":"openai"}. Free within the daily quota, then $0.003 via x402. Alias: get_status.

Input parameters:

- `provider` (string, required): Lowercase provider id from list_providers, not the display name. Examples: openai, anthropic, google-ai, mistral, groq, github, stripe, cloudflare.

### `check_model_deprecation` (~317 tokens)

Is this model deprecated, and what replaces it?

Check whether one LLM model id is active, deprecated, or retired, plus its shutdown date and replacement, from that provider's deprecation page (OpenAI, Anthropic, Google, and other tracked LLM vendors). Use before hard-coding or calling a model, or when a call fails with model-not-found. Not for API uptime (check_api_status) and not for a retirement feed (list_recent_api_changes with kind model_retirement, or get_digest). Returns summary, verdict (active|deprecated|retired|unknown), recommended_action (keep_using|plan_migration|switch_now|verify_with_provider), replacement, shutdown_date, evidence, and freshness; pages are re-read every few hours. An unlisted id is verdict unknown, not an error; longer than 120 characters returns 400 bad_model_id. Example: {"model":"gpt-4-0613"}. Free within the daily quota, then $0.003 via x402. Alias: get_model (param id).

Input parameters:

- `id` (string): Deprecated alias of model, only for the get_model tool name. Same 1–120 character API id. Ignored when model is also set.
- `model` (string): Exact API model id, not a display name or provider id. 1–120 characters; lowercased, and a leading models/ is stripped. Examples: gpt-4-0613, claude-3-opus-20240229, gemini-1.5-pro.

### `list_recent_api_changes` (~342 tokens)

What changed recently in AI/dev APIs?

List the on-demand feed of recent AI and developer API changes (status flips, deprecation-page edits, model retirements, pricing-page edits). Use for a chosen window, one provider, or one kind, when explaining sudden breakage. Not for live up/down (check_api_status) and not for the once-a-day digest, which also covers MCP server breakage (get_digest). Returns summary, count, freshness, and changes[] with provider, kind, title, detail, source, and at, newest first. Status rows arrive within about 5 minutes; doc-page rows every few hours. A limit above 500 is clamped to 500; an unknown provider returns an empty list, not an error. Example: {"provider":"anthropic","kind":"model_retirement"}. Free within the daily quota, then $0.01 via x402. Alias: get_changes.

Input parameters:

- `kind` (string): Optional type filter. status = provider state flips; deprecations = deprecation-page line edits; model_retirement = a model id became deprecated or retired; pricing = pricing-page line edits. Omit fo…
- `limit` (number): How many changes to return, newest first. Positive integer. Omit for 100.
- `provider` (string): Optional lowercase provider id from list_providers, e.g. openai or anthropic. Omit for every provider.
- `since` (string): Exclusive lower bound compared to each change's at. ISO 8601 UTC. Example: 2026-10-01T00:00:00Z. Omit for 7 days ago.

### `list_providers` (~147 tokens)

List tracked API providers

List every AI and developer API provider Upstream tracks (~40) with id, name, category, current state, checked_at, and status page. Use to pick a provider id for check_api_status, or for one all-providers health pass. Not for one provider's incidents (check_api_status) and not for what changed (list_recent_api_changes or get_digest). No parameters. Always free; does not spend the daily quota. State is refreshed about every 5 minutes. Returns {count, providers:[{id, name, category, state, checked_at, status_page}]}; state is operational, degraded, partial_outage, major_outage, maintenance, or unknown.

### `get_digest` (~306 tokens)

Daily AI/dev API breaking-changes digest

Read one published daily breaking-changes digest: AI/dev API status flips, model deprecations and retirements, pricing-page edits, and breaking MCP server changes. Use for a once-a-day catch-up. For a filtered on-demand API feed with no MCP section, use list_recent_api_changes; for live up/down, check_api_status; for one model id, check_model_deprecation. Always free (no quota, no x402). Published once at 12:00 UTC as a frozen window since the previous issue (usually ~24h); not updated later. Omit date for the latest; a missing YYYY-MM-DD returns 404 {error:no_issue}. One issue per date, no paging. Returns {date, title, summary, window_start, window_end, published_at, markdown, data, url, sponsor:null}. data holds counts, status, open_now, model_changes, shutting_down_30d, pricing, deprecation_page_edits, and mcp (breaking, non_breaking, down, back, auth_broken, auth_fixed). markdown caps model rows, breaking MCP rows, and each MCP event kind at 30, 30, and 20; data is the full window.

Input parameters:

- `date` (string): Published issue date, YYYY-MM-DD (example 2026-10-14). Omit for the latest issue. A date with no stored issue returns 404 no_issue; issues appear at 12:00 UTC.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/toolweather-upstream/upstream#diagnostics

## Score history

- 2026-10-23: 69
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 67
- 2026-10-19: 67
- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 66

## Common questions

### What is the Upstream MCP server?

Upstream is an MCP server listed in the public MCP registry as io.github.toolweather/upstream. Is this AI/dev API down? Is this model deprecated, what replaces it? Live status for ~40 APIs. This page covers its hosted endpoint (https://upstream.toolweather.workers.dev/mcp).

### Is the Upstream MCP server safe to use?

Upstream scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Upstream MCP server expose?

Upstream exposes 5 tools: check_api_status, check_model_deprecation, list_recent_api_changes, list_providers, get_digest. Their descriptions and schemas cost roughly 1,359 tokens of context every time the server is loaded.

### Does the Upstream MCP server require authentication?

No. We connected to Upstream without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Upstream MCP server still maintained?

Upstream is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://upstream.toolweather.workers.dev/mcp
- Repository: https://github.com/toolweather/upstream
- Website: https://upstream-api.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/toolweather-upstream/upstream.xml
- Changelog JSON feed: https://verifymcp.io/servers/toolweather-upstream/upstream.json
- HTML version of this page: https://verifymcp.io/servers/toolweather-upstream/upstream