apiwatch
REMOTE · APIWATCH.REIGNVENTURES.CO
Is this model or API still safe to call? Retirement and breaking change dates, with the fix.
Available components
Last scanned (21 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 673 → 937 ▼ functional
- 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” functional
- 21 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://apiwatch.reignventures.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apiwatch.reignventures.co | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | fd0ab0fda9c638a813fd72afbc19ccc1 |
| SANs: apiwatch.reignventures.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apiwatch.reignventures.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| reignventures.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apiwatch.reignventures.co/mcp | Verified | 200 | |
| http (plaintext) | http://apiwatch.reignventures.co/mcp | HTTPS enforced | 301 | https://apiwatch.reignventures.co/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_identifiers Check many identifiers ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifiers | array | yes | Identifiers as they appear in code |
| Name | Type | Req | Description |
|---|---|---|---|
| next_step | string | yes | – |
| record_urls | array | yes | – |
| records | array | yes | – |
| results | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
check_model Check an AI model id ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | The model id as it appears in code |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| found | boolean | yes | – |
| matches | array | yes | – |
| model | string | yes | – |
| next_step | string | yes | – |
| record_urls | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
get_record Get one record ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Record id, for example openai-2026-10-23-gpt-4o-2024-05-13 |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| next_step | string | yes | – |
| record | object | – | – |
| record_urls | array | yes | – |
No examples provided.
list_upcoming List upcoming changes ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days ahead, default 90 |
| vendor | string | – | Only this vendor, for example OpenAI, Anthropic, Google, Stripe |
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| next_step | string | yes | – |
| record_urls | array | yes | – |
| records | array | yes | – |
| to | string | yes | – |
| total | integer | yes | – |
| truncated | boolean | yes | – |
| vendor | string | yes | – |
No examples provided.
list_watched_mcp_servers List watched MCP servers ~82
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| index_url | string | yes | – |
| note | string | yes | – |
| servers | array | yes | – |
| total | integer | yes | – |
No examples provided.
mcp_server_changes Recent tool changes on an MCP server ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days back, default 90 |
| server | string | yes | Slug (context7), URL (https://mcp.context7.com/mcp) or registry name |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| changes | array | yes | – |
| days | integer | yes | – |
| from | string | yes | – |
| index_url | string | yes | – |
| notes | array | yes | – |
| query | string | yes | – |
| server | object|null | yes | – |
| to | string | yes | – |
| truncated | boolean | yes | – |
| watched | boolean | yes | – |
No examples provided.
search_changes Search changes ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 20 |
| query | string | yes | – |
| vendor | string | – | Only this vendor, for example OpenAI, Anthropic, Google, Stripe |
| Name | Type | Req | Description |
|---|---|---|---|
| next_step | string | yes | – |
| query | string | yes | – |
| record_urls | array | yes | – |
| records | array | yes | – |
| total | integer | yes | – |
| truncated | boolean | yes | – |
| vendor | string | yes | – |
No examples provided.
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.
remote · apiwatch.reignventures.co
claude mcp add --transport http reignventures-apiwatch 'https://apiwatch.reignventures.co/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.