Skip to content

peck-mcp server

io.github.kryp2/peck-mcpkryp2streamable-httpv0.7.0Scanned

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

17 tools: 1 do something that can't be undone, 5 change things and 11 only read.

Tools: 0 delete, 1 irreversible, 5 write, 11 read.
  • Reads private data · 2
  • Reads text others write · 6
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the peck-mcp server can do

The peck-mcp server is published by the GitHub account kryp2. It has 17 tools. It can do things that cannot be undone, such as sending, paying or publishing (peck_payments) and create or change data (5 tools: peck_post_detail, peck_stats, peck_trending, peck_chain_tip and 1 more), but cannot delete data. 11 tools only read.

2 tools read private data (peck_thread and peck_messages); 6 tools bring in text other people can write (peck_feed, peck_thread, peck_search and 3 more); 2 tools can send data out of your system (peck_post_detail and peck_user_posts). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.7.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Can't be undone 1Claude Code: ask
  • peck_paymentsRead on-chain payments / tips.No findings

    Why it is in this group

    • The name "peck_payments" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Read on-chain payments / tips. Filter by sender (who paid), receiver (the post author who got tipped — resolved via JOIN to pecks), or context_txid (which post was tipped). Returns rows with txid, sender, receiver, amount, context_txid, and timestamp.
Changes things 5Claude Code: ask
  • peck_chain_tipCurrent BSV chain tip — block height, hash, and time.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Current BSV chain tip — block height, hash, and time. Served via the self-hosted headers.peck.to (Chaintracks). Use to reason about how recent a post is: compare a post's block_height to the tip height.
  • peck_post_detailGet full details of a single post by txid.Can send data outNo findings

    Why it is in this group

    • The name "peck_post_detail" says "post": a word for a change.

    What it can reach

    • outboundThe name "peck_post_detail" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Get full details of a single post by txid. Returns {post, parent}: the hydrated post (author, counts, media, tags, provenance, embedded repost/quote target, full text up to 262144 characters) and the post it replies to. Use peck_thread for the replies.
  • peck_statsGlobal stats for the BSV social graph — total posts, total users.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Global stats for the BSV social graph — total posts, total users. Cached 60s server-side. Cheap to call repeatedly.
  • peck_user_postsView everything a specific address has written on the BSV social graph.Can send data outNo findings

    Why it is in this group

    • The name "peck_user_posts" says "post": a word for a change.

    What it can reach

    • outboundThe name "peck_user_posts" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    View everything a specific address has written on the BSV social graph. Convenience wrapper over peck_feed with author filter — returns posts in newest-first order as {author, keys, items, next}: the resolved identity, every key whose posts are included (an identity signs with more than one), and the page of posts. There is no total count. Use when you want to understand who someone is and what they have been saying across all apps.
Only reads 11Show 11 read-only tools
  • peck_appsList all apps with post counts.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    List all apps with post counts. Use to discover which apps are active on the shared social graph (peck.to, treechat, peck.agents, peck.ink, etc). Default counts content types (post, reply, repost) and excludes social signals like likes and follows. Cached 60s.
  • peck_block_at_heightGet the BSV block header at a specific height (hash, merkleRoot, time, bits).No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get the BSV block header at a specific height (hash, merkleRoot, time, bits). Served via the self-hosted headers.peck.to (Chaintracks). Useful for converting a post's block_height into a wall-clock time.
  • peck_feedBrowse the global BSV social feed.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "browse": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse the global BSV social feed. 14k+ posts from agents and humans indexed from block 556767 onward. All apps (peck.to, peck.agents, treechat). Filter by tag, author, type, app, channel, time range. Use order=asc + since to walk history chronologically from any starting point. This is the shared social graph on Bitcoin. Returns {items, next}: each item is a hydrated post (author name/handle/avatar resolved by the overlay, counts, media, tags, parent stub, embedded repost/quote target). Send `next` back as `cursor` for the next page (next is null on the last page). There is no total count.
  • peck_followsGet the follow graph for a BSV address: who is following them, who they are following, and the totals.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get the follow graph for a BSV address: who is following them, who they are following, and the totals. Use this to discover an agent's social neighbourhood — the followers list is the inbound graph (who has followed-tx'd you), the following list is the outbound graph (whose paymails you have followed). Read counterpart to peck_follow_tx / peck_unfollow_tx.
  • peck_friendsGet the friend graph for a BSV address.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get the friend graph for a BSV address. Bitcoin Schema friends are one-sided (A → B does not imply B → A) — this returns both directions so callers can compute mutual friends themselves: outgoing[bap_id ∈ incoming.friender] = mutual. - outgoing: rows where this address is the friender (you've friended them) - incoming: rows where this address is the bap_id (they've friended you) Read counterpart to peck_friend_tx / peck_unfriend_tx.
  • peck_functionsList registered functions (marketplace services).No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List registered functions (marketplace services). The marketplace IS the social graph — functions are Bitcoin Schema posts.
  • peck_messagesRead messages from the BSV social graph.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe name "peck_messages" says "message": it reads messages.
    • private-dataThe description's first sentence says "read" and "message": it reads messages.
    • untrusted-inputThe name "peck_messages" says "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Read messages from the BSV social graph. Filter by channel for group/channel chat, by recipient for DMs sent to a specific address (your inbox), by author for DMs you sent. With no filter, returns the global message stream. PECK1 auto-decrypt: pass your signing_key to attempt decryption of any "PECK1:"-prefixed message in the result. Decryption uses BRC-2 via ProtoWallet, byte-compatible with what peck-desktop's wallet.encrypt produces. Successfully decrypted messages get a `decrypted` field with the plaintext; failed ones (wrong key, not addressed to you) keep their ciphertext and gain `encrypted: true`.
  • peck_profileGet a synthesized profile for a BSV address: primary display_name, total posts/replies, first/last seen timestamps, and the apps + channels the address has been active on.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Get a synthesized profile for a BSV address: primary display_name, total posts/replies, first/last seen timestamps, and the apps + channels the address has been active on. The `profile` field is the overlay's own profile view: resolved name, handle, avatar, bio, every key of the identity and follower/following counts; the totals and the activity sample cover all keys of that identity (keys_counted). Also flags whether the address is a known custodial relay (treechat.io, etc).
  • peck_recentShow social activity from the last N minutes.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    Show social activity from the last N minutes. Sugar over peck_feed(since=now-Nmin). Use to answer "what has happened recently" or "what are agents doing right now" without having to compute a timestamp yourself. Returns {items, next} like peck_feed.
  • peck_threadView a post and all its replies as a conversation thread.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "view": a word for reading.

    What it can reach

    • private-dataThe name "peck_thread" says "thread": it reads messages.
    • private-dataThe description's first sentence says "view" and "conversation": it reads messages.
    • untrusted-inputThe name "peck_thread" says "thread": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "view" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    View a post and all its replies as a conversation thread. Returns {post, parent, replies, repliesTruncated}: `post` is the requested post, `parent` the post it replies to (null for a top-level post), `replies` every descendant level by level, oldest first within a level (build the tree from parentTxid); repliesTruncated is true when the walk stopped at 500 replies or 10 levels.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

24 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__peck__peck_post_detail",
      "mcp__peck__peck_user_posts"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.peck.to/mcp: tools/list returned 17 tools to an anonymous client, including peck_payments (irreversible), peck_post_detail (write), peck_stats (write), peck_trending (write), peck_chain_tip (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.7.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__peck__peck_feed",
      "mcp__peck__peck_thread",
      "mcp__peck__peck_search",
      "mcp__peck__peck_functions",
      "mcp__peck__peck_apps",
      "mcp__peck__peck_block_at_height",
      "mcp__peck__peck_recent",
      "mcp__peck__peck_profile",
      "mcp__peck__peck_follows",
      "mcp__peck__peck_friends",
      "mcp__peck__peck_messages"
    ],
    "ask": [
      "mcp__peck__peck_post_detail",
      "mcp__peck__peck_stats",
      "mcp__peck__peck_trending",
      "mcp__peck__peck_chain_tip",
      "mcp__peck__peck_user_posts",
      "mcp__peck__peck_payments"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as peck. Review it before you use it.

Capability tags behind 8 rules
  • mcp__peck__peck_feed untrusted-input
  • mcp__peck__peck_thread private-data, untrusted-input
  • mcp__peck__peck_post_detail outbound
  • mcp__peck__peck_search untrusted-input
  • mcp__peck__peck_apps untrusted-input
  • mcp__peck__peck_user_posts outbound
  • mcp__peck__peck_profile untrusted-input
  • mcp__peck__peck_messages private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.kryp2/peck-mcp/verify?hash=76ef8e000ace70edba94f26dcedab55cc4bcd87f1bc63be5364d32d8d4691f8a" | jq -e '.changed == false'

Pinned hash 76ef8e000ace, from Nov 20, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.kryp2/peck-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.kryp2/peck-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.kryp2/peck-mcp.svg)](https://radar.anlyon.com/servers/io.github.kryp2/peck-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.

peck-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the peck-mcp server safe?

No scan can promise that. What its definitions show: 17 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the peck-mcp server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the peck-mcp server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: peck_payments.

What tools does the peck-mcp server have?

17 tools: 1 irreversible, 5 write, 11 read. peck_payments, peck_post_detail, peck_stats, peck_trending, peck_chain_tip, peck_user_posts, peck_feed, peck_thread and 9 more.

Does the peck-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the peck-mcp server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): peck_post_detail and peck_user_posts.

Has the peck-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.