since-cutoff MCP server
io.github.MohammadHijjawi97/since-cutoff·v0.5.0·1 starsWhich Python library APIs changed after your model's training cutoff (static diff, no model calls)
not scanned yet
1 stars112 downloads/wk
Reviews
Write oneNobody has reviewed since-cutoff yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
since-cutoff tools
No tool declarations could be read from the package source. They show once the server is installed.
How since-cutoff compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 90% of 4,460 AI and agents servers
- GitHub stars
- 1
- more than 50% of 2,711 AI and agents servers
- Downloads a week
- 112
- more than 66% of 1,538 AI and agents servers with a package
Release history: 6 versions in the registry since 2026-09-27, latest 2026-09-28, typically several a day.
Install since-cutoff in Claude Code, Cursor or VS Code
claude mcp add since-cutoff -- uvx since-cutoff
What the publisher says
From the since-cutoff repository's README, as published. We do not edit it. Read it on GitHub
since-cutoff
<!-- mcp-name: io.github.MohammadHijjawi97/since-cutoff -->
For Python projects written with a coding agent: since-cutoff finds the dependency APIs that changed after the model's training cutoff, measures which of them the model gets wrong, and fixes those with short AGENTS.md notes, each checked by a type checker or taken directly from the API diff.
English | 简体中文 | Español | Français
The problem
Every model has a training cutoff; your lockfile keeps moving. When a library changes its public API after the cutoff, a model that learned the old version keeps writing the old calls. Some of that code fails at import or call time. Some still runs, because the old path is only deprecated.
A few of the changes since-cutoff scan finds for Claude Sonnet 4.5 (training cutoff July
which pins six of its nine dependencies to current releases (for the other three, which are unpinned, the tool uses the latest release):
- in the sample project,
In that project, 7 of 9 dependencies changed their public API after the cutoff. The static diff flags 317 breaking changes and 23 new deprecations; some are internals, which the probes skip.
It is not one model or one vendor. Across 36 widely used Python AI libraries and 21 models from OpenAI, Anthropic, Google, xAI, DeepSeek, Qwen, Moonshot and Mistral, even the newest model tested (Claude Opus 5.5, June 2026 cutoff) predates a public API break in 20 of the 36 (full results):
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
since-cutoff: common questions
- Is since-cutoff MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the since-cutoff safety report
- How do I install since-cutoff?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does since-cutoff need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is since-cutoff maintained?
- The last commit was 38 days ago (2026-09-27). The latest release is v0.5.0.
- What can I use instead of since-cutoff?
- Servers from other publishers that do the same job: Ausca MCP server and AKShare MCP server.
- How does since-cutoff compare with other AI and agents MCP servers?
- safety score 92/100 (higher than 90% of 4,460 AI and agents servers); github stars 1 (more than 50% of 2,711 AI and agents servers); downloads a week 112 (more than 66% of 1,538 AI and agents servers with a package). Full comparison.
Alternatives to since-cutoff
Same job from other publishers: the closest match first, then the best rated.
