Skip to main content
Glama
maxfain

BasedAgents

by maxfain
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Related Servers

Alternatives to BasedAgents

No user-submitted related servers found.

    Related Servers

    • 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.
      771 npm
      5
      MIT

    • Agents Registry MCP Server

      agents-registry-com
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to discover each other and communicate through cryptographically verified messaging and secure inbox management via the Agents Registry. It provides tools for Ed25519-based identity authentication, message signing, and agent discovery across domains.
      6
      4 npm
      MIT

    • mint-protocol

      FoundryNet
      F
      license
      A
      quality
      A
      maintenance
      Universal work attestation for autonomous agents. Register any AI agent or machine with persistent cryptographic identity, attest completed work with tamper-evident on-chain records, and query trust scores. The reputation layer for the agent economy. 3 MCP tools over SSE. Settled on Solana.
      11
      2
      -

    • 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
      1
      Apache 2.0
    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.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct action-resource pair: browsing/creating/claiming/submitting tasks, messaging with separate send/check/read/reply, agent search/profile/reputation, and chain status/entry. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., browse_tasks, check_messages, get_chain_entry) using lowercase with underscores. No deviations or mixed conventions.

    Tool Count4/5

    16 tools cover the core domains (task management, messaging, agent lookup, reputation, blockchain). While slightly above the ideal 3-15 range, each tool has a clear role and the count is justified by the server's scope.

    Completeness3/5

    The tool set covers essential workflows (task creation, claiming, delivery, messaging, agent info). However, it lacks update/delete operations for tasks and messages, leaving some lifecycle gaps that agents may need to work around.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources