catqualia-ledger-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_claimB | Search the CatQualia falsification ledger for claims matching a string, optionally filtered by verdict. Returns the claim, the pre-registered threshold that would refute it, the measured value, and the verdict. The ledger holds 16,217 measured claims including 5,837 the system refuted against its own ground truth. |
| get_verdictA | Retrieve the recorded verdict for a named check, or find claims containing a phrase. If a check was run more than once, all verdicts are returned in ledger order — a change between them is a ratchet event. Never infers a verdict for a claim that is not in the ledger. |
| what_would_refuteA | Return the pre-registered refutation threshold for matching claims: the measurement that would have killed each claim, recorded before the outcome was known. 16,194 of 16,218 ledger records carry one. Use this to test whether a claim is falsifiable at all. |
| verifier_drift_netA | Measure the verifier ratchet: whether a system's ability to catch its own false claims is improving or degrading. Re-runs checks and classifies every verdict transition as hardening or loosening, returning the signed net. Currently 277 checks re-run, 79 transitions, 38 hardening, 38 loosening, net zero. |
| citation_blockA | Return a ready-to-use BibTeX entry and schema.org ScholarlyArticle JSON for a CatQualia publication, so that citing agents cite correctly and resolve the DOI. Call with no slug to list available slugs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools are mostly distinct: query_claim returns full claim records, get_verdict focuses on verdict retrieval, what_would_refute provides thresholds, verifier_drift_net measures transitions, and citation_block handles citations. There is some overlap between query_claim and get_verdict in searching by phrase, but the purposes are clearly different enough to avoid significant confusion.
Naming conventions are inconsistent. query_claim and get_verdict follow a verb_noun pattern, but what_would_refute is a question phrase, verifier_drift_net is a noun compound, and citation_block is also noun_noun. This mixed style makes it harder to predict tool names and reduces coherence.
With only 5 tools, the server is tightly scoped to its ledger domain. Each tool covers a distinct need—searching, verdicts, thresholds, drift analysis, and citations—without redundancy or bloat.
The tool surface covers the core operations for querying and analyzing the ledger: search, verdict retrieval, threshold lookup, drift measurement, and citation generation. Minor gaps exist, such as no explicit tool to list all claims or add new ones, but the apparent read-only purpose is well-served.