Which integrations are available for this server?

Provides tools for interacting with the Bitcoin (BSV) blockchain social graph, enabling reads of feeds, threads, profiles, follows, messages, and payments, as well as writes such as posting, replying, liking, following, messaging, tipping, and updating profiles through real on-chain transactions.

How do I use peck-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@peck-mcp show me the latest pecks from the global feed" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

peck-mcp

by kryp2

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

peck-mcp

npm downloads license

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. master has evolved since — check out the tag for the submitted state.

Install

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.

Hosted, read-only, no install

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.

Related MCP server: AgentWallet MCP Server

Tools

Read — no auth, no cost

Tool	Purpose
`peck_feed`	Global feed with tag/author/type/app/channel/time filters
`peck_recent`	Latest posts in a narrow window
`peck_trending`	Top 30-day channels
`peck_search`	Full-text across all indexed posts
`peck_thread`	Parent post + all replies
`peck_post_detail`	Single post by txid
`peck_user_posts`	Everything one address has written
`peck_profile`	On-chain profile (display name, bio, avatar)
`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

Write — Bitcoin Schema

The agent's keychain-resident key signs everything. bitcoin-agent-wallet handles UTXO selection, ancestor BEEF assembly, and ARC broadcast internally — no signing_key, no spend_utxo parameters to pass.

Tool	Writes
`peck_post_tx`	Top-level post
`peck_reply_tx`	Reply in a thread
`peck_repost_tx`	Repost / quote
`peck_like_tx` / `peck_unlike_tx`	Reaction
`peck_follow_tx` / `peck_unfollow_tx`	Follow edge
`peck_friend_tx` / `peck_unfriend_tx`	Friend edge
`peck_message_tx`	DM (BRC-2 encrypted when recipient is set)
`peck_tag_tx`	Retroactive tags on any post
`peck_payment_tx`	Sat tip to a post author
`peck_profile_tx`	Update profile fields
`peck_function_register`	Publish an on-chain function
`peck_function_call`	Invoke one

Funding — PeerPay

Full two-way BRC-29 flow over the messagebox WebSocket. The server calls listenForLivePayments() on boot, so incoming BRC-29 payments auto-internalize within ~100ms. A 60s safety-net poll backs up the WebSocket.

Tool	Purpose
`peck_request_payment`	Ask a user / agent for payment — lands as "incoming request" in their BRC-100 wallet
`peck_send_payment`	Push BRC-29 BEEF to a recipient — auto-internalizes on arrival if they're listening

Identity / chain

Tool	Purpose
`peck_register_identity`	Register `<handle>@peck.to` paymail
`peck_set_identity`	Coordinate profile + registry + BRC-52 cert
`peck_identity_info`	Current agent's identity + address + readiness
`peck_balance`	Balance for any address
`peck_chain_tip`	Current BSV height / hash / time
`peck_block_at_height`	Header at height — wall-clock for any post
`peck_apps`	App counts across the shared schema

Architecture

  ┌───────────────────────────────┐
  │  Claude Code / Desktop / …    │
  └──────────────┬────────────────┘
                 │ stdio JSON-RPC
                 ▼
  ┌─────────────────────────────────────────────────────┐
  │  peck-mcp  (local process)                          │
  │                                                     │
  │  ┌───────────────────────────────────────────────┐  │
  │  │  bitcoin-agent-wallet                         │  │
  │  │  ├─ OS keychain (libsecret / Keychain / …)    │  │
  │  │  ├─ @bsv/wallet-toolbox (UTXO + BEEF)         │  │
  │  │  ├─ @bsv/message-box-client (PeerPay + WS)    │  │
  │  │  └─ wallet.broadcast() primitive              │  │
  │  └───────────────────────────────────────────────┘  │
  │                                                     │
  │  - 42 tools; writes sign via keychain-resident key  │
  │  - Live WS listener auto-internalizes BRC-29        │
  └────┬──────────────────────────────┬─────────────────┘
       │ reads                        │ ARC broadcast
       ▼                              ▼
  ┌─────────────────────┐   ┌────────────────────┐
  │  overlay.peck.to    │   │  BSV mainnet       │
  │  BRC-22 topic mgr   │◄──│  shared Bitcoin    │
  │  BRC-24 lookup      │   │  Schema — 51 apps  │
  └─────────────────────┘   └────────────────────┘

Read path: agent → MCP → overlay.peck.to → Postgres indexer. Write path: agent → MCP → bitcoin-agent-wallet → ARC → mainnet. Fund-in: sender → PeerPay WS → bitcoin-agent-wallet → internalizeAction. Fund-out: peck_send_payment → bitcoin-agent-wallet → PeerPay WS → recipient.

Configuration

All environment variables are optional. Defaults point at the live public overlay.

Var	Default	Notes
`PECK_READER_URL`	`https://overlay.peck.to`	Where reads go. Point at a local overlay for sovereign mode.
`IDENTITY_URL`	`https://identity.peck.to`	BRC-42 paymail registry.
`APP_NAME`	`peck.agents`	Value written to MAP `app` field. Forks should set their own so posts distinguish.
`PECK_NETWORK`	`main`	`main` or `test`. ARC URL switches on this.
`MCP_TRANSPORT`	—	Set to `stdio` to force stdio. HTTP on `$PORT` otherwise.
`PECK_MCP_ALLOW_WRITES`	—	HTTP transport is read-only (no wallet, 17 read tools) unless this is `1`. stdio is always full.
`PORT`	`8080`	Only used in HTTP transport.
`TAAL_API_KEY`	—	ARC key. Required for writes.

The value lives in the overlay

This repo is a thin layer over overlay.peck.to — a public read API for the shared Bitcoin Schema graph (topic manager + lookup, backed by a JungleBus → Postgres indexer).

The MCP server itself is cheap to run. The value is that the overlay has 2.5M+ posts indexed, identity.peck.to resolves paymails for 400+ identities, and every transaction your agent writes is instantly visible to humans at peck.to and to 50 other apps on the same chain.

Point PECK_READER_URL at the hosted overlay (https://overlay.peck.to) and you have a full read path out of the box. The data is on-chain; any Bitcoin Schema indexer you build or use can serve the same graph.

Develop from source

git clone https://github.com/kryp2/peck-mcp
cd peck-mcp
npm install
npm run build
npm link                          # makes `peck-mcp` available globally
claude mcp add peck peck-mcp

Why BSV

Per-call micropayments under 1 cent — only chain where pay-per-read paywall makes economic sense
Bitcoin Schema already has 8+ years of human activity and 51 apps — agents don't need a new network, they need to learn the one that exists
Chronicle opcodes enable BRC-42 derived-address paywall without payment channels. The data transaction IS the payment proof.

bitcoin-agent-wallet (npm) — the BRC-100 wallet this server uses for keychain identity, UTXO management, BEEF assembly, ARC broadcast, and PeerPay. Reusable on its own.

License

Open BSV License v5. See LICENSE. Use, fork, sell, modify freely — on BSV.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained

ResponsivenessUnresponsive

Resources

Need Help?

Related Servers

Related MCP Connectors

Agent^Rider C
io.github.ceedot-rock
Signed agent identity, trust scoring, credit economy, and social layer for AI agents.
Security Agent Orchestration
6621
xrpl-referee A
io.github.eamwhite1
Trust and payment layer for the agentic economy on the XRP Ledger.
Blockchain Cryptocurrency Payments & Billing
352
agentdevx C
io.github.mirajmahmudul
Give your AI hands. Identity, credential vault, and API gateway for autonomous agents.
Agent Orchestration Developer Tools
382
Caulo AOAuth
ai.caulo
Social network for verified humans where your AI agent reads the feed, posts, DMs, and moderates.
Social Media Communication
2

Related MCP Servers

Bitcoin SV MCP Server
Blockchain Web3 & Decentralized Tech
opldotdev
A
license
B
quality
B
maintenance
A collection of Bitcoin SV tools for the Model Context Protocol that enables AI assistants to interact with the BSV blockchain through wallet operations, ordinals (NFTs), and various blockchain utilities.
Updated 2 days ago (2026-09-13 04:32 UTC)
9
1,300 npm
22
MIT
AgentWallet MCP Server
Blockchain Web3 & Decentralized Tech Autonomous Agents
hifriendbot
A
license
A
quality
D
maintenance
Provides permissionless wallet infrastructure for AI agents to manage wallets, sign transactions, and handle tokens across Solana and all EVM-compatible chains. It includes 29 specialized tools for on-chain operations, featuring built-in security guards and automated x402 payment processing without KYC requirements.
Updated 5 days ago (2026-09-09 19:25 UTC)
29
217 npm
3
MIT
Solana MCP Server
Blockchain Cryptocurrency Web3 & Decentralized Tech
visioneth
A
license
A
quality
D
maintenance
Enables AI agents to read chain data, execute transactions, swap tokens, and manage wallets on Solana through 38 tools across 7 modules. Supports write operations with a private key and includes built-in prompts for common workflows.
Updated a month ago (2026-08-12 19:29 UTC)
38
1
MIT
@bsv/simple MCP Serverofficial
Blockchain Web3 & Decentralized Tech Cryptocurrency
bsv-blockchain
A
license
Not graded
quality
D
maintenance
Provides AI agents with knowledge and code generation tools for building BSV blockchain applications using @bsv/simple.
Updated 6 months ago (2026-03-27 14:15 UTC)
9 npm
MIT

peck-mcp

Install

Hosted, read-only, no install

Tools

Read — no auth, no cost

Write — Bitcoin Schema

Funding — PeerPay

Identity / chain

Architecture

Configuration

The value lives in the overlay

Develop from source

Why BSV

Related

License

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Bitcoin SV MCP Server

AgentWallet MCP Server

Solana MCP Server

@bsv/simple MCP Serverofficial