Okapi
bot.okapiPublished by okapi.botOfficial publisherv1.1.0Updated Nov 7, 2026
Breaking changes of third-party APIs: check your code's API calls before they break.
Overview
Okapi is a remote MCP server that lets an assistant check your code's third-party API calls for breaking changes before they break.
- What you can do
- Check the API calls in your code against breaking changes in third-party APIs
- Run a call check that works without an API key
- Use a free API key to access the full checking capability
- When to use it
- Useful when you depend on third-party APIs and want to catch upcoming breaking changes in your code's calls before they cause failures, for example during upgrades or routine dependency review.
- Requirements
- A remote streamable HTTP endpoint at mcp.okapi.bot. An Authorization header carrying a free API key from the provider's API key page is needed for full use; the call check reportedly works without one.
Installation
In SourceWeft
- Open Okapi in the dashboard and add it to a workspace.
- 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/bot.okapi%2Fokapi/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"okapi": {
"type": "http",
"url": "https://mcp.okapi.bot/mcp"
}
}
}Tools
0Version history
1- v1.1.0LatestNov 7, 2026
Score
67% 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
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.