# apiwatch (remote · apiwatch.reignventures.co)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `apiwatch.reignventures.co`: 80/100 (this document), [markdown](https://verifymcp.io/servers/reignventures-apiwatch/apiwatch.md), [page](https://verifymcp.io/servers/reignventures-apiwatch/apiwatch)

## Channel facts

- Endpoint: `https://apiwatch.reignventures.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-05.

- **Endpoint Security**: 80/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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 937 tokens (~133/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 apiwatch MCP server?

apiwatch is a hosted endpoint at https://apiwatch.reignventures.co/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 reignventures-apiwatch 'https://apiwatch.reignventures.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "reignventures-apiwatch": {
      "url": "https://apiwatch.reignventures.co/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.reignventures-apiwatch]
url = "https://apiwatch.reignventures.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reignventures-apiwatch": {
      "type": "remote",
      "url": "https://apiwatch.reignventures.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add reignventures-apiwatch --url 'https://apiwatch.reignventures.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  reignventures-apiwatch:
    url: "https://apiwatch.reignventures.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "reignventures-apiwatch": {
      "Transport": "http",
      "Url": "https://apiwatch.reignventures.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add reignventures-apiwatch -t streamable-http -u 'https://apiwatch.reignventures.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "reignventures-apiwatch": {
      "type": "http",
      "url": "https://apiwatch.reignventures.co/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-11-04 (score 80, +1)

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

### 2026-11-01 (score 79, +1)

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

### 2026-10-30 (score 78, +1)

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

### 2026-10-28 (score 77, +1)

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

### 2026-10-26 (score 76, +1)

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

### 2026-10-24 (score 75, +1)

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

### 2026-10-22 (score 74, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 673 → 937
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “list_watched_mcp_servers”
- [functional] New tool “mcp_server_changes”

### 2026-10-21 (score 73)

First indexed and scored.

## MCP tools (7)

### `check_model` (~150 tokens)

Check an AI model id

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.

Input parameters:

- `model` (string, required): The model id as it appears in code

Output parameters:

- `answer` (string)
- `found` (boolean)
- `matches` (array)
- `model` (string)
- `next_step` (string)
- `record_urls` (array)
- `truncated` (boolean)

### `check_identifiers` (~114 tokens)

Check many 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.

Input parameters:

- `identifiers` (array, required): Identifiers as they appear in code

Output parameters:

- `next_step` (string)
- `record_urls` (array)
- `records` (array)
- `results` (array)
- `truncated` (boolean)

### `list_upcoming` (~112 tokens)

List upcoming changes

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.

Input parameters:

- `days` (integer): How many days ahead, default 90
- `vendor` (string): Only this vendor, for example OpenAI, Anthropic, Google, Stripe

Output parameters:

- `from` (string)
- `next_step` (string)
- `record_urls` (array)
- `records` (array)
- `to` (string)
- `total` (integer)
- `truncated` (boolean)
- `vendor` (string)

### `search_changes` (~113 tokens)

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.

Input parameters:

- `limit` (integer): Default 20
- `query` (string, required)
- `vendor` (string): Only this vendor, for example OpenAI, Anthropic, Google, Stripe

Output parameters:

- `next_step` (string)
- `query` (string)
- `record_urls` (array)
- `records` (array)
- `total` (integer)
- `truncated` (boolean)
- `vendor` (string)

### `get_record` (~93 tokens)

Get one 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.

Input parameters:

- `id` (string, required): Record id, for example openai-2026-10-23-gpt-4o-2024-05-13

Output parameters:

- `found` (boolean)
- `next_step` (string)
- `record` (object)
- `record_urls` (array)

### `list_watched_mcp_servers` (~82 tokens)

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.

Output parameters:

- `index_url` (string)
- `note` (string)
- `servers` (array)
- `total` (integer)

### `mcp_server_changes` (~154 tokens)

Recent tool changes on an MCP server

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.

Input parameters:

- `days` (integer): How many days back, default 90
- `server` (string, required): Slug (context7), URL (https://mcp.context7.com/mcp) or registry name

Output parameters:

- `answer` (string)
- `changes` (array)
- `days` (integer)
- `from` (string)
- `index_url` (string)
- `notes` (array)
- `query` (string)
- `server` (object|null)
- `to` (string)
- `truncated` (boolean)
- `watched` (boolean)

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73

## Common questions

### What is the apiwatch MCP server?

apiwatch is an MCP server listed in the public MCP registry as io.github.ReignVentures/apiwatch. Is this model or API still safe to call? Retirement and breaking change dates, with the fix. This page covers its hosted endpoint (https://apiwatch.reignventures.co/mcp).

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

apiwatch scores 80 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 apiwatch MCP server expose?

apiwatch exposes 7 tools: check_model, check_identifiers, list_upcoming, search_changes, get_record, and 2 more. Their descriptions and schemas cost roughly 818 tokens of context every time the server is loaded.

### Does the apiwatch MCP server require authentication?

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

### Is the apiwatch MCP server still maintained?

apiwatch is still listed as active in the MCP registry. We last reached this channel on 5 November 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://apiwatch.reignventures.co/mcp
- Repository: https://github.com/ReignVentures/apiwatch
- Website: https://apiwatch.reignventures.co/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/reignventures-apiwatch/apiwatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/reignventures-apiwatch/apiwatch.json
- HTML version of this page: https://verifymcp.io/servers/reignventures-apiwatch/apiwatch