Skip to main content
Glama
OpeningBlackBox

catqualia-ledger-mcp

Official
by OpeningBlackBox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to catqualia-ledger-mcp

No user-submitted related servers found.

    Related Servers

    • claimidx by claimidx

      claimidxofficial

      claimidx
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to query a public signed ledger of known failures and fixes before retrying, then ingest, confirm, fail, and share dense claims so subsequent agents avoid paying the same cost.
      29
      468 PyPI
      1
      Apache 2.0

    • VerifyAPI MCP Server

      KyTheKitty
      A
      license
      A
      quality
      C
      maintenance
      Enables agents and clients to fact-check factual claims against live web sources, returning citable verdicts with source details and cryptographically signed receipts for downstream verification.
      1
      307 npm
      MIT

    • stillos-notary-mcp

      stillmarcus24
      A
      license
      A
      quality
      D
      maintenance
      Enables submitting claims and receiving Ed25519-signed, hash-chained verdicts resolved against real external ground truth, supporting resolvers like GitHub PRs, on-chain transactions, URL JSON, HTTP status, and Kalshi markets.
      5
      352 npm
      MIT

    • AgentGround Cross-Check

      Arafel187
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to cross-verify candidate claims against caller-supplied source texts, flagging hallucinations, numerical drift, entity mismatches, contradictions, and unverified assertions. It returns sentence-level verdicts with matched evidence snippets and machine-readable factual grounding confidence scores, exposed over MCP stdio, HTTP REST, and A2A discovery routes.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    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 Consistency2/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources