# Toolweather (remote · toolweather.toolweather.workers.dev)

MCP health (~2k servers) + API status & model deprecations (~40 APIs). One suite for agents.

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

## Components

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

## Channel facts

- Endpoint: `https://toolweather.toolweather.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (unwatch_server).
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3997 tokens (~222/item across 18 items; 18 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

Toolweather is a hosted endpoint at https://toolweather.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-toolweather 'https://toolweather.toolweather.workers.dev/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "toolweather-toolweather": {
      "type": "http",
      "url": "https://toolweather.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 63, +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 62, +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 61, +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 60, +1)

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

### 2026-10-16 (score 59, −1)

- [security] Tool “check_api_status” rewrote its description, which is the text the model reads
- [security] Tool “check_mcp_server_health” 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 “find_alternative_mcp_servers” rewrote its description, which is the text the model reads
- [security] Tool “get_api_key” 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
- [security] Tool “list_watches” rewrote its description, which is the text the model reads
- [security] Tool “unwatch_server” rewrote its description, which is the text the model reads
- [security] Tool “watch_server” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 137 → 222
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.3.0 → 0.5.0
- [functional] New tool “batch_check_mcp_servers”
- [functional] New tool “check_merchant”
- [functional] New tool “get_quota”
- [functional] New tool “paycheck_get_api_key”
- [functional] New tool “paycheck_get_quota”
- [functional] New tool “score_spend”
- [functional] New tool “spendgate_get_api_key”
- [cosmetic] “check_api_status” reworded the description of “provider”
- [cosmetic] “check_mcp_server_health” reworded the description of “bearer_token”
- [cosmetic] “check_mcp_server_health” reworded the description of “fresh”
- [cosmetic] “check_mcp_server_health” reworded the description of “server”
- [cosmetic] “check_mcp_server_health” reworded the description of “tool”
- [cosmetic] “check_model_deprecation” reworded the description of “id”
- [cosmetic] “check_model_deprecation” reworded the description of “model”
- [cosmetic] “find_alternative_mcp_servers” reworded the description of “limit”
- [cosmetic] “find_alternative_mcp_servers” reworded the description of “query”
- [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”
- [cosmetic] “unwatch_server” reworded the description of “id”
- [cosmetic] “watch_server” reworded the description of “server”
- [cosmetic] “watch_server” reworded the description of “webhook_url”

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

First indexed and scored.

## MCP tools (18)

### `check_mcp_server_health` (~361 tokens)

Is this MCP server healthy / safe to call right now?

Read whether one remote MCP server, and optionally one tool on it, is safe to call right now. Use before adding or calling that server, or after its calls fail or time out. Do not use it to search by capability (find_alternative_mcp_servers), to vet a list (batch_check_mcp_servers; stored verdicts only), or to subscribe to later outages (watch_server). A result older than 5 minutes, or fresh/bearer_token, runs one read-only initialize and spends a live-check credit (200/day, then the cache). Counts on the Toolweather quota (1,000/key or 50/day anonymous). Returns summary, verdict (safe|caution|unsafe|unknown), recommended_action (call_it|call_with_care|use_alternative|verify_yourself), reasons, latency_ms, auth, last_tool_change, checked_at, and freshness. Also callable as is_safe_to_call.

Input parameters:

- `bearer_token` (string): Token for the target server only, not a Toolweather key. One authenticated initialize + tools/list, never stored or logged. Setting it forces a live check.
- `fresh` (boolean): True forces a live read-only initialize now and spends one of 200 live checks/day (priced as a live check). Omit to live-check only when the stored result is older than 5 minutes.
- `server` (string, required): Registry name (io.github.owner/name) or that server's MCP endpoint URL. Partial names match the Toolweather index. A product homepage usually will not match.
- `tool` (string): Optional tool name on that server. If the server is up but this name is absent, verdict is unsafe. Omit to judge the server only.

### `find_alternative_mcp_servers` (~202 tokens)

Find a working MCP server that does X

Search the Toolweather index for healthy MCP servers by capability, or for a replacement for one broken server. Use when check_mcp_server_health is unsafe or unknown, or when you lack a capability. Do not use it to judge one server you already chose (check_mcp_server_health) or to subscribe to later outages (watch_server). Does not call those servers and does not spend a live-check credit; unsafe rows are dropped. Returns summary, checked_at, and alternatives[] with server, url, verdict, latency_ms, and matching_tools. Counts on the Toolweather daily quota. Also callable as suggest_alternatives.

Input parameters:

- `limit` (integer): Max ranked servers to return. Integer 1-20; omitted means 5. There is no paging cursor.
- `query` (string, required): Capability phrase such as 'send email', or the registry name/URL of a server to replace. Not a tool name on Toolweather itself.

### `get_api_key` (~169 tokens)

Get a free Toolweather API key

Mint one new Toolweather API key (tw_…) for health checks and watches on this server (1,000 calls/day, 3 watches). Use it once per install, then send that key as the X-API-Key header. Do not call it every turn, and do not use it when you need a SpendGate key (spendgate_get_api_key returns sg_live_…) or a PayCheck key (paycheck_get_api_key returns pc_live_…). Takes no arguments; the caller network is the limit. Each call creates a different secret. Returns api_key once, plus daily_limit and watches_limit; later calls cannot fetch it again. A few new keys per network per day, then reuse an existing key. Health checks also work with no key at 50 calls/day.

### `watch_server` (~227 tokens)

Alert me when an MCP server breaks

Create one HTTPS webhook subscription for an indexed MCP server's verdict, auth requirement, or breaking tool-list change. Use instead of polling check_mcp_server_health. Do not use it to read health now (check_mcp_server_health) or to list subscriptions (list_watches). Requires a Toolweather key from get_api_key. The same server and webhook_url do not create a second watch; a different URL does. Three watches are free; each extra watch is $0.05 for 30 days via x402. Returns id and a one-time secret for the signature header. Toolweather later POSTs alerts to the webhook_url you supply. Does not spend the daily check quota.

Input parameters:

- `server` (string, required): Registry name (io.github.owner/name) or that server's MCP endpoint URL. Partial names match the Toolweather index. A product homepage usually will not match.
- `webhook_url` (string, required): Public https URL Toolweather will POST JSON alerts to. Private, loopback, and non-https hosts are rejected. The same URL plus server does not create a second watch.

### `list_watches` (~134 tokens)

List my server watches

List webhook subscriptions stored for the Toolweather API key on this request, including delivery health. Use to copy a watch id before unwatch_server, or to see failures. Do not use it to learn if a server is up (check_mcp_server_health) or to create a subscription (watch_server). No arguments and no quota charge. The key is the X-API-Key header; anonymous callers are rejected. Returns watches[] (id, server, webhook_url, active, disabled_reason, last_known, consecutive_failures, last_delivery) and free_tier. Does not reveal webhook secrets and does not probe servers.

### `unwatch_server` (~148 tokens)

Stop watching a server

Delete one webhook subscription for this Toolweather API key and drop its pending deliveries. Use to stop alerts or to free a watch slot. Do not use it to change a webhook URL (delete, then watch_server) or to check health (check_mcp_server_health). Pass id from list_watches, not a server name. Repeating the same id deletes nothing further and returns watch not found. Returns {deleted: id}. Requires get_api_key first. Does not contact the MCP server and does not spend check quota.

Input parameters:

- `id` (string, required): Watch id from list_watches (w_…). Not a server registry name. An unknown id returns watch not found and removes nothing else.

### `batch_check_mcp_servers` (~175 tokens)

Check up to 25 MCP servers at once

Read stored health verdicts for up to 25 MCP servers you already intend to call. Use at startup to vet that list. Do not use it for a live handshake or auth detail (check_mcp_server_health) or to discover servers by capability (find_alternative_mcp_servers). Does not contact the remotes and never spends a live-check credit. Each name still counts as one Toolweather quota call; over quota the batch is one x402 charge ($0.01). Returns summary, checked_at, and results[] with the same verdict fields as a single check. Unknown names come back verdict unknown.

Input parameters:

- `servers` (array, required): Registry names or MCP endpoint URLs already chosen, at most 25. Not a capability search. Each entry counts as one daily Toolweather call. Unknown names return verdict unknown.

### `check_api_status` (~183 tokens)

Is this API / provider down right now?

Read whether one tracked AI or developer API provider is operational, degraded, or down. Use before calling that provider, or right after 5xx, 429, or timeouts. Do not use it for an MCP server (check_mcp_server_health) or a model id (check_model_deprecation); ids come from list_providers, not URLs. Does not invoke the provider's API. Returns summary, verdict, recommended_action, open incidents, affected components, checked_at, and freshness (about every 4 minutes). Uses Upstream's quota, then $0.003 via x402, not the Toolweather check quota. Also callable as get_status.

Input parameters:

- `provider` (string, required): Lowercase id from list_providers, such as openai, anthropic, google-ai, github, or stripe. Not a URL and not an MCP registry name.

### `check_model_deprecation` (~211 tokens)

Is this model deprecated, and what replaces it?

Read whether one LLM model id is active, deprecated, or retired, plus its shutdown date and the provider's replacement. Use before hard-coding a model id, or when a call fails as model-not-found. Do not use it to see if the provider is down (check_api_status) or to list many retirements (list_recent_api_changes). Prefer model; id is only the legacy argument name. Returns summary, verdict, recommended_action (keep_using|plan_migration|switch_now|verify_with_provider), replacement, shutdown_date, evidence, and freshness. Upstream quota, then $0.003 via x402. Also callable as get_model.

Input parameters:

- `id` (string): Legacy name for the same model id. Prefer model. Not a provider id.
- `model` (string): Model id exactly as the provider API expects, such as gpt-4o or claude-3-opus-20240229. Not a provider name; that is check_api_status.

### `list_recent_api_changes` (~209 tokens)

What changed recently in AI/dev APIs?

List recent outages, deprecation-page edits, model retirements, and pricing-page edits across tracked AI and developer APIs. Use to see what changed in a window, or to explain a sudden integration error. Do not use it for one provider's live status (check_api_status) or for the once-a-day narrative (get_digest). Returns summary plus items with timestamps and source links. Upstream quota, then $0.01 via x402. Also callable as get_changes.

Input parameters:

- `kind` (string): Optional change class. Omit for every class. Not a provider id.
- `limit` (number): Max rows to return. Default 100, max 500. Not a page token.
- `provider` (string): Optional id from list_providers. Omit to span every tracked provider.
- `since` (string): ISO 8601 lower bound. Omit for the last 7 days. Not a YYYY-MM-DD digest key; that is get_digest's date.

### `list_providers` (~114 tokens)

List tracked API providers

List the AI and developer API providers Upstream tracks, each with state (operational, degraded, or outage) and checked_at. Use to choose a provider id before check_api_status. Do not use it as an MCP health check (check_mcp_server_health), as the change feed (list_recent_api_changes), as a spend score (score_spend), or as a merchant check (check_merchant). No arguments. Returns the catalog only. Does not probe providers or use the Toolweather check quota. Free.

### `get_digest` (~127 tokens)

Daily AI/dev API breaking-changes digest

Read one daily digest of AI/dev API incidents, model retirements, pricing-page edits, and breaking MCP server changes. Use once a day instead of polling list_recent_api_changes. Do not use it for a live provider check (check_api_status) or a filtered change feed (list_recent_api_changes). Omit date for the latest issue. Returns that issue's summary and items. Free: no Toolweather quota and no webhook.

Input parameters:

- `date` (string): UTC day YYYY-MM-DD of one digest issue. Omit for the latest issue. Not an ISO timestamp and not a range.

### `score_spend` (~593 tokens)

Score a planned spend before an agent pays

Score one planned payment and return approve, ask_human, or block before any tool sends money. Use before a crypto transfer, gift card, subscription, or paid API call. Do not use it for uptime (check_mcp_server_health, check_api_status), to judge whether a host or wallet is trusted (check_merchant), or to read remaining free scores (get_quota). Does not transfer funds. Returns score 0-100, verdict (approve means pay, ask_human means stop and ask a person, block means do not pay), reasons, and recommended_action. Scoring is deterministic, so rewording purpose will not change the verdict. amount is USD, not token units. api_key, when set, is a SpendGate sg_live_ key, not a Toolweather tw_ key from get_api_key. Uses SpendGate's quota (100/day anonymous, 1,000/day with an sg_live_ key), then $0.001 via x402, not the Toolweather check quota.

Input parameters:

- `agent_id` (string): Your agent or key id. Echoed back, not scored in v1.
- `amount` (number, required): Planned spend in USD, not in token atomic units. Compared with daily_budget_remaining and monthly_budget_remaining when those are set.
- `api_key` (string): Optional SpendGate key (sg_live_…). Not a Toolweather tw_ key; that key belongs in the X-API-Key header. Omit to use the anonymous IP/session cap, which can reset on rotating egress.
- `category` (string): One of status_check, api_call, saas, infra, gift_card, crypto_transfer, irreversible. Unknown categories are scored as unknown risk, not rejected.
- `currency` (string): Payment currency. Defaults to USDC. Does not convert amount; amount stays in USD.
- `daily_budget_remaining` (number): USD still available today. Amount above this is blocked. Omit if you have no daily cap to enforce.
- `endpoint` (string): Alias of merchant when the payee is an API URL. Pass one of them, not both for different payees.
- `merchant` (string): Merchant name or https endpoint URL that would receive the spend. The call does not pay this URL.
- `monthly_budget_remaining` (number): USD still available this month. Amount above this is blocked. Omit if you have no monthly cap.
- `purpose` (string): Short human description. Used as the category when category is omitted. Rewording it does not change a v1 verdict.
- `risk_hints` (array): Self-reported hints. Raising: new_payee, new_merchant, first_payment, high_velocity, mismatched_purpose, off_platform, shared_wallet. Lowering: trusted_repeat, within_policy, human_preapproved. known…

### `get_quota` (~180 tokens)

SpendGate free scores left today

Read how many free SpendGate scores this caller has left today. Use before a run of score_spend calls. Do not use it for the Toolweather health-check quota, for PayCheck's merchant-check cap (paycheck_get_quota), or to mint a key (spendgate_get_api_key or get_api_key). Does not consume a score and is not billed. Pass an sg_live_ key to read that key's cap; omit it only for the anonymous IP/session cap, which can reset on rotating egress. A tw_ key does not select this cap. Returns the remaining SpendGate count only.

Input parameters:

- `api_key` (string): Optional sg_live_ key from spendgate_get_api_key. Not a Toolweather tw_ key. Omit only to read the anonymous IP/session cap, which can reset on rotating egress.

### `spendgate_get_api_key` (~151 tokens)

Get a free SpendGate API key

Mint one new SpendGate API key (sg_live_…) for score_spend and get_quota. Use it once, then pass the secret as api_key on those tools. Do not call it every turn, and do not use it when you need a Toolweather key for health checks and watches (get_api_key returns tw_…). No required arguments. Each call creates a different secret. Returns that secret once. Not billed, and not drawn from the Toolweather quota. label is an optional stored note, not an auth secret.

Input parameters:

- `label` (string): Optional note stored beside the new sg_live_ key, max 80 characters. Not a secret and not a Toolweather key.

### `check_merchant` (~448 tokens)

Check a merchant before an agent pays

Decide whether an autonomous agent should pay one merchant, host, or wallet, and return trusted, unknown, suspicious, or block. Use immediately before a payment, a checkout redirect, or a transfer to a new 0x address. Do not use it to send money, to score a dollar amount (score_spend), or to read remaining checks (paycheck_get_quota). Does not sign transactions or hold wallet keys. target is a bare domain, an https URL, or a 0x address with 40 hex characters. amount_usd and category are ignored, so changing them does not change the verdict. trusted is only the published allowlist of known AI and developer APIs on https port 443. A new or random domain is never trusted. A wallet is never trusted. If the URL contains an embedded 0x address, this scores the host only; pass the bare address to score the wallet. api_key, when set, is a PayCheck pc_live_ key, not a Toolweather tw_ key from get_api_key and not a SpendGate sg_live_ key. Uses PayCheck's quota (100/day anonymous or an anon: bundle client, 1,000/day with a pc_live_ key or a hex Toolweather bundle client), then $0.001 via x402, not the Toolweather check quota. The same target for the same caller is idempotent for 60 seconds and does not consume a second check.

Input parameters:

- `amount_usd` (number): Ignored by the scorer. Sending a different amount cannot change the verdict. Not a SpendGate amount.
- `api_key` (string): Optional PayCheck key (pc_live_…). Not a Toolweather tw_ key and not a SpendGate sg_live_ key. Omit to use the anonymous or bundle-client allowance.
- `category` (string): Ignored by the scorer. Do not put instructions or a purpose in this field. Not a SpendGate category.
- `target` (string, required): Domain, https URL, or 0x wallet (40 hex characters) to score before paying. Not a dollar amount (score_spend) and not an MCP registry name.

### `paycheck_get_quota` (~217 tokens)

PayCheck free checks left today

Read how many free PayCheck merchant checks this caller has left today. Use before a run of check_merchant calls, or after an HTTP 402. Do not use it for SpendGate's free-score cap (get_quota), the Toolweather health-check quota, or to mint a key (paycheck_get_api_key, spendgate_get_api_key, or get_api_key). Does not consume a check and is not billed. Pass a pc_live_ key to read that key's cap. A tw_ key does not select this cap. A hex x-tw-bundle-client (Toolweather key hash) is the 1,000/day tier; an anon: bundle client stays at 100/day. Returns subject_kind, limit, used, remaining, and resets_at for PayCheck only.

Input parameters:

- `api_key` (string): Optional pc_live_ key from paycheck_get_api_key. Not a Toolweather tw_ key and not an sg_live_ key. Omit only to read the anonymous or bundle-client allowance.

### `paycheck_get_api_key` (~148 tokens)

Get a free PayCheck API key

Mint one new PayCheck API key (pc_live_…) for check_merchant and paycheck_get_quota. The key raises the merchant-check allowance from 100 to 1,000 per UTC day. Use it once, then pass the secret as api_key on those tools. Do not call it every turn, and do not use it when you need a Toolweather key (get_api_key returns tw_…) or a SpendGate key (spendgate_get_api_key returns sg_live_…). No arguments. Each call creates a different secret, returned once. Not billed, and not drawn from the Toolweather quota. Limited to 10 new keys per caller IP per UTC day.

## Diagnostics

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

## Score history

- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 62
- 2026-10-20: 61
- 2026-10-19: 61
- 2026-10-18: 60
- 2026-10-17: 60
- 2026-10-16: 59
- 2026-10-15: 60

## Common questions

### What is the Toolweather MCP server?

Toolweather is an MCP server listed in the public MCP registry as io.github.toolweather/toolweather. MCP health (~2k servers) + API status & model deprecations (~40 APIs). One suite for agents. This page covers its hosted endpoint (https://toolweather.toolweather.workers.dev/mcp).

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

Toolweather scores 63 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 Toolweather MCP server expose?

Toolweather exposes 18 tools: check_mcp_server_health, find_alternative_mcp_servers, get_api_key, watch_server, list_watches, and 13 more. Their descriptions and schemas cost roughly 3,997 tokens of context every time the server is loaded.

### Does the Toolweather MCP server require authentication?

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

### Is the Toolweather MCP server still maintained?

Toolweather 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://toolweather.toolweather.workers.dev/mcp
- Authorisation metadata: https://toolweather.toolweather.workers.dev/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/toolweather/toolweather
- Website: https://toolweather.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/toolweather-toolweather/toolweather.xml
- Changelog JSON feed: https://verifymcp.io/servers/toolweather-toolweather/toolweather.json
- HTML version of this page: https://verifymcp.io/servers/toolweather-toolweather/toolweather