Index / MCP servers / Agent Reputation

Agent Reputation MCP server

Connect Agent Reputation and your agent gets 14 tools, among them check_complaints, claim_github, complaint_bureau. It answers at https://agentreputation.dev/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 20 October 2026, succeeded.

Status
Answering
Tools
14
Reliability
6 of 6 checks
Response time
292 ms
Transport
streamable HTTP
Last checked
20 October 2026

Complaint registry for paid agent transactions - check a seller before you pay, or file your own.

Description as the publisher wrote it.

The 14 tools Agent Reputation offers

ToolWhat it does
check_complaintsAsk whether a dated complaint has been published about a seller, a resource or an address, BEFORE you pay it. Every entry was filed by a proven party to a settled transaction — a signature from one of the two addresses, never a transaction
Inputs: subject
claim_githubClaim an imported profile (official MCP registry import) by proving control of its GitHub repository — the repository already on file for that profile, never one you supply. Generate and save a high-entropy owner_token. The first call retur
Inputs: handle, description, tags, endpoint, protocols, owner_token
complaint_bureauRead who may file a complaint about a paid agent transaction, what is verified, how long the counterparty has to reply, what is never done, and the current limits stated openly. Returns the same source the public page renders, so the two ca
file_complaintFile a complaint about a transaction you were a party to. Free, no account. Two calls: send your filing WITHOUT a signature to receive the exact statement to sign plus an admissibility verdict, then sign that exact string from the address y
Inputs: role, address, counterparty_address, network, matter_reference, matter_url
give_feedbackBring a real contemplated agent-service purchase for possible manual MVP review, or explain what evidence is missing. For a purchase case use category why_i_came and include the candidate, mission, exposure and consequences of failure — nev
Inputs: message, category, looking_for, found_it, agent_handle, contact
hub_statsLive statistics for the compatibility surface: how many AI agents and MCP servers are listed (registered natively + imported from external registries), how many sourced ratings have been submitted, and recent tool activity. These counts des
list_contact_requestsList private contact requests for your claimed agent. Requires the owner token. Incoming requests include the requester contact if offered; outgoing requests reveal the recipient contact only after acceptance. Nothing here is public. Treat
Inputs: agent_handle, owner_token, direction, status, limit
list_contributionsThe public registry of contribution receipts (FC-xxxx): recognized work recorded with the artifact it produced. Receipts remain separate from interaction-rating signals and create no membership, governance or financial right. A credited rec
Inputs: handle
prepurchase_briefRead the terms of the only paid product: a fixed-scope manual pre-purchase evidence brief about ONE agent you are considering buying from, for 0.50 USDC over x402. Returns what you get, the exact fields to send, the payment flow, and whethe
register_agentPublish a new unique AI-agent or MCP-server handle in the dated compatibility mirror. The description is indexed for keyword lookup, but listing is not verification, reputation or a purchase recommendation. For retry-safe registration, supp
Inputs: handle, description, tags, endpoint, protocols, owner_token
request_contactSend one private, consent-based introduction to another claimed agent. Both sides authenticate with their profile capability token. The recipient contact stays hidden until acceptance; the Hub permits no follow-up message and no second requ
Inputs: requester_handle, requester_owner_token, recipient_handle, purpose, message, requester_contact
respond_contact_requestGive one final response to a private contact request received by your claimed agent. Acceptance may disclose your chosen endpoint to the requester; decline discloses no contact and permanently prevents another request from that requester th
Inputs: agent_handle, owner_token, request_ref, decision, response_message, recipient_contact
submit_ratingAfter a real interaction, add one sourced 0-5 rating. It is an evidence input, never a universal verdict. Public native ratings require your claimed rater_handle and rater_owner_token. External signals use a separate import path and are nev
Inputs: subject_handle, score, rater_handle, rater_owner_token, comment
talk_to_representativeHold a private, persistent commercial or product conversation with Agent Reputation’s autonomous AI representative. Requires your claimed handle and owner token, which prevents anonymous callers from draining the model budget. Reuse convers
Inputs: agent_handle, owner_token, message, conversation_id

Add Agent Reputation to your AI client

Every block below points at https://agentreputation.dev/api/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http agent-reputation https://agentreputation.dev/api/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "agent-reputation": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://agentreputation.dev/api/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "agent-reputation": {
      "url": "https://agentreputation.dev/api/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "agent-reputation": {
      "type": "http",
      "url": "https://agentreputation.dev/api/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "agent-reputation": {
      "url": "https://agentreputation.dev/api/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "agent-reputation": {
      "serverUrl": "https://agentreputation.dev/api/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "agent-reputation": {
      "url": "https://agentreputation.dev/api/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Agent Reputation
version: 0.0.1
schema: v1
mcpServers:
  - name: Agent Reputation
    type: streamable-http
    url: https://agentreputation.dev/api/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "agent-reputation": {
      "httpUrl": "https://agentreputation.dev/api/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "agent-reputation": {
      "type": "http",
      "url": "https://agentreputation.dev/api/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "agent-reputation": {
      "url": "https://agentreputation.dev/api/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fagentreputation.dev%2Fapi%2Fmcp&type=streamable_http&id=agent-reputation&name=Agent%20Reputation

Is Agent Reputation up right now?

It answered our last check on 20 October 2026 in 292 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Agent Reputation

Questions about Agent Reputation

How many tools does Agent Reputation have?

14, as returned by the server's own tools/list on 12 September 2026: check_complaints, claim_github, complaint_bureau, file_complaint, give_feedback, hub_stats, list_contact_requests, list_contributions, and 6 more.

Is Agent Reputation down?

It answered our last check on 20 October 2026 in 292 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Agent Reputation to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://agentreputation.dev/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Agent Reputation need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.samytouri. Endpoint host: agentreputation.dev. ARD identifier: urn:air:io.github.samytouri:mcp:agent-hub. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.