apiwatch

io.github.ReignVenturesPublished by GitHub account ReignVenturesv1.1.0Updated Oct 28, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Lets an assistant check AI model ids, API endpoints and MCP tools against apiwatch's reviewed feed of vendor retirements, breaking changes and deprecations.

What you can do
  • Look up one model id and get its retirement or behavior-change date with the fix
  • Check many identifiers at once: model ids, endpoints, MCP tool names, SDK methods, field names
  • List dated upcoming changes soonest first, filtered by days ahead or vendor
  • Search the change feed by text and read a single record in full
  • List watched public MCP servers and see whether their tools were removed, renamed or changed
When to use it
Useful when writing or reviewing code that names AI models, API endpoints or MCP tools, and when planning migrations around vendor retirement dates. Also handy before relying on a public MCP server whose tools may have changed.
Requirements
Remote Streamable HTTP endpoint; no install, account or API key. Network access to the apiwatch host is required.
Before you install
Answers come only from apiwatch's reviewed records; a "no record" result means unknown, not safe. Some records apply only to certain repos or files, so read each record's scope. Queries are sent to a third-party service, though it states it stores nothing it is sent.

Installation

In SourceWeft

  1. Open apiwatch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ReignVentures%2Fapiwatch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

apiwatch

Know when an API, model, or MCP server you depend on changes, and exactly which lines of your code it breaks.

Vendors retire models, rename MCP tools, and change API behavior on a schedule you don't control. Most of these changes are announced in a changelog nobody on your team reads. apiwatch reads them for you, and its GitHub Action points at the exact lines they land on, before the shutoff date.

  • The feed: reviewed records of breaking, silent, and deprecation changes from OpenAI, Anthropic, Google, Stripe, Twilio, Notion, Atlassian, GitHub, xAI, and more. Every record cites the vendor's own page and is rechecked daily. Browse it at apiwatch.reignventures.co (Atom and JSON Feed included).
  • The scan: finds the call sites each change lands on in your repo. It is token aware (gpt-4 does not match gpt-4o), follows constants, reads notebooks, and separates real uses from entries in model lists.
  • The brief: for each hit, what changed, where, a suggested fix, and acceptance criteria you can hand to a coding agent.
  • The probe: baseline a live JSON endpoint or an MCP server's tools/list and get told when it drifts, no spec required.

What it caught

The feed holds 135 reviewed changes, each checked against the vendor's own page.

  • By vendor: Google 33, Stripe 30, OpenAI 26, Anthropic 17, Notion MCP 8, Atlassian Rovo MCP 4, GitHub MCP Server 4, Notion 4, xAI 4, Twilio 3, Greenhouse 1, MCP specification 1
  • By severity: breaking 100, silent 25, deprecation 10

Next dates (everything in the next 180 days):

GitHub Action

yaml
name: apiwatchon: [push, pull_request]jobs:  scan:    runs-on: ubuntu-latest    permissions: { contents: read, pull-requests: write }    steps:      - uses: actions/checkout@v4      - uses: ReignVentures/apiwatch@v1        with:          fail-on-breaking: "true"   # fail CI when a breaking or silent change touches your code          comment: "true"            # keep one up to date report comment on pull requests          only-changed: "true"       # on PRs, gate only on the files the PR changes

Every run writes a short report to the job summary: which changes touch your code, how severe, whether the date is past or coming, and links to each location. Add SARIF upload to see hits as code scanning annotations:

yaml
      - uses: github/codeql-action/upload-sarif@v3        if: always()        with: { sarif_file: apiwatch.sarif }

Tip: add a schedule: trigger (for example daily) so you hear about new changes even when nobody is pushing.

CLI

bash
pip install git+https://github.com/ReignVentures/apiwatchapiwatch scan . --fail-on-breaking --markdown report.mdapiwatch probe docs "mcp:stdio:npx -y @modelcontextprotocol/server-everything"apiwatch probe docs mcp:https://example.com/mcp --header 'Authorization: Bearer $TOKEN' --fail-on-drift

Scans run locally with no network calls. Your code never leaves your machine or your CI runner.

To leave generated or copied files out of a scan, add a .apiwatchignore file at the repository root: one glob per line (agents/*.json), a trailing / for a directory (generated/), # for comments. Translation folders (locales/, i18n/) are skipped by default.

MCP server

AI agents can ask the feed directly while they work: does this model id or API have a published change, when, and what replaces it? One public URL, no install, no account: https://apiwatch.reignventures.co/mcp (Streamable HTTP, both the 2026-07-28 and the earlier initialize protocol eras).

bash
claude mcp add --transport http apiwatch https://apiwatch.reignventures.co/mcp

Tools: check_model, check_identifiers, list_upcoming, search_changes, get_record. It answers only from the reviewed records the site publishes, stores nothing it is sent, and says "no record" (never "safe") for an id it doesn't know. Setup for other clients: https://apiwatch.reignventures.co/mcp-server

Two more tools, list_watched_mcp_servers and mcp_server_changes, answer from apiwatch's history of observed tool changes on some public MCP servers (https://apiwatch.reignventures.co/mcp-servers/): tools removed or renamed, new required parameters, rewritten descriptions, changed hints. They never return a server's own tool descriptions.

How records are verified

A record is published only after a reviewer that did not write it checks every field against the vendor's primary source, and an automated check confirms the quoted evidence is still on that page. The full rules are in docs/REVIEW.md. If a vendor edits or removes the page, the record comes off the site until it is reviewed again.

Found a change we missed, or a record that's wrong? Open an issue with a link to the vendor's page.

apiwatch Pro

Pro watches every repository in your GitHub organization each night, with nothing to add to your workflows, and opens an issue when a new change lands on your code. $19 per month. See how Pro works.

License

MIT. Built by Reign Ventures LLC.

Source: README.md at commit 30c7bf1

Tools

7

check_model

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.

Parametersmodelrequired

check_identifiers

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.

Parametersidentifiersrequired

list_upcoming

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.

Parametersdaysvendor

search_changes

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.

Parameterslimitqueryrequiredvendor

get_record

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.

Parametersidrequired

list_watched_mcp_servers

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.

Takes no parameters.

mcp_server_changes

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.

Parametersdaysserverrequired

Version history

2
  1. v1.1.0LatestOct 26, 2026
  2. v1.0.0Oct 21, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts