Skip to main content
Glama
ProofCore-Protocol

proofcore-mcp

Official
by ProofCore-Protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to proofcore-mcp

Related Servers

  • DocImprint

    sawftware-labs
    F
    license
    Not graded
    quality
    A
    maintenance
    Verifiable document intelligence for AI agents. Extract, summarize, claim-check, and notarize PDFs & URLs with cryptographic proofs, cross-document search, and on-chain attestation via Base L2.
    -

  • dgb-attest-mcp

    dgb-tools
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables on-chain attestation of any content onto the DigiByte blockchain, providing permanent, timestamped, tamper-evident proofs. Allows AI agents to notarize their outputs or verify attestations using only the blockchain.
    13 npm
    MIT

  • APEX PSI MCP Server

    kawal393
    A
    license
    A
    quality
    C
    maintenance
    Provides cryptographic truth infrastructure for AI agents, enabling them to seal content with SHA-256 and Ed25519, verify receipts, anchor them to Bitcoin via OpenTimestamps, generate citations, and audit chains of receipts.
    5
    24 npm
    1
    MIT

  • Cryptair MCP Server

    Syronius
    A
    license
    A
    quality
    D
    maintenance
    Enables AI agents to certify documents, prove agreements, and verify counterparty claims with on-chain receipts on Hedera Hashgraph. Provides tools for document certification, two-party attestation, and agent registration with zero-config setup.
    6
    23 npm
    MIT

  • PiQrypt MCP Server

    PiQrypt
    A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to sign decisions with post-quantum cryptographic proofs and maintain secure audit trails for compliance. It provides tools for stamping events, verifying chain integrity, and exporting audit data across industries like finance and healthcare.
    4
    32 npm
    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.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: sealing, status checking, verification, and key retrieval. No two tools overlap in functionality, making tool selection unambiguous.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (seal_content, get_proof_status, verify_content, get_public_key). The naming is predictable and uniform across the set.

Tool Count5/5

With only 4 tools, the server is tightly focused on its core purpose of sealing and verifying content. Each tool is essential and contributes to a complete workflow without redundancy.

Completeness5/5

The tool surface covers the full lifecycle: sealing content, checking its status, verifying, and obtaining the public key for verification. No obvious gaps exist for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources