Skip to main content
Glama
Sign In
stillmarcus24

stillos-notary-mcp

by stillmarcus24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to stillos-notary-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      78 npm
      MIT

    • Confirme

      francistremblay30-netizen
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to obtain independent, Ed25519-signed receipts confirming real-world facts: whether a page is online, a domain is legitimate, an email address is deliverable, a heartbeat was declared, or a scheduled task actually ran. Each response includes a verifiable cryptographic receipt, so agents can prove to their users that an asserted outcome was observed by a neutral third party rather than self-attested.
      MIT

    • FOAAP Engine

      paulovillalobos
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI applications to submit claims, decisions, and evidence so it maintains a typed state model of beliefs, conflicts, changes, and next actions, preserving claim lineage and semantic evidence across versioned persistence.
      MIT
    • catqualia-ledger-mcp by OpeningBlackBox

      catqualia-ledger-mcpofficial

      OpeningBlackBox
      F
      license
      A
      quality
      A
      maintenance
      Enables agents to verify claims against a real falsification ledger, querying pre-registered refutation thresholds, recorded verdicts, and verifier drift metrics instead of guessing.
      5
      -
    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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action—general claim resolution, specialized scoring, OFAC screening, dispute filing, and receipt verification. The overlapping 'signed verdict' outputs are clearly differentiated by resolver type, pricing model, and lifecycle role.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: claim_verdict, file_dispute, screen_entity, verify_receipt. distress_score breaks that pattern as a noun phrase, making it the one inconsistent name in an otherwise coherent set.

    Tool Count5/5

    Five tools is well-scoped for a notary-style service. The set covers creation, specialized verdict types, dispute handling, and verification without unnecessary redundancy.

    Completeness4/5

    The core lifecycle is covered: create verdicts, dispute them, and verify receipts. A minor gap is the lack of a general receipt-listing or lookup tool, though verify_receipt by hash mitigates this.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow

    Resources