apiwatch

io.github.ReignVentures由 GitHub 账号 ReignVentures 发布v1.1.0更新于 Oct 28, 2026

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

已验证Streamable HTTP可网页运行开发者工具AI 与机器学习

概览

AI 生成的概览

让助手对照 apiwatch 经审核的厂商变更记录，核查 AI 模型 ID、API 端点与 MCP 工具的下线、破坏性变更和弃用信息。

可以做什么
  • 查询单个模型 ID，返回其停用或行为变更日期及应对方式
  • 批量核查模型 ID、API 端点、MCP 工具名、SDK 方法与字段名
  • 按日期列出即将发生的变更，可按天数或厂商筛选
  • 按文本搜索变更记录，并读取单条记录的完整内容
  • 列出被监测的公开 MCP 服务器，查看其工具是否被删除、改名或改动
适用场景
适合在编写或审查涉及 AI 模型、API 端点或 MCP 工具的代码时使用，也适合围绕厂商停用日期规划迁移。在依赖某个公开 MCP 服务器之前，也可先确认其工具是否发生变化。
运行要求
远程 Streamable HTTP 端点，无需安装、账号或 API 密钥；需要能访问 apiwatch 主机的网络。
安装前请注意
回答仅来自 apiwatch 经审核的记录，“无记录”表示未知而非安全。部分记录只适用于特定仓库或文件，需留意每条记录的适用范围。查询内容会发送给第三方服务，其声明不保存所收到的内容。

安装

在 SourceWeft 中

  1. 打开 控制台中的 apiwatch，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.ReignVentures%2Fapiwatch/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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.

来源：README.md，提交 30c7bf1

工具

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.

输入参数model必填

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.

输入参数identifiers必填

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.

输入参数daysvendor

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.

输入参数limitquery必填vendor

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.

输入参数id必填

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.

无需输入参数。

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.

输入参数daysserver必填

版本历史

2
  1. v1.1.0最新Oct 26, 2026
  2. v1.0.0Oct 21, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分