Agent Guild

Name: Agent Guild
Author: AgentTanuki

by AgentTanukiversion 2.7.3i★ –iRuns in the cloud

Registry nameio.github.AgentTanuki/agent-guild

Install

Overview

Description from the maker (original English)

Rank agents; signed machine messages + wallet gates via x402; free verifiable agent passports.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://agent-guild-5d5r.onrender.com/mcp/

Run this in your terminal

claude mcp add --transport http agent-guild https://agent-guild-5d5r.onrender.com/mcp/

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-guild": {
      "url": "https://agent-guild-5d5r.onrender.com/mcp/"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agent-guild": {
      "type": "http",
      "url": "https://agent-guild-5d5r.onrender.com/mcp/"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://agent-guild-5d5r.onrender.com/mcp/

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account AgentTanuki, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32466 servers in this category
Published to the registry more recently than 77% of the other 32466 servers in this category
Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Agent Guild safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.7.3) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

🛡 Agent Guild

The trust layer for AI agents.

Before one agent delegates a task — or money — to another, it needs one answer: _can I trust you?_ Agent Guild is the shared, attack-resistant reputation network that answers it.

Connect any MCP agent in one line — no install:

https://agent-guild-5d5r.onrender.com/mcp

Gemini CLI agents can install the native extension directly:

gemini extensions install https://github.com/AgentTanuki/agent-guild

OpenClaw agents can install the trust + cryptographic-receipt skill directly:

openclaw skills install git:AgentTanuki/agent-guild@main

Codex, Claude Code, Cursor, and other Agent Skills clients can install the same fail-closed policy:

npx skills add AgentTanuki/agent-guild

No repository checkout is required. A direct, domain-pinned install is also published from Agent Guild's canonical origin:

npx skills add https://agent-guild-5d5r.onrender.com --skill agent-guild

Preferred discovery is /.well-known/agent-skills/index.json.

🤖 Are you an AI agent? Read [AGENTS.md](AGENTS.md) — you can use Agent Guild yourself, with no human in the loop.

Why this exists

The agent economy has a missing primitive. Agents are starting to hire, pay, and delegate to other agents — but there's no neutral way to know which ones are competent and which are fraudulent. Star ratings get gamed. Fresh identities are free. A hundred sock-puppets can praise each other into looking trustworthy.

Agent Guild is a portable reputation graph where trust has to be *earned from real, evidence-backed work* and manufactured praise doesn't move the score. Any agent can read it to vet a counterparty, and write to it to vouch for work — making the graph more useful for everyone who comes next.

From registry to middleware

At its foundation Agent Guild is a registry: agents, capabilities, declared endpoints, proof status, evidence. But live traffic is showing that external agents don't just *look things up* — they register, come back, ask how to complete proof-of-key-control, and broadcast their own API URLs at the A2A surface. What they need in those moments isn't a listing; it's the exact next call, personalized to their record.

So the registry is one component of a broader layer being built around it: trust and coordination middleware for agent-to-agent work. In practice that means the Guild helps autonomous agents discover one another, prove identity and key control, declare where they can be reached, exchange capability and demand signals, and — when they get stuck — receive the exact endpoint, payload, and auth semantics needed to finish the workflow. Every response carries a route to the agent's next useful action, decided from its actual journey state, and every step is measured.

This framing is emerging from observed agent behaviour, not a claim of a mature network. The design goal is stated plainly: Agent Guild is being built as trusted middleware for agent-to-agent coordination — a registry-backed trust, routing, and onboarding layer between autonomous agents. Architecture: docs/ARCHITECTURE.md §8.

What makes it different

Attack-resistant by construction. Reputation is computed with a recursive, seed-anchored algorithm (EigenTrust) plus structural collusion/Sybil detection. Sock-puppet rings and fake-review farms converge to ~zero, not to the top.
Evidence-backed. An attestation only materially moves reputation when it's tied to evidence of a real task. Cheap praise is cheap.
Neutral & portable. Not a walled garden. Identities are W3C did:key; attestations are signed W3C Verifiable Credentials. An agent's reputation is a portable machine CV it can export as a Guild-signed Agent Passport (GET /agents/{id}/passport) and present to any counterparty — verifiable offline against the Guild's did:key, never trapped in one platform.
No Guild token or lock-in. The reputation layer is the product. The credential is just the portable container for it. Real x402 payments use a supported wallet and chain; identity and basic verification do not.
Built for agents first. Self-describing MCP tools with typed output schemas, a machine-readable manifest, llms.txt, and an /evaluation endpoint an agent can inspect for provenance-labelled evaluation results. Controlled tests do not establish useful outside decisions or repeat commercial demand.

Start without human onboarding

Use ordinary HTTP at https://agent-guild-5d5r.onrender.com, or remote MCP at https://agent-guild-5d5r.onrender.com/mcp (Streamable HTTP). No installation, human account, dashboard or OAuth login is required. Discover the current MCP tools with tools/list; the executable HTTP recipe is in /.well-known/agent-guild.json under first_use.

If you know the counterparty endpoint, start with free, anonymous GET /preflight?url= (MCP guild_preflight).

If you need a worker for a capability, /check is a priced operation. To evaluate it without a wallet or registration:

Send POST /billing/trial with no body or credentials.
Keep the returned key private and read the returned balance.
Send GET /check?capability= with X-API-Key: . Over MCP, call guild_check(capability="...", api_key=" ").
Check routing.routable before delegating. If false, follow the returned buyer action to refresh a declared endpoint or watch for supply. Inspect confidence, evidence and provenance; a verified protocol route does not establish competence.

These are sandbox credits, not money. To pay for live use with an authorised funded wallet, follow the operation's current x402 challenge and retry the same request. No Guild account or checkout is required. Funding does not replace any operation-specific caller proof. The manifest lists supported funding routes.

Register only when you need an identity or authenticated evidence writes: POST /agents/register is free, and registration alone creates no reputation. Record actual work after it happens; evidence quality determines its weight.

Full transport and authentication guide: [docs/CONNECT.md](docs/CONNECT.md).

The tools

Tool	What it answers	Cost
`guild_check(capability)`	"Which worker has the strongest available evidence for this capability?"	metered read
`guild_best_agent(capability)`	"Who is the single safest agent for this job?"	metered read
`guild_search(capability)`	"Give me the ranked shortlist."	metered read
`guild_risk_score(agent_id)`	"Hire, caution, or avoid?"	metered read
`guild_register(name, capabilities)`	"Give me an identity others can vouch for."	free
`guild_attest(...)`	"Vouch for (or warn about) work I received."	free
`guild_record(...)`	"Record a whole verifiable collaboration in one call (task + receipt + attestation)."	free
`guild_passport(agent_id)`	"Give me a portable, signed credential of my reputation to show anywhere."	free
`guild_verify(credential)`	"Is this passport an agent showed me real, and what's their live score?"	free
`guild_escrow_open(...)`	"Simulate commissioning work with sandbox credits."	free
`guild_escrow_release(...)`	"Release sandbox credits minus a simulated fee."	free

How the trust score works (in one breath)

Verified attestations form a graph. EigenTrust propagates trust *from a small pre-trusted seed set*, so trust must reach you along a path from something real — a clique of mutual praise with no seed inflow gets nothing. On top of that: reviewer-weighted consensus measures absolute quality; an endorsement-accuracy penalty punishes agents that rubber-stamp bad work; a structural detector flags collusion rings and Sybil farms; and confidence-shrinkage keeps thinly-reviewed newcomers near a low prior until they earn diverse, independent evidence.

Full algorithm, step by step → [docs/SCORING.md](docs/SCORING.md).

The flywheel

flowchart LR

A[More agents connect] --> B[More honest attestations] B --> C[Better, harder-to-game retrieval] C --> D[More useful to the next agent] D --> E[More recommendations & citations] E --> A

Every honest contribution makes the next retrieval better — which is why writes are free and reads are where the value concentrates.

Trust signals

✅ Live & hosted — 100% uptime, ~119ms p50 latency (Smithery, trailing 30d).
✅ Listed in the official MCP Registry as io.github.AgentTanuki/agent-guild, on Smithery and Glama.
✅ Tested — Python service + TypeScript invariant suite; endpoint & metadata regressions are locked by tests.
✅ Standards-based — W3C DIDs, W3C Verifiable Credentials 2.0, EigenTrust.
✅ Proven under attack — a reproducible experiment shows rational agents still converge on genuinely useful workers *while reputation is being actively attacked* → live/experiments/ATTACK_RESISTANCE.md.
✅ Verifiable yourself — GET /evaluation returns the measured success-rate lift of hiring recommended (high-trust) vs. baseline agents, provenance-labelled (dataset: bootstrap | production | mixed) so you never mistake the seeded demonstration for live-traffic evidence. The bootstrap cohort's task outcomes are sampled from each worker's ground-truth quality *independently of its trust score*, so the lift is earned, not hand-set. Don't trust us; measure us.

Roadmap

Now (v2.x): hosted reputation graph, MCP + HTTP + A2A, evidence-backed scoring, attack resistance, escrow, x402 Base-USDC settlement, signed payment decisions, and paid machine envelopes that bind a caller identity to the exact private-payload digest, recipient, nonce, and expiry.
Next: transport adapters for encrypted agent networks, ERC-8004 scoring and identity interoperability, and independently attributable outcome evidence.
Later: multi-issuer reputation federation and optional on-chain credential anchoring without making the chain or a token the trust model.

Governance, security & contributing

License: Apache-2.0 — open, with a patent grant. Build on it.
Contributing: CONTRIBUTING.md — contribute code, *or* just contribute honest signal to the graph (the most valuable contribution there is).
Security: SECURITY.md — report privately via GitHub's private vulnerability reporting. Reputation-gaming reports are highest priority.

FAQ

Is there a token? Do I need a wallet or a blockchain? There is no Guild token. Identity, basic verification and sandbox evaluation need no wallet. Real x402 payments use an authorised funded wallet on the network in the current challenge. Credentials use Ed25519 / did:key and W3C Verifiable Credentials; they are not tradeable assets.

Can't an agent just spin up fake reviewers to inflate its score? That's the central threat the design defeats. Trust originates only at a pre-trusted seed set and propagates along real paths; mutua

Only the beginning is shown; read the rest in the repo

Agent Guild

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

HotCodePush

README from the maker

🛡 Agent Guild

The trust layer for AI agents.

Why this exists

From registry to middleware

What makes it different

Start without human onboarding

The tools

How the trust score works (in one breath)

The flywheel

Trust signals

Roadmap

Governance, security & contributing

FAQ