Skip to main content
Glama
FoundryNet

mint-protocol

by FoundryNet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mint-protocol

No user-submitted related servers found.

    Related Servers

    • BasedAgents

      maxfain
      A
      license
      A
      quality
      C
      maintenance
      AI agent identity and reputation registry. Ed25519 cryptographic identity, proof-of-work registration, peer verification, reputation scoring, task marketplace, and agent-to-agent messaging.
      16
      185 npm
      Apache 2.0

    • moltbridge

      SageMindAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Agent network intelligence for trust verification, broker discovery, and capability matching. Ed25519 identity, graph-based trust scoring, USDC payments, and MCP tools for agent registration, search, and trust attestation.
      614 npm
      5
      MIT

    • Agent Guild

      AgentTanuki
      A
      license
      B
      quality
      B
      maintenance
      Agent trust checks, reputation and signed passports. Glama's build is a separate local Guild with an empty graph and its own issuer. Registrations and evidence stay local. Use the remote MCP connector for the shared hosted Guild; its free preflight and metered trust services are separate.
      43
      Apache 2.0
    • Aegis-ZK by aegis-zk

      Aegis-ZKofficial

      aegis-zk
      F
      license
      Not graded
      quality
      D
      maintenance
      On-chain trust verification for AI agent tools. Agents query skill attestations, audit levels, and risk scores before running third-party MCP servers, so you know what's safe before you execute.
      1
      -
    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

    A4.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool maps to a distinct action and resource: registering, attesting, verifying, rating, recommending, discovering, and the cell/policy lifecycle tools are clearly separated by their noun object. Even with similar 1-5 rating mechanics, rate targets attestations while recommend targets actor relationships, and the descriptions make that unambiguous.

    Naming Consistency4/5

    All tools share a consistent mint_ snake_case prefix and verb-first style, making them predictable. However, the set mixes bare verbs like mint_attest and mint_rate with explicit verb_noun forms like mint_create_cell and mint_settle_policy, so it is not a fully uniform pattern.

    Tool Count5/5

    At 11 tools, the server is well within the ideal range and each tool covers a meaningful protocol operation. The count is reasonable even though the server spans identity, attestation, work cells, and insurance.

    Completeness3/5

    The core identity/attestation/reputation lifecycle is well covered, but the cell and policy sub-domains have notable read-side gaps: there is no way to fetch or list cells/policies, check their current status, or set an actor's capabilities/MCP endpoint for discovery. Agents can create and settle resources but may lack the query tools needed to complete those workflows without external information.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources