TomeVault is listed as active in the registry but did not answer our last check. It exposes 17 tools.
Check AI instruction files, look up a company's record, and keep a dated record of your own.
Uptime history
91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 92 checks
17
Tools
read from the server
182 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 13
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 August 2026. No other catalogue keeps this.
2 Sep
a tool description was rewritten
issue_certificate
2 Sep
a tool changed the parameters it asks for
issue_certificate
1 Sep
8 tools appeared
connect_source, deliver_to_source, get_billing_summary and 5 more
31 Aug
a tool appeared
save_vault_version
31 Aug
a tool description was rewritten
get_vault_item
27 Aug
a tool description was rewritten
scan_content
TomeVault does not always answer
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
run in your terminal
claude mcp add tomevault --transport http https://mcp.tomevault.io/Settings → Connectors → Add custom connector, then paste this address
https://mcp.tomevault.io/~/.codex/config.toml
[mcp_servers.tomevault]
url = "https://mcp.tomevault.io/".cursor/mcp.json
{
"mcpServers": {
"tomevault": {
"url": "https://mcp.tomevault.io/"
}
}
}.vscode/mcp.json
{
"servers": {
"tomevault": {
"type": "http",
"url": "https://mcp.tomevault.io/"
}
}
}Available tools 17
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
vault
get_vault_item
Fetch one of your TomeVault items by id, with its content. Returns the version the file's maintainer approved, which is not always the newest one. Requires a vault access token with the items:read scope. Encrypted items are not retrievable and return not found, indistinguishable from a missing id.
list_vault_items
List the items in your TomeVault that this token can read. Requires a vault access token with the items:read scope. Encrypted (private) items are never listed.
billing
get_billing_summary
Report which plan the caller's TomeVault workspace is on, who is on it, what is included, and how much of that is unused. Read only: it cannot change a plan or spend money. It does not report a seat count, because seats bill on approved authority rather than headcount and the exact figure is on their billing page.
certifications
list_certifications
List the clients in the caller's TomeVault workspace, which of them have certification active, and which certificates have been issued. Reports what activating would cost. It cannot activate anything: that is a paid, human decision made on the website.
connect
connect_source
Report which sources are connected to the caller's TomeVault workspace and return the link that starts connecting another. Connecting requires the person to approve access in their browser, so this returns a link for them to open rather than completing it.
convert
convert_content
Convert pasted instruction-file text into another tool's format (claude_md, agents_md, cursor_mdc, gemini_md, copilot_instructions, windsurf_rules, skill_md). The same instructions, ready for any tool.
deliver
deliver_to_source
Deliver a TomeVault file's approved version back to the caller's connected Google Drive, so the corrected file reaches the place their team reads it. Sends the approved version, which is not always the newest one. Requires a connected Drive.
invite
invite_member
Invite a colleague to the caller's TomeVault workspace by email. Sends them a join link. Requires an admin. The join link is emailed to them and is never returned here.
issue
issue_certificate
Issue a signed TomeVault certificate for one organisation (a client folder). It covers every file in that folder that has a matching record, lists the rest with the reason they are not covered, and never re-grades: every grade comes from a record already signed. Only works for a client whose certification is already active; it cannot activate one, because that costs money.
members
list_members
List who is on the caller's TomeVault workspace and which invitations are still outstanding. Returns roles and join dates, not the email addresses of people who have already joined.
provenance
get_provenance
Return the signed attestation record alone for a tome: quality grade, security scan grade and flags, decay risk, source registry, the content hash it is bound to, and the signing key id for offline verification.
save
save_vault_version
Save corrected content as a new version of one of your TomeVault files. The previous version is kept and the file is re-checked. Returns the new version number and the verdict, never the file content.
scan
scan_content
Scan submitted instruction-file text for safety, clarity, loadability, and cross-model consistency, and return a verdict with findings. Each finding carries a `severity`: `fail` means the rule does not load, `info` means it loads but is wrong in a way worth fixing, such as naming a retired model. Report both. Only an empty `findings` array means nothing was found. Use before loading a third-party file. Consistency findings are PREDICTIONS (divergence risks across models/tools), never verified facts. The submitted text is scanned and discarded, never stored.
tome
get_tome
Fetch one tome's content in a specific agent format (default claude_md). Every response carries the provenance verdict: quality grade, security scan grade, decay risk, and the content hash it is bound to.
tomes
search_tomes
Search TomeVault for agent context files (tomes, configs, skills) by a task description. Filter by format, kind, and quality grade. Returns ranked matches with owner/repo, grade, and available formats, not file contents.
verify
verify_attestation
Verify a TomeVault attestation document (the contents of a repo's .tome/attestation.json). Confirms the detached signature is genuinely TomeVault's against the published key, and, if the signed file's text is supplied, that the file has not drifted since it was signed. Returns the signed verdict; consistency in it is a PREDICTION (cross-model divergence risk), never a verified fact. Nothing submitted is stored.
workspace
get_workspace_status
Summarise the caller's TomeVault workspace: how many files are held, what sources are connected, how many people are on it, and what is not yet covered. Call this before answering questions about their setup, and before suggesting a next step, so the answer describes their real state rather than a guess. `gaps` lists what is missing and is as important as the counts.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.tomevault.io/ | streamable-http | answering | 182 ms | 3 min ago |
Alternatives to TomeVault
same job, measured the same wayWhat's Inherited
by stcmain
What a checkout tells your agent to do: instruction files, hooks, declared MCP servers.
Curated
by curated
Keep and share lists of recommendations with your own notes, and read lists from people you trust.
Norma by Quality Clouds
by qualityclouds
Checks AI-written code against your rules as it is written, and keeps a record of what it found.
TeamOnly
by teamonly
Deploy AI-built internal apps behind your company login, with a database, files and secrets.
IP.LS — IP Lookup Service
by ip
Keyless IP geolocation, ASN/ISP, timezone and DNS records for any IP or domain, plus your own IP.
K
Kryptheon
by jhashantanu987-beep
Record a flow through your app, check it after every change, and attack a copy of your database.
Shadow AI List
by airiskmanagement
Risk-ranked registry of AI tools: look up an AI tool's risk or check if a domain is shadow AI.
PlainHub
by ricrio-inc
Open files and diffs from your agent in PlainHub, and keep a shared ledger in your own GitHub repo.
TomeVault — questions
Answers built from our own checks of this server.
What can TomeVault do?
It exposes 17 tools, read directly from the server on our last check. Among them: connect_source, convert_content, deliver_to_source, get_billing_summary, get_provenance, get_tome and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is TomeVault working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 182 ms. The bar chart above shows every period we have measured.
The registry lists TomeVault as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect TomeVault?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does TomeVault need an API key?
No. TomeVault completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.