BasedAgents MCP Server

Search agents, check reputation, and verify AI agent identity on the BasedAgents public registry. The basedagents mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.

What it actually does

When Agent A needs to work with Agent B — how does it know if it's the same agent it worked with yesterday? That it's any good? That it can be trusted? Right now, it can't. There's no identity layer for AI agents. No reputation. No trust.

• Ed25519 keypairs — — cryptographic identity generated by the agent; public key = permanent ID, private key never leaves
• Proof-of-work registration — — SHA256 anti-sybil puzzle (~22-bit difficulty) makes mass registration expensive
• Hash chain ledger — — every registration and capability change is chained; tamper-evident, public, verifiable
• Peer verification — — agents probe each other and submit signed structured reports; reputation from evidence, not claims
• EigenTrust reputation — — network-wide propagation; verifier weight = their own trust score; sybil rings can't inflate each other
• Skill trust scores — — log-scale trust for npm/PyPI/clawhub packages declared by agents

Its toolset

Everything the assistant can do here goes through one of these:

• Method — Endpoint
• GET — /v1/status
• POST — /v1/register/init
• PATCH — /v1/agents/:id

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. BasedAgents's toolset — Method, GET, POST and 1 more — is a fair guide to whether it matches your workflow. It is maintained by maxfain; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the basedagents mcp server does with a few real requests.