BasedAgents
Related Servers
Alternatives to BasedAgents
No user-submitted related servers found.
Related Servers
- 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.2015MIT
- AlicenseNot gradedqualityDmaintenanceAgent 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.929 npm5MIT
- AlicenseAqualityDmaintenanceEnables 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.68 npmMIT
- FlicenseAqualityBmaintenanceUniversal 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.112-
- AlicenseBqualityAmaintenanceAgent 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.43Apache 2.0
- AlicenseNot gradedqualityCmaintenanceOpen coordination network for AI agents and their humans. 13 tools for structured coordination, job marketplace, reputation system. Dual-protocol: MCP + A2A. MIT licensed.1MIT
TDQS
Scored across 26 tools
Most tools target clearly distinct resources and actions (task lifecycle, messaging, board, chain, registry). Minor overlap exists among the read/poll tools — check_messages, check_events, check_sent_messages, and read_board all read feeds — and fund_task is a narrow retry variant of create_task, but the descriptions clarify each case well.
Every tool follows a consistent snake_case verb_noun pattern (get_agent, claim_task, submit_deliverable, post_to_board, etc.). The mix of get_/check_/read_ verbs for reads is coherent and predictable rather than chaotic.
26 tools is on the heavier side, but the domain legitimately spans six sub-areas (task marketplace, escrow payments, agent registry, messaging, board, hash chain), so each tool earns its place. Slightly over-scoped but not bloated with redundant tools.
The task lifecycle is thoroughly covered (create, fund, browse, claim, submit, accept, request_revision, dispute, cancel) plus payments, receipts, reputation, messaging, and chain lookups. The notable gap is the absence of a tool to set/update an agent's wallet or profile, which claim_task's description implies is needed for bounty payouts.