# Versyka (remote · www.versyka.com)

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

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `www.versyka.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-versyka-versyka/api-mcp.md), [page](https://verifymcp.io/servers/com-versyka-versyka/api-mcp)

## Channel facts

- Endpoint: `https://www.versyka.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-versyka-versyka": {
      "type": "remote",
      "url": "https://www.versyka.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-versyka-versyka --url 'https://www.versyka.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-versyka-versyka:
    url: "https://www.versyka.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-versyka-versyka": {
      "Transport": "http",
      "Url": "https://www.versyka.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-versyka-versyka -t streamable-http -u 'https://www.versyka.com/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 75, +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.

### 2026-10-16 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 74)

First indexed and scored.

## MCP tools (7)

### `check_dependencies` (~131 tokens)

Check API SDK versions

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.

Input parameters:

- `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, required): The full text of the manifest file.

### `find_retired_models` (~112 tokens)

Find retired AI models in code

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.

Input parameters:

- `files` (array, required): Files to scan, each with its repository-relative path and full text.

### `lookup_model` (~104 tokens)

Look up a model's retirement

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.

Input parameters:

- `model` (string, required): The model ID as written in code or config.

### `list_model_retirements` (~84 tokens)

List AI 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.

Input parameters:

- `include_retired` (boolean): Also list models that are already retired.
- `vendor` (string)
- `within_days` (integer): Only retirements within this many days from today.

### `get_sdk_versions` (~96 tokens)

Latest SDK version

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.

Input parameters:

- `ecosystem` (string, required): Which registry: npm (JavaScript/TypeScript) or pypi (Python).
- `package` (string, required): Package name, e.g. openai, @anthropic-ai/sdk, boto3.

### `list_migration_guides` (~72 tokens)

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.

Input parameters:

- `package` (string): Only guides for this package, e.g. openai.

### `get_migration_guide` (~76 tokens)

Get a 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.

Input parameters:

- `slug` (string, required): The guide slug from list_migration_guides, e.g. openai-python-v0-to-v1.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-versyka-versyka/api-mcp#diagnostics

## Score history

- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74

## Common questions

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

## Links

- Remote endpoint: https://www.versyka.com/api/mcp
- Website: https://www.versyka.com/integrations
- Changelog RSS feed: https://verifymcp.io/servers/com-versyka-versyka/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-versyka-versyka/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-versyka-versyka/api-mcp