Developer · Remote MCP server
Versionly
Monitor third-party API changes in GitHub repos, map breaks to files, open reviewable auto-fix PRs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.versionly/mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- dev.versionly
- Namespace
- Namespace verified by the MCP Registry via the domain versionly.dev · how
- Listed under
- GitHub MCP servers, Maps MCP servers
- Website
- versionly.dev
- Repository
- github.com/WoWSQL/versionly-cursor-plugin
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.versionly.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Versionly
Versionly is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.versionly.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, versionly.dev, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| VerirunExecution-grounded verification for AI coding agents on Windows: evidence, not agent claims. | Local · stdio |
| VerisBehavioral verification intelligence for AI coding agents. 17 MCP tools. Local-first. MIT. | Local · stdio |
| VeriTeknikManage VeriTeknik servers, DNS, backups and support tickets from your AI assistant. | Remote · HTTPLive check: sign-in required |
| Verlon AI MCPInspect and manage Verlon AI gates, logs, recommendations, and experiments from any MCP client. | Local · stdio |
| VetDiscover and vet MCP servers: search 200K+ AI tools with security verification and schemas. | Local · stdio |
| Veto93 agentic MCP tools + 49 specialist agents for every major AI CLI. Self-learning, no API keys. | Local · stdio |
| Veto - SQL Safety & Cost OracleDeterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it. | Remote · HTTPLive check: ✓ handshake |
| Vetted ConsumerWill a local LLM run on your hardware? GGUF quant, buy-vs-rent-vs-API cost, used-GPU prices. | Remote · HTTPLive check: ✓ handshake |