MCP Catalog Overview
The MCP Catalog is Velerion’s registry of Model Context Protocol servers. It answers two questions that every team hits once more than one agent is in production: which tools are approved here, and who is allowed to attach them to what.
How it is organised
Section titled “How it is organised”- Public catalog — servers published and maintained by Velerion and by verified vendors.
- Workspace catalog — servers your organisation has approved, including private forks of public entries and internal servers that are never published outside the workspace.
- Pinned versions — every attachment records an exact server version. Catalog updates never change a running agent until you promote the new version.
Anatomy of a catalog entry
Section titled “Anatomy of a catalog entry”| Field | Meaning |
|---|---|
id |
Stable identifier, for example velerion/postgres. |
version |
Semantic version of the server implementation. |
transport |
stdio, streamable-http or sse. |
tools |
Declared tool names, argument schemas and side-effect class. |
scopes |
Credentials the server requires from the connection it is bound to. |
review |
Velerion security review status and the date it was last re-checked. |
Read-only by default
Section titled “Read-only by default”Every tool in a catalog entry declares whether it mutates state. Newly attached servers are exposed to agents with mutating tools disabled; an admin enables them explicitly per environment.
Next steps
Section titled “Next steps”- Browse & Install Servers — attach a server to an environment.
- Publishing Servers — get your own server into the catalog.
