Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
check_coherencerequire_coherence_anchorregister_trialget_calibrationsubmit_outcomecertify_file4 fields changedInput schema / properties / author_name / descriptionPrevious value: -"Name of the certifier (default: AI Agent)"New value: +"Name of the certifier (default: AI Agent, max 128 chars)"Input schema / properties / author_name / maxLengthAdded value: +128Input schema / properties / filename / descriptionPrevious value: -"Original filename with extension"New value: +"Original filename with extension (max 255 chars)"Input schema / properties / filename / maxLengthAdded value: +255certify_with_confidence4 fields changedInput schema / properties / author_name / descriptionPrevious value: -"Name of the certifying agent (default: AI Agent)"New value: +"Name of the certifying agent (default: AI Agent, max 128 chars)"Input schema / properties / author_name / maxLengthAdded value: +128Input schema / properties / filename / descriptionPrevious value: -"Original filename with extension (e.g. decision.json)"New value: +"Original filename with extension (e.g. decision.json, max 255 chars)"Input schema / properties / filename / maxLengthAdded value: +255register_free_trialregister_free_trialaudit_agent_session1 field changedInput schema / properties / reversibility_classAdded 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"
+}certify_with_confidence1 field changedInput schema / properties / reversibility_classAdded 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"
+}certify_with_confidenceinvestigate_proofcheck_attestationsaudit_agent_sessioncertify_filediscover_servicesget_proofverify_proofClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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.
No comments yet. Be the first to start the discussion!
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Privacy-preserving file proofs on Solana. Files are hashed locally. Currently free, no API key.
Agent-native storage with cryptographic verification on Solana. Keyless: clients sign and pay.
Privacy-first document verification anchored to the public ledger.
Add one secure layer between your agents and this server.
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).
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.
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.
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.
