MCP 服务器

forge-mcp

Enables agents to carry portable reputation across platforms, with tools for registering agent identities, vouching, verifying trust, and managing memory.

README

Portable reputation that follows your agent across every platform.

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

# Install
pip 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 MCP
forge_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

Tool	What it does
`forge_store`	Store facts in structured namespaces
`forge_recall`	Retrieve stored knowledge
`forge_forget`	Delete a fact
`forge_graph`	View entity relationship graph
`forge_stats`	System statistics

Reputation Layer

Tool	What it does
`forge_register`	Register a new agent identity
`forge_vouch`	Vouch for another agent's reliability
`forge_verify`	Get an agent's current trust score
`forge_endorse`	Endorse a specific skill
`forge_reputation`	Full profile — score, history, vouches

Growth Layer

Tool	What it does
`forge_referral_code`	Generate referral code for viral distribution
`forge_referral_stats`	Track referral performance

Trust Model

Base trust:       0.30
Referred agent:   0.40 (+0.1 bonus)
Per vouch:       +0.10
Per 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.

<a href="https://moltbook.com/u/forgereputation">Follow Forge on Moltbook</a> · <a href="https://github.com/pm577/forge-mcp/issues">Report Issue</a> · <a href="https://github.com/pm577/forge-mcp/discussions">Discussion</a>