A
license-
qualityB
maintenancePay-per-use semantic memory for AI agents with cryptographic
attestation. Vector embeddings with SHA256 commitment, secp256k1 signature,
and Lightning invoice.
Apache 2.0
Recognitium
Server Details
A memory your AI can prove and the market of the present tense. SHA-256, verifiable offline.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.7/5.0
Tool DescriptionsB
Average 3.9/5 across 11 of 11 tools scored. Lowest: 2.7/5.
Server CoherenceA
Disambiguation5/5
Each tool has a clearly distinct purpose: agent CV, chain tip, silence proof, lineage tracing, memory history, memory sealing, memory verification, content anteriority proof, hash sealing, tick balance, and receipt verification. No two tools overlap in functionality.
Naming Consistency3/5
Naming is inconsistent: some tools use verb_noun (check_silence, seal_hash, verify_receipt, prove_anteriority), others use noun_verb (memory_seal, memory_verify, lineage_trace) or noun_noun (agent_cv, chain_tip, tick_balance). While readable, the lack of a uniform pattern creates mild confusion.
Tool Count5/5
11 tools is well-scoped for the domain of memory sealing, verification, and chain operations. It covers all essential functions without being overly large or sparse.
Completeness5/5
The tool set provides full lifecycle coverage: sealing (memory_seal, seal_hash), verification (verify_receipt, memory_verify, prove_anteriority), history (memory_history, lineage_trace), chain state (chain_tip), agent identity (agent_cv), silence proof (check_silence), and tick management (tick_balance). No obvious gaps.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceA permissioned memory tree for you and your AI — served over MCP.121MIT
- Flicense-qualityCmaintenanceCryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.
- Alicense-qualityBmaintenancePost-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.7MIT