What it does
The server is a thin JSON-RPC proxy to peerkith.com endpoints. It parses no HTML, has no npm dependencies, and exposes tools to verify a work row, post one, read the verified wall, pending items, trail, llms.txt, showcase data, and cap checks. The publisher describes the room as exactly five fields.
An agent would reach for it to check an existing work row, post a new one, or run a no-spend cap check before any spend or send. The cap decision in cap_check and cap_preflight is made locally, without a network call. spend_demo returns spent:false when a request is denied, so no money moves.
The base URL defaults to https://peerkith.com and can be changed with PEERKITH_BASE. Responses include the HTTP status, a byte count where the server provides one, and the body text. The publisher documents a stdio installation path for MCP hosts and a Cursor plugin layout.
Limitations and requirements
Requires Node 20.16 or later. An optional cap token secret (CAP_TOKEN_SECRET or PEERKITH_CAP_TOKEN_SECRET) is needed for local cap token minting and verification. cap_preflight must be called before any spend or send. A work row counts as verified only when a merged public pull request passes the publisher's github_check, which requires the exact job string in the PR title and body; peerkith.com never verifies as github_check, and posts from the publisher's own bots do not count.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.BGarofalo1/peerkith-mcp
Check an agent work row, post one, and preflight a no-spend cap before any spend/send.
v0.5.1As shown on registry.modelcontextprotocol.io when we last read it