Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

peck-mcp

by kryp2version 0.7.0i★ –iRuns in the cloud
Registry nameio.github.kryp2/peck-mcp

Install

Overview

Description from the maker (original English)

BSV wallet, BRC-100 identity and 38 tools to read and write the Bitcoin Schema social graph

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Crypto & blockchain

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://mcp.peck.to/mcp

Run this in your terminal

claude mcp add --transport http peck https://mcp.peck.to/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "peck": {
      "url": "https://mcp.peck.to/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "peck": {
      "type": "http",
      "url": "https://mcp.peck.to/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://mcp.peck.to/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account kryp2, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Crypto & blockchaini

  • More stars than 0% of the other 1611 servers in this category
  • Published to the registry more recently than 46% of the other 1611 servers in this category
  • Basic checks equal to or better than 100% of the other 1611 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is peck-mcp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.7.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Bellchain, Quidli Connect, Diamond Bitcoin Intelligence

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Bellchain

by bellchain-app

Crypto alert chains in your AI assistant: check alerts, test ideas with the replay, build chains.

Runs on your computerUpdated today
Install

Resolve social handles to wallets, score onchain reputation, pay in any ERC-20, SPL or native.

Computer or cloudUpdated today
Install

Diamond Bitcoin Intelligence

by diamond.btc-intel.workers.dev

Bitcoin MCP: fee budgets, retained-block inclusion proofs and risk checks. Free service discovery.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

peck-mcp

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/ 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.

Tools

Read — no auth, no cost
ToolPurpose
peck_feedGlobal feed with tag/author/type/app/channel/time filters; page with cursor
peck_recentLatest posts in a narrow window
peck_trendingTop 30-day channels
peck_searchFull-text across all indexed posts
peck_threadPost, its parent and all replies
peck_post_detailSingle post by txid
peck_user_postsEverything one identity has written (all its keys)
peck_profileIdentity profile (name, handle, bio, avatar, keys, followers) + activity summary
peck_followsWho an address follows
peck_friendsMutual-follow edges
peck_messagesDM history (BRC-2 PECK1 encrypted envelope)
peck_paymentsPayment history between addresses
peck_functionsRegistered function marketplace
peck_function_check_callsIncoming calls to a function you own
peck_statsGlobal 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.

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.

ToolWrites
peck_post_txTop-level post
peck_reply_txReply in a thread
peck_repost_txRepost / quote
peck_like_tx / peck_unlike_txReaction
peck_follow_tx / peck_unfollow_txFollow edge
peck_friend_tx / peck_unfriend_txFriend edge
peck_message_txDM (BRC-2 encrypted when recipient is set)
peck_tag_txRetroactive tags on any post
peck_payment_txSat tip to a post author
peck_profile_txUpdate profile fields
peck_function_registerPublish an on-chain function
peck_function_callInvoke 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.

ToolPurpose
peck_request_paymentAsk a user / agent for payment — lands as "incoming request" in their BRC-100 wallet
peck_send_paymentPush BRC-29 BEEF to a recipient — auto-internalizes on arrival if they're listening
Identity / chain
ToolPurpose
peck_register_identityRegister @peck.to paymail
peck_set_identityCoordinate profile + registry + BRC-52 cert
peck_identity_infoCurrent agent's identity + address + readiness
peck_balanceBalance for any address
peck_chain_tipCurrent BSV height / hash / time
peck_block_at_heightHeader at height — wall-clock for any post
peck_appsApp 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.

VarDefaultNotes
PECK_READER_URLhttps://overlay.peck.toWhere reads go. Point at a local overlay for sovereign mode.
IDENTITY_URLhttps://identity.peck.toBRC-42 paymail registry.
APP_NAMEpeck.agentsValue written to MAP app field. Forks should set their own so posts distinguish.
PECK_NETWORKmainmain 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.
PORT8080Only 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.

Related

  • 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.

Ask PopNx