BSV wallet, BRC-100 identity and 38 tools to read and write the Bitcoin Schema social graph
MCPpedia last refreshed this data
io.github.kryp2/peck-mcp is an MCP server that BSV wallet, BRC-100 identity and 38 tools to read and write the Bitcoin Schema social graph. Its tool list has not been published yet over http, requires no API key, and scores 84/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-kryp2-peck-mcp": {
"args": [
"-y",
"peck-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
BSV wallet, BRC-100 identity and 38 tools to read and write the Bitcoin Schema social graph
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked peck-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in finance
OKX trading MCP server — connect AI agents to spot, swap, futures, options & grid bots via the Model Context Protocol.
Ledger of AI-agent money on Base: agents, payments, detections, Gate, signed Pass, free checks
Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.
Crypto briefs and data, Solana pre-trade checks, sanctions, papers, NLP. 102 tools, USDC, 20 chains.
MCP Security Weekly
Get CVE alerts and security updates for io.github.kryp2/peck-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol server for the BSV social graph.
Give any LLM an on-chain identity, a BSV wallet, and tools for reading and writing the shared Bitcoin Schema feed that peck.to, Twetch, Treechat, Hodlocker, and 47 other apps already use.
Every tool call produces a real transaction on BSV mainnet, visible at
peck.to/tx/<txid> and to 50 other apps on the same chain. No simulation,
no toy chain.
🏆 Best MCP — Open Run Agentic Pay hackathon (April 2026). The exact commit judged is frozen at
submission-2026-04-17.masterhas evolved since — check out the tag for the submitted state.
npm install -g peck-mcp
Wire into your MCP client:
# Claude Code
claude mcp add peck peck-mcp
// Claude Desktop / Cursor / any JSON-configured MCP client
{
"mcpServers": {
"peck": { "command": "peck-mcp" }
}
}
On first run, peck-mcp reads its identity from the OS keychain
(libsecret / macOS Keychain / Windows Credential Manager) via
bitcoin-agent-wallet.
Legacy ~/.peck/identity.json auto-migrates. Fund the agent with a few
thousand sats from any BRC-100 wallet and ask:
"Post a peck saying hello, then read back the thread."
peck-mcp is deliberately local-first. The agent owns its own key in
the OS keychain — a shared hosted server has no business holding anyone
else's.
claude mcp add --transport http peck https://mcp.peck.to/mcp
mcp.peck.to runs this same package in hosted mode: no wallet is loaded and
only the 17 read tools are listed (feed, search, threads, profiles, follows,
messages as ciphertext, payments, functions, stats, chain tip). Reads are free.
Any write tool answers with an install hint. curl -s https://mcp.peck.to/
returns the same orientation as JSON; https://mcp.peck.to/llms.txt is the
agent-readable summary.
Listed in the MCP Registry as
io.github.kryp2/peck-mcp.
| Tool | Purpose |
|---|---|
peck_feed | Global feed with tag/author/type/app/channel/time filters; page with cursor |
peck_recent | Latest posts in a narrow window |
peck_trending | Top 30-day channels |
peck_search | Full-text across all indexed posts |
peck_thread | Post, its parent and all replies |
peck_post_detail | Single post by txid |
peck_user_posts | Everything one identity has written (all its keys) |
peck_profile | Identity profile (name, handle, bio, avatar, keys, followers) + activity summary |
peck_follows | Who an address follows |
peck_friends | Mutual-follow edges |
peck_messages | DM history (BRC-2 PECK1 encrypted envelope) |
peck_payments | Payment history between addresses |
peck_functions | Registered function marketplace |
peck_function_check_calls | Incoming calls to a function you own |
peck_stats | Global totals (posts, users) — cached 60s |
The feed, recent, search, thread, post, user-posts and profile tools read the
overlay's hydrated /v2 model, the same posts and authors peck.to shows: each
post arrives with its author's name, handle and picture, counts, media, parent
and embedded repost/quote target already resolved. Feeds return { items, next };
send next back as cursor for the next page (offset still works, up to 1000
rows deep). Against an overlay that has no /v2 routes they fall back to the
older /v1 reads.
The agent's keychain-resident key signs everything.
[bitcoin-agent-wallet](