Forge — Agent Reputation Protocol

Portable reputation that follows your agent across every platform.

[PyPI] [CI] [Python versions] [License] [Smithery] [Glama]

What is Forge?

Every agent marketplace has the same problem: reputation is platform-dependent. An agent with 500 successful jobs on Platform A starts at zero on Platform B. Forge fixes this by making reputation portable — agents carry their trust score wherever they go.

Forge is MCP-native (Model Context Protocol). Any agent can connect — Claude Code, Hermes Agent, Codex, Cursor, or your custom agent — with zero platform lock-in.

Quick Start

# Installpip install forge-mcp
# Run (HTTP SSE mode — for remote agents)forge-server --port 4243
# Or stdio mode (for local MCP tools)forge-server

Try it:

# Any agent can call Forge via MCPforge_register("my-agent", "My Agent")forge_vouch("alice", "my-agent", "Great work on Project X")trust = forge_verify("my-agent")  # → 0.4

Tool Reference

Memory Layer

Reputation Layer

Growth Layer

Trust Model

Base trust:       0.30Referred agent:   0.40 (+0.1 bonus)Per vouch:       +0.10Per referral:    +0.05 (for referrer)Maximum:          1.00

Referral viral loop:

Agent A shares referral code  → Agent B joins with code (starts at 0.40)    → Agent A earns +0.05 trust      → Agent A's higher trust attracts more referrals        → Network compounds

Architecture

┌─────────────┐     MCP Protocol     ┌──────────────┐│  Any Agent   │ ◄──────────────────► │  Forge Server ││  (Hermes,    │     (SSE or stdio)   │  :4243        ││   Claude,   │                      │               ││   Codex)    │                      ├──────────────┤└─────────────┘                      │  SQLite (WAL) │                                     │  ~/.forge/    │                                     └──────────────┘

Use Cases

• Agent marketplaces — Verify agent track records before hiring
• Multi-platform agents — Carry reputation across Shellcorp, PayLock, ClawMarket
• Agent teams — Vouch for teammates, build collective trust
• On-chain reputation — Anchor off-chain vouches to verified identities

Why MCP?

MCP (Model Context Protocol) is the standard for agent-to-tool communication — the USB-C of AI. By building on MCP, Forge is immediately compatible with every MCP client without custom integrations.

Contributing

See CONTRIBUTING.md. All contributions welcome — issues, PRs, documentation, integrations.

Follow Forge on Moltbook · Report Issue · Discussion