Versyka
REMOTE · WWW.VERSYKA.COM
Find retiring AI models and outdated API SDKs in your code, with dates, replacements and guides.
Available components
Last scanned (6 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 803 tokens (~114/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://www.versyka.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.versyka.com | CN=YR1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | 59207e2769e7685b031f1c045cf618fd33e |
| SANs: www.versyka.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.versyka.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| versyka.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.versyka.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.versyka.com/api/mcp | HTTPS enforced | 308 | https://www.versyka.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_dependencies Check API SDK versions ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Check every package, not just third-party API SDKs. |
| file_name | string | – | The file name, e.g. requirements.txt. Helps detect the format. |
| manifest | string | yes | The full text of the manifest file. |
No output schema declared.
No examples provided.
find_retired_models Find retired AI models in code ~112
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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to scan, each with its repository-relative path and full text. |
No output schema declared.
No examples provided.
get_migration_guide Get a migration guide ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The guide slug from list_migration_guides, e.g. openai-python-v0-to-v1. |
No output schema declared.
No examples provided.
get_sdk_versions Latest SDK version ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Which registry: npm (JavaScript/TypeScript) or pypi (Python). |
| package | string | yes | Package name, e.g. openai, @anthropic-ai/sdk, boto3. |
No output schema declared.
No examples provided.
list_migration_guides List migration guides ~72
Versyka's step-by-step SDK migration guides (OpenAI, Anthropic, Google Gemini, AWS, Stripe, Firebase, Slack, Twilio, Auth0, Pinecone), optionally filtered by package name.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | – | Only guides for this package, e.g. openai. |
No output schema declared.
No examples provided.
list_model_retirements List AI model retirements ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_retired | boolean | – | Also list models that are already retired. |
| vendor | string | – | – |
| within_days | integer | – | Only retirements within this many days from today. |
No output schema declared.
No examples provided.
lookup_model Look up a model's retirement ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | The model ID as written in code or config. |
No output schema declared.
No examples provided.
How do I install the Versyka MCP server?
Versyka is a hosted endpoint at https://www.versyka.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.versyka.com
claude mcp add --transport http com-versyka-versyka 'https://www.versyka.com/api/mcp'
What is the Versyka MCP server?
Versyka is an MCP server listed in the public MCP registry as com.versyka/versyka. Find retiring AI models and outdated API SDKs in your code, with dates, replacements and guides. This page covers its hosted endpoint (https://www.versyka.com/api/mcp).
Is the Versyka MCP server safe to use?
Versyka scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Versyka MCP server expose?
Versyka exposes 7 tools: check_dependencies, find_retired_models, lookup_model, list_model_retirements, get_sdk_versions, and 2 more. Their descriptions and schemas cost roughly 675 tokens of context every time the server is loaded.
Does the Versyka MCP server require authentication?
No. We connected to Versyka without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Versyka MCP server still maintained?
Versyka is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.