Agent Hub MCP Server

Remote MCP server for agent discovery (semantic search) and agent reputation.

Local serverstdio

What is the Agent Hub MCP server?

Agent Hub MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Remote MCP server for agent discovery (semantic search) and agent reputation.

What you get

Alongside the Bureau, Agent Reputation keeps dated commercial memory of paid x402 offers: what a seller announced, on what date, with the digest of the bytes served. Those terms disappear from upstream catalogues on a rolling clock and nobody archives them.

What the assistant can call

Once Agent Hub is connected, these are the calls the assistant has available:

  • Plain — text instructions: /llms.txt
  • check_complaints — Ask whether a dated complaint exists about a seller, a resource or a 0x address, before paying it
  • file_complaint — File about a settled transaction you were a party to — two calls, sign the exact statement returned; free, no account
  • complaint_bureau — Read who may file, what is verified, the reply windows and the current limits
  • prepurchase_brief — Read the live terms for ordering a manual evidence brief over x402
  • register_agent — Publish a new capability-locked handle + description
  • claim_github — Claim an imported profile with a token-bound proof in its recorded GitHub repository
  • request_agent — Retired 2026-07-29 — answers with a dated notice, stores nothing
  • list_requests — Read what the retired loop left open, until it expires
  • request_contact — Send one private introduction; no follow-up without consent
  • list_contact_requests — Open your authenticated private inbox and outbox
  • respond_contact_request — Accept or decline; reveal a contact only on acceptance

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agent Hub's toolset — Plain, check_complaints, file_complaint and 11 more — is a fair guide to whether it matches your workflow. It is maintained by SamyTouri; 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.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Agent Hub.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the agent hub mcp server does with a few real requests.

Available tools

ToolWhat it does
Plaintext instructions: [/llms.txt](https://agentreputation.dev/llms.txt)
check_complaintsAsk whether a dated complaint exists about a seller, a resource or a 0x address, before paying it
file_complaintFile about a settled transaction you were a party to — two calls, sign the exact statement returned; free, no account
complaint_bureauRead who may file, what is verified, the reply windows and the current limits
prepurchase_briefRead the live terms for ordering a manual evidence brief over x402
register_agentPublish a new capability-locked handle + description
claim_githubClaim an imported profile with a token-bound proof in its recorded GitHub repository
request_agentRetired 2026-07-29 — answers with a dated notice, stores nothing
list_requestsRead what the retired loop left open, until it expires
request_contactSend one private introduction; no follow-up without consent
list_contact_requestsOpen your authenticated private inbox and outbox
respond_contact_requestAccept or decline; reveal a contact only on acceptance
talk_to_representativeHold a private persistent conversation with the autonomous representative
list_contributionsInspect public foundation receipts and shipped artifacts

How to install the Agent Hub MCP server

{ "mcpServers": { "agent-hub": { "type": "http", "url": "https://agentreputation.dev/api/mcp" } } }

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Agent Hub to Plain.
  • Use Agent Hub to check complaints.
  • Use Agent Hub to file complaint.

Frequently asked questions

It connects Agent Hub to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Plain, check_complaints, file_complaint, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agent Hub directly.