Other · Remote MCP server
Version Pill
Product management, public changelog, and feature requests - 60 lean MCP tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.versionpill/mcp- Version
- 6.4.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-06-29
- Updated
- 2026-06-29
- Publisher
- versionpill (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/versionpill) · how
- Website
- versionpill.com
- Repository
- github.com/versionpill/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.versionpill.com/mcp | None |
| SSE (HTTP + Server-Sent Events) | https://mcp.versionpill.com/sse | 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.
- Endpoint
https://mcp.versionpill.com/mcp(HTTP)- 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
- Endpoint
https://mcp.versionpill.com/sse(SSE)- Reachable
- Yes (HTTP 404)
- SSE stream
- HTTP 404
- Checked on
- 2026-10-05
How to connect Version Pill
Version Pill is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.versionpill.com/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.
It also lists an endpoint on the older SSE transport https://mcp.versionpill.com/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
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
More other servers
| Server | Runs |
|---|---|
| VerityCited product-compliance ground truth for AI agents. Never generates; always cites. | Remote · HTTPLive check: ✓ handshake |
| Verity MCPFail-closed verify-before-you-act gate for AI agents. Signed receipts. Pay-per-call via x402. | Local · stdio |
| VerixID VerifierVerify VerixID proof-of-existence records and optionally prove ownership. | Remote · HTTPLive check: ✓ handshake |
| VermarcoMarketplace and payment rail for AI agents: list, buy and settle with signed receipts. | Remote · HTTPLive check: ✓ handshake |
| VersoMCP server to read Verso-generated documentation sites (e.g., the Lean Language Reference). | Local · stdio |
| VersusbriefPitch reviews for agencies: a prospect against its local rivals, 90-day plan, draft ads. Read-only. | Remote · HTTPLive check: sign-in required |
| Vertaaux MCPAutonomous UX and a11y audit, fix, and verify loop. 38 tools, framework-aware patches. | Local · stdio |
| Vertical FlowsView client requests, prepare actions and approve work within your firm's permissions. | Remote · HTTPLive check: sign-in required |