Skip to main content
Glama

Server Details

Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
2.5% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
jasonxkensei/prove-before-act
GitHub Stars
1
Server Listing
xProof

TDQS

A3.9/5.0

Scored across 13 tools

Disambiguation4/5

Most tools have clearly distinct purposes (file certification, decision certification, coherence anchoring, session audit, attestations, calibration, proof retrieval/verification). Minor overlap exists between get_proof and verify_proof, and between check_coherence and require_coherence_anchor, but descriptions clarify their different roles (retrieve vs verify, create vs check).

Naming Consistency4/5

The vast majority follow a verb_noun pattern (audit_agent_session, certify_file, check_attestations, discover_services, get_calibration, get_proof, investigate_proof, register_trial, require_coherence_anchor, submit_outcome, verify_proof). One deviation: certify_with_confidence uses a verb_with_noun structure, but it's still readable and the pattern is otherwise consistent.

Tool Count5/5

13 tools is well-scoped for a blockchain certification service covering discovery, trial, certification creation, verification, coherence anchoring, calibration, and investigation. Each tool addresses a specific workflow step without redundancy or bloat.

Completeness4/5

The core certification lifecycle (create, verify, retrieve) is fully covered, along with coherence anchors, calibration tracking, and investigation. A notable gap is the lack of a list or search tool to enumerate proofs for a wallet, but agents can work around it if proof IDs are known or provided by other flows.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Addedcheck_coherence
    • Addedrequire_coherence_anchor
  2. 1 tool update
    • Addedregister_trial
  3. 2 tool updates
    • Addedget_calibration
    • Addedsubmit_outcome
  4. 2 tool updates
    • Changedcertify_file4 fields changed
      • changedInput schema / properties / author_name / description
        Previous value: -"Name of the certifier (default: AI Agent)"New value: +"Name of the certifier (default: AI Agent, max 128 chars)"
      • addedInput schema / properties / author_name / maxLength
        Added value: +128
      • changedInput schema / properties / filename / description
        Previous value: -"Original filename with extension"New value: +"Original filename with extension (max 255 chars)"
      • addedInput schema / properties / filename / maxLength
        Added value: +255
    • Changedcertify_with_confidence4 fields changed
      • changedInput schema / properties / author_name / description
        Previous value: -"Name of the certifying agent (default: AI Agent)"New value: +"Name of the certifying agent (default: AI Agent, max 128 chars)"
      • addedInput schema / properties / author_name / maxLength
        Added value: +128
      • changedInput schema / properties / filename / description
        Previous value: -"Original filename with extension (e.g. decision.json)"New value: +"Original filename with extension (e.g. decision.json, max 255 chars)"
      • addedInput schema / properties / filename / maxLength
        Added value: +255
  5. 1 tool update
    • Removedregister_free_trial
  6. 1 tool update
    • Addedregister_free_trial
  7. 2 tool updates
    • Changedaudit_agent_session1 field changed
      • addedInput schema / properties / reversibility_class
        Added value: +{
        +  "description": "Governance: how reversible is this action? 'reversible' = can be undone at low cost, 'costly' = reversible but expensive (fees, slippage, delay), 'irreversible' = cannot be undone (on-chain settlement, data deletion, email sent). When 'irreversible', a confidence_level >= 0.95 is required to be policy-compliant.",
        +  "enum": [
        +    "reversible",
        +    "costly",
        +    "irreversible"
        +  ],
        +  "type": "string"
        +}
    • Changedcertify_with_confidence1 field changed
      • addedInput schema / properties / reversibility_class
        Added value: +{
        +  "description": "Governance: how reversible is this action? 'reversible' = can be undone, 'costly' = reversible but expensive, 'irreversible' = cannot be undone (on-chain settlement, data deletion, sent email). When 'irreversible', confidence_level must be >= 0.95 or xproof flags a policy violation.",
        +  "enum": [
        +    "reversible",
        +    "costly",
        +    "irreversible"
        +  ],
        +  "type": "string"
        +}
  8. 1 tool update
    • Addedcertify_with_confidence
  9. 1 tool update
    • Addedinvestigate_proof
  10. 1 tool update
    • Addedcheck_attestations
  11. 1 tool update
    • Addedaudit_agent_session
  12. 4 tool updates
    • First observedcertify_file
    • First observeddiscover_services
    • First observedget_proof
    • First observedverify_proof

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    F
    maintenance
    Post-quantum document anchoring for AI agents. Anchor any SHA-256 hash to Algorand mainnet with ML-DSA-65 (NIST FIPS-204) signatures and receive a self-contained proof bundle verifiable offline — decades from now, without trusting any vendor.
    4 npm
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents and MCP hosts to anchor file hashes to Bitcoin via OpenTimestamps and verify proofs, ensuring files existed before a given time with privacy-preserving local hashing.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.