# apiwatch

> Is this model or API still safe to call? Retirement and breaking change dates, with the fix.

- name: io.github.ReignVentures/apiwatch
- version: 1.1.0
- connection class: R0 (autonomous)
- trust: 97/100
- quality: 100/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.ReignVentures%2Fapiwatch
- tools: https://api.protogrid.dev/v1/servers/io.github.ReignVentures%2Fapiwatch/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "apiwatch": {
      "type": "http",
      "url": "https://apiwatch.reignventures.co/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-97% +updated-12d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 100/100 (strong)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 3600000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 7 of 7 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,291 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 2 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 7, about 1,291 tokens to load them all
- tool set hash: 76f2eb3a936fd57326f873b3926f58f0
- tools last changed: 2026-10-21T23:26:57.083Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.ReignVentures/apiwatch.svg)](https://protogrid.dev/servers/io.github.ReignVentures/apiwatch)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-21 `mcp_server_changes` added
  - Before you rely on a public MCP server's tools, ask whether apiwatch saw them change: tools removed or renamed, new required parameters, rewritten descriptions, changed safety hints. Give a watched server's slug, URL or registry name. Returns a one line answer and the confirmed changes in the last N days (default 90, max 365), newest first, with flags worth a look. Observations only: no changes is not a statement that a server is safe. Never includes tool description text.
- 2026-10-21 `list_watched_mcp_servers` added
  - List the public MCP servers whose tools apiwatch checks every 6 hours (tools/list only, no login, no tool calls), with each one's status (answering, needs a login, not reachable), tool count, last check and last observed change. Use it to see which servers mcp_server_changes can answer about. Returns no tool descriptions.

Full history: https://api.protogrid.dev/v1/servers/io.github.ReignVentures%2Fapiwatch/changes

## Remotes

- https://apiwatch.reignventures.co/mcp (streamable-http, auth none, reachable true, uptime30d 0.9701493)

## Packages

_none_

## Tools (7)

- `check_identifiers`: Look up many identifiers at once before shipping code: model ids, API endpoints (/v1/assistants), MCP tool names, SDK methods or field names. For each one, a one line answer and the ids of matching records, plus the records themselves. A record scoped to some code (for example only repos that depend on a given SDK major version) is returned with that scope spelled out, never as an unconditional hit. Max 100 identifiers.
- `check_model`: Look up one AI model id (for example gpt-4o-2024-05-13 or claude-sonnet-4-5) in apiwatch's reviewed feed of vendor changes before you use it in code. Returns a one line answer (when it stops working, changes behavior, or its deprecation key date) and each matching record with the date, what to do and the replacement, and links to the record and the vendor's source. "No record" means apiwatch has no record for it, not that it is safe. Records that apply only in some repos or files say so in scope.
- `get_record`: Get one apiwatch record in full, as published: what changes, what to do, the strings to search for, ids it does not cover, where it applies, the vendor source and when it was reviewed. Use an id from another tool's result.
- `list_upcoming`: List the dated changes in apiwatch's feed from today forward, soonest first: model retirements, breaking API changes, silent behavior changes and deprecation key dates. Use it to plan migrations. Optionally limit to the next N days (default 90, max 365) or one vendor. Max 50 records.
- `list_watched_mcp_servers`: List the public MCP servers whose tools apiwatch checks every 6 hours (tools/list only, no login, no tool calls), with each one's status (answering, needs a login, not reachable), tool count, last check and last observed change. Use it to see which servers mcp_server_changes can answer about. Returns no tool descriptions.
- `mcp_server_changes`: Before you rely on a public MCP server's tools, ask whether apiwatch saw them change: tools removed or renamed, new required parameters, rewritten descriptions, changed safety hints. Give a watched server's slug, URL or registry name. Returns a one line answer and the confirmed changes in the last N days (default 90, max 365), newest first, with flags worth a look. Observations only: no changes is not a statement that a server is safe. Never includes tool description text.
- `search_changes`: Search apiwatch's feed of reviewed vendor changes by text: a case-insensitive match on each record's summary, vendor and signatures (the strings to look for in code). Use it when you know a product or feature name but not the exact id. Newest key date first; default 20 results, max 50.