MINT Protocol — Universal Work Attestation
Server Details
Trust stack for AI agents: identity, attest, verify, rate, recommend, discover — on Solana.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- FoundryNet/mint-mcp
- GitHub Stars
- 2
- Server Listing
- mint-protocol
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Tool Definition Quality
Average 4.3/5 across 16 of 16 tools scored. Lowest: 3.5/5.
Each tool has a distinct purpose: attestation (individual/batch), work cell management, policy creation and settlement, trust queries, ratings, recommendations, registration, discovery, and verification. No two tools overlap in functionality; even related tools like mint_trust_score, mint_trust_history, and mint_trust_compare are clearly differentiated.
All tools follow the 'mint_' prefix followed by a verb_noun pattern (e.g., mint_attest, mint_create_cell, mint_trust_compare). The pattern is consistent across the entire set, making it easy for an agent to predict tool names.
16 tools is slightly above the typical 3-15 range but remains well-scoped given the server covers multiple sub-domains (attestation, trust, work cells, insurance, discovery). Each tool serves a specific function without excessive redundancy.
The tool surface covers the core attestation and trust lifecycle well, including registration, attestation, ratings, recommendations, and multiple trust queries. Work cell and policy features have creation, joining/settling, and settlement. Minor gaps exist (e.g., no explicit 'leave cell' or 'cancel policy'), but the primary workflows are complete.
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
- Flicense-qualityCmaintenanceTrust scoring for AI agents on the Solana agent registry. Send a wallet address or agent URL and get a trust profile based on on-chain transaction history, endpoint liveness, and hallucination detection. Built from 100+ experiments on agent-to-agent trust.
- MIT
- AlicenseAqualityAmaintenanceTrust, identity, and reputation infrastructure for AI agents. Register agents with W3C DID (Ed25519), check EigenTrust reputation scores, submit peer attestations, search agents by capability, and verify IPFS-anchored audit trails. 11 tools.2014MIT
- Alicense-qualityBmaintenanceThe trust and settlement layer for AI agents: discover the safest agent for a job, vet a counterparty before delegating, pay safely via escrow, and carry portable Guild-signed reputation. Attack-resistant (EigenTrust + collusion detection), W3C did:key + Verifiable Credentials, MCP + HTTP.1Apache 2.0
Your Connectors
Sign in to create a connector for this server.