Developer Tools
versyka.com
A developer tool that checks dependency manifests and SDK versions while scanning for retired or soon-to-be-retired AI model IDs.
ENDPOINT 1
https://www.versyka.com/api/mcp
MCP server metadata
- Name
- versyka
- Version
- 1.0.0
Versyka tracks breaking changes in third-party API SDKs (OpenAI, Anthropic, Google Gemini, Stripe, AWS, Twilio and about 40 more on npm and PyPI) and AI model retirement dates from the vendors' own deprecation pages. Use check_dependencies when the user has a package.json, requirements.txt, pyproject.toml or Pipfile; find_retired_models on source files before changing or shipping code that calls an AI model; lookup_model for one model ID; get_migration_guide for step-by-step upgrade instructions with before and after code. Cite the source URLs the tools return.
Known tools 7
check_dependenciesCheck a dependency manifest (package.json, requirements.txt, pyproject.toml or Pipfile) for third-party API SDKs that are major versions behind, deprecated or replaced, against the live npm registry and PyPI.
Inferred read-onlyfind_retired_modelsScan source and config files for AI model IDs that the vendor (OpenAI, Anthropic, Google Gemini, Mistral, Cohere) has retired or scheduled for retirement.
Inferred read-onlylist_model_retirementsThe AI model retirement calendar: model IDs with their shutdown dates, replacements and sources, soonest first.
Inferred read-onlyget_sdk_versionsThe latest version of an npm or PyPI package, whether it is deprecated, its release-notes link, the API vendor it belongs to and a Versyka migration guide when one exists.
Inferred read-onlylist_migration_guidesVersyka's step-by-step SDK migration guides (OpenAI, Anthropic, Google Gemini, AWS, Stripe, Firebase, Slack, Twilio, Auth0, Pinecone), optionally filtered by package name.
Potential side effectsget_migration_guideOne migration guide as Markdown: what changed, each step with before and after code, how to find every affected call, how to test, and the vendor sources it is based on.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.versyka]
url = "https://www.versyka.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"versyka": {
"type": "http",
"url": "https://www.versyka.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: versyka
Remote MCP URL: https://www.versyka.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"versyka": {
"url": "https://www.versyka.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"versyka": {
"type": "http",
"url": "https://www.versyka.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "versyka",
"transport": "streamable-http",
"url": "https://www.versyka.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.