Skip to content
Versyka logo

Versyka MCP server

Which MCP servers are Versyka's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Versyka

Whose server it is
  • Registry namecom.versyka/versykaverified in the MCP registry

The registry name sits under versyka.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools7
  • Server calls itselfversyka
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 827 ms.

Should an agent connect itNot proven either way yet
  • Its tools do Scan repositories for outdated and vulnerable packages, but not Open pull requests for SDK upgrades only after tests pass.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "Scan repositories for outdated and vulnerable packages", the likely first call is check_dependencies.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer370 ms
  • Space in an agent's context≈ 1,127 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 98 of 100
  • Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 7

What an agent can do with it

  • not sure · Rewrite code calls affected by breaking SDK changes
  • cannot · Open pull requests for SDK upgrades only after tests pass
  • can do · Scan repositories for outdated and vulnerable packages

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-27
  • 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 and PyPI. Returns each SDK's current…

  • find_retired_models

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

  • 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 shutdown date, status, replacement and…

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "versyka": {
      "type": "http",
      "url": "https://www.versyka.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http versyka https://www.versyka.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://www.versyka.com/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.