Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TomeVault

REMOTE · MCP.TOMEVAULT.IO · SCANNED SEP 20

Check AI instruction files, look up a company's record, and keep a dated record of your own.

Available components

0 this week 37 Trust /100

Recent critical change

Authorization (1 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security92
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Install

How do I install the TomeVault MCP server?

TomeVault is a hosted endpoint at https://mcp.tomevault.io/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.tomevault.io

# add to Claude Code
claude mcp add --transport http olijboyd-tomevault 'https://mcp.tomevault.io/'
// .cursor/mcp.json
{
  "mcpServers": {
    "olijboyd-tomevault": {
      "url": "https://mcp.tomevault.io/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "olijboyd-tomevault": {
      "type": "http",
      "url": "https://mcp.tomevault.io/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.olijboyd-tomevault]
url = "https://mcp.tomevault.io/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "olijboyd-tomevault": {
      "type": "remote",
      "url": "https://mcp.tomevault.io/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add olijboyd-tomevault --url 'https://mcp.tomevault.io/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  olijboyd-tomevault:
    url: "https://mcp.tomevault.io/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "olijboyd-tomevault": {
      "Transport": "http",
      "Url": "https://mcp.tomevault.io/"
    }
  }
}
# add to Vellum
assistant mcp add olijboyd-tomevault -t streamable-http -u 'https://mcp.tomevault.io/'
// mcp.json
{
  "mcpServers": {
    "olijboyd-tomevault": {
      "type": "http",
      "url": "https://mcp.tomevault.io/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Sept 26 −43
    • Endpoint reachability: reachable → behind authorisation security
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Transport: pass → unverified security
    • Authorization: fail → pass security
    • First check of Authorization: pass security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: 100 → unverified functional
  • 3 Sept 26 0
    • A breaking change shipped without a version bump: still 1.0.0 security
    • Tool “issue_certificate” rewrote its description, which is the text the model reads security
    • “issue_certificate” dropped the required parameter “item_ids” functional
  • 2 Sept 26 0
    • New tool “deliver_to_source”, which the server declares destructive security
    • New tool “invite_member”, which the server declares destructive security
    • New tool “issue_certificate”, which the server declares destructive security
    • Schema quality: 102 → 88 functional
    • New tool “connect_source” functional
    • New tool “get_billing_summary” functional
    • New tool “get_workspace_status” functional
    • New tool “list_certifications” functional
    • New tool “list_members” functional
  • 1 Sept 26 +1
    • Authorization: unverified → fail critical
    • New tool “save_vault_version”, which the server declares destructive security
    • Tool “get_vault_item” rewrote its description, which is the text the model reads security
    • Schema quality: unverified → 100 functional
    • Schema quality: fail → pass functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • New resource “record-panel” functional
  • 28 Aug 26 0
    • Tool “scan_content” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail functional
  • 27 Aug 26 0
    • Endpoint reachability: not serving MCP → reachable functional
  • 26 Aug 26 +56
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.83 → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://mcp.tomevault.io/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.tomevault.io CN=YE1,O=Let's Encrypt,C=US 14 Aug 2026 12 Nov 2026 ECDSA 256 ECDSA-SHA384 6e13f201a5545a8981a290f3380019e75f8
SANs: mcp.tomevault.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.tomevault.io. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
tomevault.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer scope="estate:read estate:write members:read", resource_metadata="https://mcp.tomevault.io/.well-known/oauth-protected-resource"

Bearer scope="estate:read estate:write members:read", resource_metadata="https://mcp.tomevault.io/.well-known/oauth-protected-resource"
Header Value
www-authenticate Bearer scope="estate:read estate:write members:read", resource_metadata="https://mcp.tomevault.io/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://mcp.tomevault.io/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.tomevault.io/
Authorisation server https://tomevault.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.tomevault.io/ Auth required 401
http (plaintext) http://mcp.tomevault.io/ HTTPS enforced 308 https://mcp.tomevault.io/
MCP tools · 17 exposed · ~1,576 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
connect_source ~54

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

convert_content ~113

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.

NameTypeReqDescription
contentstringyesThe raw instruction-file text to convert.
descriptionstringOptional one-line description for the converted file.
namestringOptional title for the converted file's heading/frontmatter.
to_formatstringyesThe target tool format.

No output schema declared.

No examples provided.

deliver_to_source ~74

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.

NameTypeReqDescription
item_idstringyesThe vault file id, from list_vault_items.

No output schema declared.

No examples provided.

get_billing_summary ~79

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_provenance ~97

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.

NameTypeReqDescription
ownerstringyesGitHub owner or org.
repostringyesGitHub repository name.
skill_pathstringAddress a specific skill within the repo, e.g. skills/foo.

No output schema declared.

No examples provided.

get_tome ~130

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.

NameTypeReqDescription
formatstringOutput format, e.g. claude_md, agents_md, skill_md.
ownerstringyesGitHub owner or org.
repostringyesGitHub repository name.
skill_pathstringFetch a specific skill within the repo (the skill_path from a search_tomes result). Omit for the repo's primary unit.

No output schema declared.

No examples provided.

get_vault_item ~91

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.

NameTypeReqDescription
idstringyesThe vault item id, from list_vault_items.

No output schema declared.

No examples provided.

get_workspace_status ~88

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

invite_member ~56

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.

NameTypeReqDescription
emailstringyesThe colleague's email address.

No output schema declared.

No examples provided.

issue_certificate ~116

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.

NameTypeReqDescription
client_idstringyesThe client id, from list_certifications.
titlestringDisplay title for the certificate. Not part of the signature.

No output schema declared.

No examples provided.

list_certifications ~57

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_members ~42

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_vault_items ~52

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.

NameTypeReqDescription
limitinteger

No output schema declared.

No examples provided.

save_vault_version ~88

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.

NameTypeReqDescription
contentstringyesThe complete corrected file. Partial content would truncate the file.
item_idstringyesThe vault file id, from list_vault_items.

No output schema declared.

No examples provided.

scan_content ~159

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.

NameTypeReqDescription
namestringOptional display name, e.g. CLAUDE.md.
textstringyesRaw instruction-file text to scan.

No output schema declared.

No examples provided.

search_tomes ~139

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.

NameTypeReqDescription
formatstringTarget tool format, e.g. claude_md, agents_md, cursor_mdc.
gradestringScreen by graded quality tier.
kindstringtome = full project config + skills; config = one config file; skill = one skill.
limitinteger
querystringyesFree-text task or topic to match.

No output schema declared.

No examples provided.

verify_attestation ~141

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.

NameTypeReqDescription
attestationstringyesThe .tome/attestation.json document text.
contentstringOptional: the instruction file the attestation signs, to also confirm it has not changed.

No output schema declared.

No examples provided.

Common questions

What is the TomeVault MCP server?

TomeVault is an MCP server listed in the public MCP registry as io.github.olijboyd/tomevault. Check AI instruction files, look up a company's record, and keep a dated record of your own. This page covers its hosted endpoint (https://mcp.tomevault.io/).

Is the TomeVault MCP server safe to use?

TomeVault scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TomeVault MCP server expose?

TomeVault exposes 17 tools: search_tomes, get_tome, get_provenance, scan_content, convert_content, and 12 more. Their descriptions and schemas cost roughly 1,576 tokens of context every time the server is loaded.

Does the TomeVault MCP server require authentication?

Yes. TomeVault asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the TomeVault MCP server still maintained?

TomeVault is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.