Versyka MCP Server

by versyka Your server? Claim it

not responding

Versyka is listed as active in the registry but did not answer our last check. It exposes 7 tools.

Find retiring AI models and outdated API SDKs in your code, with dates, replacements and guides.

Uptime history 24 days of history · worst day 0%

24 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

99 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.

25 Oct a tool description was rewritten find_retired_models

25 Oct a tool changed the parameters it asks for list_model_retirements

Versyka does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://www.versyka.com/api/mcp

~/.codex/config.toml

[mcp_servers.versyka]
url = "https://www.versyka.com/api/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

migration

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.

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.

dependencies

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 spec, latest version, release-notes link and a Versyka migration guide when one exists.

lookup

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 source, or that no retirement is listed.

model

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.

retired

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, Vertex AI, LiteLLM and OpenRouter spellings. Returns each model's shutdown date, days left, the vendor's recommended replacement, the source page and the file:line locations.

sdk

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.

Endpoints

URL	Transport	State	Latency	Checked
https://www.versyka.com/api/mcp	streamable-http	answering	99 ms	11 min ago

Alternatives to Versyka

same job, measured the same way

llmshift

by dechuks-hub

Find retiring LLM calls in code and test the replacement model on real traffic before switching.

491 installs/wk local only

Sfdx Retirement Lint

by jmshinhwa

Finds retired API versions and removed sfdx force:* commands in your DX repo before a deploy or a CI

125 installs/wk local only

Kijito

by kijito

Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.

answering

Security Engineer

by guardbee

Fix GuardBee AI Security Engineer findings in your repo with your coding agent, then verify

local only

Vinv

by vinvai

Vinv runs, tests, and finds issues in your services — with zero code changes.

66 installs/wk local only

Attest by DataHubz (verify only)

by datahubz

Verify Attest agreements, stamp codes, receipts, proofs and SHA-256 fingerprints, with no sign-in.

1 tools answering

Errata

by formachines

Sandbox-verified fixes where AI models write outdated code for PyPI and npm libraries

749 installs/wk local only

Reactable Codebase Readiness Assessments

by reactable-io

Scores your code across 12 areas, with findings, fix prompts, and re-assessment in your AI agent

answering

Versyka — questions

Answers built from our own checks of this server.

What can Versyka do?

It exposes 7 tools, read directly from the server on our last check. Among them: check_dependencies, find_retired_models, get_migration_guide, get_sdk_versions, list_migration_guides, list_model_retirements and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Versyka working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 99 ms. The bar chart above shows every period we have measured.

The registry lists Versyka as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Versyka?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Versyka need an API key?

No. Versyka completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.