Versyka

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.versyka/versyka and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 15 Oct 2026. Not supplied by the maker.

• check_dependencies

  Check 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 a

• find_retired_models

  Scan source and config files for AI model IDs that the vendor (OpenAI, Anthropic, Google Gemini, Mistral, Cohere) has retired or scheduled for retirement. Exact matches only, including Bedrock, Vertex

• lookup_model

  Is this AI model ID retired or scheduled for retirement? Accepts plain IDs and gateway spellings (e.g. openai/gpt-4-0613, anthropic.claude-3-sonnet-20240229-v1:0, claude-3-opus@20240229). Returns the

• list_model_retirements

  The AI model retirement calendar: model IDs with their shutdown dates, replacements and sources, soonest first. Filter by vendor or by how many days ahead to look.

• get_sdk_versions

  The 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.

• list_migration_guides

  Versyka's step-by-step SDK migration guides (OpenAI, Anthropic, Google Gemini, AWS, Stripe, Firebase, Slack, Twilio, Auth0, Pinecone), optionally filtered by package name.

• get_migration_guide

  One 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.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.