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.

Crovia — verifiable silence (TACET) and Crovia Seal

REMOTE · CROVIATRUST.COM

Signed, Bitcoin-anchored observations of AI training-data disclosure; verifies silence proofs, seals

Available components

0 this week 88 Trust /100

Last scanned (6 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

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 Security80
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1559 tokens (~119/item across 13 items; 8 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 20 Oct 26 +1
    • Stability: 0.97 → pass security
  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +11
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “crovia_status” rewrote its description, which is the text the model reads security
    • Tool “crovia_vs_causari” rewrote its description, which is the text the model reads security
    • Tool “explain” rewrote its description, which is the text the model reads security
    • Tool “get_silence_proof” rewrote its description, which is the text the model reads security
    • Tool “lookup_model” rewrote its description, which is the text the model reads security
    • Tool “search_models” rewrote its description, which is the text the model reads security
    • Tool “silence_report” rewrote its description, which is the text the model reads security
    • Tool “verify_seal” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 10% → 100% ▲ functional
    • Server version: 2.0.0 → 2.0.1 functional
    • “explain” reworded the description of “term” cosmetic
    • “get_silence_proof” reworded the description of “include_bundle” cosmetic
    • “get_silence_proof” reworded the description of “model” cosmetic
    • “lookup_model” reworded the description of “model” cosmetic
    • “search_models” reworded the description of “limit” cosmetic
    • “search_models” reworded the description of “query” cosmetic
    • “silence_report” reworded the description of “week” cosmetic
    • “verify_seal” reworded the description of “check_anchors” cosmetic
    • “verify_seal” reworded the description of “seal” cosmetic
    • “verify_seal” reworded the description of “url” cosmetic
    • Tool “get_silence_proof” changed its title: Get a silence proof → One silence proof or its bundle cosmetic
    • Tool “lookup_model” changed its title: Look up a model → Look up one model cosmetic
    • Tool “search_models” changed its title: Search observed models → Page of model ids cosmetic
  • 5 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Probed https://croviatrust.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=croviatrust.com CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 4b4bd82dd97626580ebbe915b27f017a
SANs: croviatrust.com, *.croviatrust.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of croviatrust.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
croviatrust.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://*.croviatrust.com https://api.drand.sh https://mempool.space https://blockstream.info; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://croviatrust.com/mcp Verified 200
http (plaintext) http://croviatrust.com/mcp HTTPS enforced 301 https://croviatrust.com/mcp
MCP tools · 8 exposed · ~1,265 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
crovia_status ~73

Live totals at this moment: epochs closed, epochs anchored in Bitcoin, models on the map, snapshot counts, signed silence proofs, and a pointer to the longest verifiable silence. No parameters. This is not a weekly Silence Report, not one model's record, and not a proof bundle. Reads published files only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crovia_vs_causari ~63

Which product is which. Crovia observes training-data disclosure. Causari is the code-provenance tool. No parameters. Use this, not explain and not crovia_status, when the question is the difference between the two. Reads no catalog.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

explain ~139

The definition of one Crovia term. Allowed terms: tacet, silence, lacuna, seal, epoch, pnx, predicate, canon. Omit term, or pass an empty or blank string, to receive every definition. Any other value is an error listing those allowed terms, and it does not return the definitions. Use crovia_vs_causari, not explain, to tell the two products apart.

NameTypeReqDescription
termstring–One of tacet, silence, lacuna, seal, epoch, pnx, predicate, canon. Omit it, or pass an empty string, for every definition. An unknown term is an error.

No output schema declared.

No examples provided.

get_silence_proof ~157

The published silence proof for one model: silence_days, observed window, epochs, seal id, URL, and how to verify it. model omitted or empty returns the proof index, not a bundle. include_bundle defaults to false; true attaches the crovia.seal.v1 bundle for that one model and does nothing on the index. This is not the live totals and not the weekly report. Reads published files only.

NameTypeReqDescription
include_bundleboolean–Default false. True includes the seal bundle for the one model. Ignored when model is omitted or empty.
modelstring–Hugging Face model id. Omit it, or pass an empty string, to receive the proof index instead of one proof.

No output schema declared.

No examples provided.

lookup_model ~146

One model's observation: latest verdict, negative snapshots, anchored epochs, silence proof pointer, archive silence, badge and record URL. Required model is a Hugging Face id, org/name, for example Qwen/Qwen3-32B. An empty model is an error. An exact id is used; otherwise one case-insensitive substring match is accepted, and several matches return candidates instead of a verdict. This is not a catalog page, not the weekly report, and not the seal bytes. Reads published files only.

NameTypeReqDescription
modelstringyesHugging Face model id, org/name. Required. Empty is an error. Example: Qwen/Qwen3-32B.

No output schema declared.

No examples provided.

search_models ~314

A page of observed model ids whose id contains query, compared case-insensitively, in catalog order, not a ranking. query omitted or empty matches the whole catalog and still returns at most limit rows. limit follows the historical rule: a missing, empty, zero or other falsy value is 25; any value int() accepts is then clamped into 1..100 (500 becomes 100, a negative becomes 1); a value int() cannot parse is an error and nothing is searched. returned and its compatibility alias count are the rows in this page. matched is how many ids match before the limit. catalog_total and its compatibility alias total_records are every record in the catalog, matching or not. limit is the limit actually applied. count is not the match count, and total_records is not the match count. This is not a verdict and not a proof. Reads published files only.

NameTypeReqDescription
limitinteger–Page size. Omitted, empty, 0 or any other falsy value means 25. A value int() accepts is clamped into 1..100: 500 is fetched as 100 and a negative as 1. There is no schema minimum or maximum, because…
querystring–Substring of the model id. Omit it, or pass an empty string, to match the whole catalog. The page is still capped by limit.

No output schema declared.

No examples provided.

silence_report ~138

One published weekly Silence Report, or the latest report index. week is an ISO week YYYY-Www, for example 2026-W38. Omit week, or pass an empty string, to receive the latest index rather than one week's facts. A week that is not YYYY-Www is an error. A week with no published file is an error and names the index. This is not the live status and not one model's proof. Reads published files only.

NameTypeReqDescription
weekstring–ISO week YYYY-Www, for example 2026-W38. Omit it, or pass an empty string, for the latest report index.

No output schema declared.

No examples provided.

verify_seal ~235

Check a crovia.seal.v1 object or a wrapped TACET silence proof: signature, canonical bytes, bindings, and per-epoch non-inclusion paths. Pass seal as a JSON object or a JSON string, or url as an https://croviatrust.com/ address. With neither, the call is an error. Supplying url fetches that URL over the network. check_anchors defaults to false; true also checks the drand round bytes and the Bitcoin anchors over the network. A seal object with check_anchors false or omitted is checked from that object alone. This tool can reach the network, so it is not a closed-world call.

NameTypeReqDescription
check_anchorsboolean–Default false. True checks the drand round and the Bitcoin anchors over the network. False does not.
sealobject|string–The seal or wrapped proof, as a JSON object or a JSON string. Omit it when url is set.
urlstring–https://croviatrust.com/ URL of a JSON seal. Any other host is rejected. Fetching it uses the network.

No output schema declared.

No examples provided.

Install

How do I install the Crovia — verifiable silence (TACET) and Crovia Seal MCP server?

Crovia — verifiable silence (TACET) and Crovia Seal is a hosted endpoint at https://croviatrust.com/mcp, 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 · croviatrust.com

# add to Claude Code
claude mcp add --transport http com-croviatrust-crovia 'https://croviatrust.com/mcp'
Common questions

What is the Crovia — verifiable silence (TACET) and Crovia Seal MCP server?

Crovia — verifiable silence (TACET) and Crovia Seal is an MCP server listed in the public MCP registry as com.croviatrust/crovia. Signed, Bitcoin-anchored observations of AI training-data disclosure; verifies silence proofs, seals. This page covers its hosted endpoint (https://croviatrust.com/mcp).

Is the Crovia — verifiable silence (TACET) and Crovia Seal MCP server safe to use?

Crovia — verifiable silence (TACET) and Crovia Seal scores 88 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 Crovia — verifiable silence (TACET) and Crovia Seal MCP server expose?

Crovia — verifiable silence (TACET) and Crovia Seal exposes 8 tools: crovia_status, lookup_model, search_models, get_silence_proof, verify_seal, and 3 more. Their descriptions and schemas cost roughly 1,265 tokens of context every time the server is loaded.

Does the Crovia — verifiable silence (TACET) and Crovia Seal MCP server require authentication?

No. We connected to Crovia — verifiable silence (TACET) and Crovia Seal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Crovia — verifiable silence (TACET) and Crovia Seal MCP server still maintained?

Crovia — verifiable silence (TACET) and Crovia Seal is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.