vercy
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
vercy
Two tools for agent memory, in one package with no dependencies.
vercy check- checks a memory store against the Vercy Governance Overlay: the fields a store needs to answer questions about time, authority and disclosure.vercy mcp- a read-only MCP server over the published Vercy model catalogue.
Apache-2.0. No telemetry. The checker makes no network calls. The MCP server only sends GET requests to
one origin, https://ver.cy by default (VERCY_BASE_URL to use a mirror), and refuses any URL or
redirect outside it.
Check a store
uvx vercy check memory.jsonlInput is a JSON array, or one JSON object per line. Your field names can stay your own:
uvx vercy check graph.jsonl --map record_id=uuid,valid_from=valid_at,valid_to=invalid_at,source=episoderecords: 30
level reached: 1 of 3
profile: vercy-governance-overlay 1.0
concept_owner level 2 MUST D-101, D-102, D-103, D-201, D-202, D-301 and 24 more
conflict_policy level 2 MUST no conflict policy anywhere in the storeLevel | Fields | What the fields let a host do, if it uses them |
1 |
| Answers about any date; an update can name what it replaces |
2 |
| Disagreement resolved by rule, change requests routed to an owner |
3 |
| What may cross a boundary, without leaking or over-refusing |
Options: --json for a machine report, --min-level 2 to raise the bar, --policy when the conflict
policy lives outside the records. Exit codes: 0 the store reaches the level, 1 it does not,
2 the input could not be read. That makes it a CI gate.
What a pass means. The overlay fields are present and not empty (valid_to only has to be
present: null means still open). Nothing more. Values are not
validated, and a pass does not mean a host enforces them: a record can carry release_to while another retrieval path ignores it.
Enforcement is a separate, testable claim, defined in ENFORCEMENT-CONTRACT.md.
Related MCP server: TokenLab MCP Server
Register a model or a registry
Anyone may register a Meta-Model, or a whole registry of them, with a Vercy register under the Open Registration Policy. Check your entry the way the register will before you submit it:
pip install "vercy[yaml]"
vercy register check entries/example.orders.yaml --token YOUR-PROOF-TOKENIt validates the entry against the registry entry schema, checks that the source answers, looks
for the proof token (domain or repository), reads the Discovery Document of a registry entry and
runs the content screens. Every failure is listed; the exit code is 0 on pass, 1 on fail and 2 for
an unreadable file, so it runs in CI as is. --offline skips the network checks and says so.
Use Vercy from an agent
claude mcp add vercy -- uvx vercy mcpOr in any MCP client configuration:
{ "mcpServers": { "vercy": { "command": "uvx", "args": ["vercy", "mcp"] } } }Tool | What it returns |
| Ranked models for a name or need |
| One model by id, model id, slug or unique alias; with |
| The overlay fields, levels, definitions and measured effects |
| The |
| Citation text, page URL, specification URL, version and digest |
All tools are read-only. Tool failures come back as {"error": code, "message": ...} with codes an
agent can branch on: unknown_model, not_published, ambiguous_id, upstream_unreachable,
foreign_url. Malformed calls get JSON-RPC errors with the request id kept.
Why these fields
Each field is in the profile because a published benchmark measured what changes without it. On the collaborative-memory benchmark, a bitemporal graph without owner and conflict rule answered 77.4 percent. Adding a governance catalogue to the same graph took it to 93.5 percent (p = 0.039). A team wiki and a Vercy dimension carrying the same facts with the fields scored 96.8 and 95.2 percent. Methods, raw runs and harnesses: ver.cy/benchmarks/collaborative-memory-v1.
Development
python -m unittest discover -s testssrc/vercy/data/profile.json is generated from profile.yaml (the file published at
https://ver.cy/overlay/profile.yaml) by python tools/sync_profile.py.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Read-only MCP server for the Durable Agent Directory: search and compare agent-infrastructure tools.
Read-only MCP server exposing a user ORANO library to their own AI agent.
OAuth-protected, read-only-by-default MCP server for provenance-labeled QuillCaddie project memory.
Related MCP Servers
- AlicenseAqualityDmaintenanceA read-only MCP server for navigating OpenAPI / Swagger specifications, enabling agents to search endpoints, retrieve parameters and schemas, and inspect authentication without loading the full spec into context.997 npmMIT
- AlicenseCqualityBmaintenanceRead-only MCP server that exposes public TokenLab model catalog tools for agents to discover models, inspect request contracts, and compare pricing.321,219 npm1MIT
- AlicenseAqualityBmaintenanceRead-only MCP server that exposes the agentic-os governance, SDLC, and Quality Engineering methodology to any MCP host. It never writes to your repository and never executes code — it serves the methodology, plans an install, and verifies it, handing any commands back to the host to run.72Apache 2.0
- AlicenseBqualityBmaintenanceRead-only MCP server that exposes governed operational records with provenance and validity windows so clients can check which evidence is still current before answering. It lets agents reconcile freshness, schedule state, and evidence specificity to determine whether scheduled automations are actually healthy, rather than trusting an expired dashboard summary.4MIT