Is this model or API still safe to call? Retirement and breaking change dates, with the fix.
MCPpedia last refreshed this data
io.github.ReignVentures/apiwatch is an MCP server that is this model or API still safe to call? Retirement and breaking change dates, with the fix. Its tool list has not been published yet over http, requires no API key, and scores 92/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-reignventures-apiwatch": {
"args": [
"-y",
"@modelcontextprotocol/server-everything"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is this model or API still safe to call? Retirement and breaking change dates, with the fix.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @modelcontextprotocol/server-everything against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
deja-vu: local memory over the session histories of forty-three coding agents.
MCP WordPress Remote proxy server
专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
Searchable football data provider documentation for AI coding agents. Like Context7 for football data.
MCP Security Weekly
Get CVE alerts and security updates for io.github.ReignVentures/apiwatch and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
gpt-4 does not match gpt-4o), follows constants, reads notebooks, and separates real uses from entries in model lists.tools/list and get told when it drifts, no spec required.The feed holds 140 reviewed changes, each checked against the vendor's own page.
Next dates (everything in the next 180 days):
name: apiwatch
on: [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:
- 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 pu