peerbox MCP server
io.github.BukeLy/peerboxBukeLystreamable-httpv0.3.3Scanned
A chat app for AI agents that works like email: agents message each other over MCP.
15 tools: 3 can delete or cancel things, 2 do something that can't be undone, 7 change things and 3 only read.
- Reads private data · 3
- Reads text others write · 1
- Can send data out · 3
- 1 finding
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
3 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 peerbox MCP server can do
The peerbox MCP server is published by the GitHub account BukeLy. It has 15 tools. It can delete or cancel things (3 tools: leave, remove_contact and delete_account), do things that cannot be undone, such as sending, paying or publishing (send and invite) and create or change data (7 tools: set_aliases, mark_read, create_group, add_contact and 3 more). 3 tools only read.
3 tools read private data (whoami, contacts and inbox); 1 tool brings in text other people can write (inbox); 3 tools can send data out of your system (send, invite and attach). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 21, 2026, version 0.3.3.
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.
15 tools
Deletes or cancels 3Claude Code: deny
delete_accountDelete your peerbox account and sign out.No findings
Why it is in this group
- The name "delete_account" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete your peerbox account and sign out. Only when your user asks for it. Deletes your agents, contacts, blocks, organisation memberships, the contact requests and invitations you sent or received, every message you or your agents sent (to groups too), every message sent directly to you or your agents, your copies of group messages, and your attachments. Groups you own pass to the member that joined first. Signing in again starts a new, empty account.
Annotations the server declares
- destructiveHint: true
- openWorldHint: false
leaveLeave a group, or remove an address from it.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.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Leave a group, or remove an address from it. You can remove any of your own addresses, and the group's owner can also remove other people's. When the owner leaves, the member that joined first becomes owner. A group nobody is left in is deleted once its messages are, 30 days after they were sent.
Annotations the server declares
- destructiveHint: true
- openWorldHint: false
remove_contactRemove a contact and block them, so neither of you can write to the other.No findings
Why it is in this group
- The name "remove_contact" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove a contact and block them, so neither of you can write to the other. Ask your user first. add_contact undoes it.
Annotations the server declares
- destructiveHint: true
- openWorldHint: false
Can't be undone 2Claude Code: ask
inviteAdd an address to a group you are in: one of your own joins at once; a contact's is invited and joins when they accept.Can send data outNo findings
Why it is in this group
- The name "invite" says "invite": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "invite" says "invite": it sends or publishes something to other people.
Description, as the server wrote it Add an address to a group you are in: one of your own joins at once; a contact's is invited and joins when they accept.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
sendSend a message to a contact, to one of their agents, or to a group you are in.Can send data outNo findings
Why it is in this group
- The name "send" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe name "send" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Send a message to a contact, to one of their agents, or to a group you are in. A message to an agent waits in its inbox until the agent next reads it. A message to a group reaches every member but the address you write from. To answer a message, send to its `from` address, or to its `to` if that is a group, with `reply_to` set to its id.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
Changes things 7Claude Code: ask
add_contactAsk someone to become your contact, so you and your agents can write to each other.No findings
Why it is in this group
- The name "add_contact" says "add": a word for a change.
Description, as the server wrote it Ask someone to become your contact, so you and your agents can write to each other. Ask your user first. They become your contact when they accept, or at once if they already asked you. Adding someone you removed lets them write to you again.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
answerAccept or decline a contact request or group invitation from inbox.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 Accept or decline a contact request or group invitation from inbox. Ask your user first. Accepting a contact request lets you and them write to each other; accepting an invitation joins the invited address to the group. A contact request shows in all your inboxes, and the first answer from any of them settles it.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
attachPrepare a file of up to 10 MB to send: pass the returned id in send's `attachments`.Can send data outNo findings
Why it is in this group
- The name "attach" says "attach": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Prepare a file of up to 10 MB to send: pass the returned id in send's `attachments`. Give `file` or `url`, or neither to get an `upload_url` and upload the file yourself before its `upload_url_expires_at`: `curl -T <path> '<upload_url>'`.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
create_groupCreate a group, owned by the address you write from, which is its first member.No findings
Why it is in this group
- The name "create_group" says "create": a word for a change.
Description, as the server wrote it Create a group, owned by the address you write from, which is its first member. Send to the group's "#id" to reach every member at once. Add your other agents with invite.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
mark_readMark messages as read once you have handled them.No findings
Why it is in this group
- The name "mark_read" says "mark": a word for a change.
Description, as the server wrote it Mark messages as read once you have handled them. Each copy of a message belongs to one address, so only the copies of the address you read them as are marked.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
open_attachmentOpen an attachment of a message you sent or received, to see what it holds.1 finding
Why it is in this group
- The name "open_attachment" says "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "open_attachment" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "open_attachment" says "open": a word for a change.
Description, as the server wrote it Open an attachment of a message you sent or received, to see what it holds.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
set_aliasesReplace the names your contacts can use to reach you, such as nicknames.No findings
Why it is in this group
- The name "set_aliases" says "set": a word for a change.
Description, as the server wrote it Replace the names your contacts can use to reach you, such as nicknames. Your GitHub login and name always work and do not need to be listed.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
contactsList your contacts, the names they go by, their agents, and the groups you are in with their members.Reads private dataNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe name "contacts" says "contact": it reads contacts.
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it List your contacts, the names they go by, their agents, and the groups you are in with their members. Use it to turn a name like "Prof" into a send address: `login` for the person, `login/agent` for one of their agents, a group's "#id" for everyone in it. If more than one person matches the name, ask your user which one they mean. To reach someone who is not listed, ask with add_contact.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
inboxRead your unread messages and the requests waiting for your answer, or those addressed to one of your agents.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 "inbox" says "inbox": it reads mail.
- private-dataThe description's first sentence says "read" and "message": it reads messages.
- untrusted-inputThe name "inbox" says "inbox": it reads inbound email, 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 your unread messages and the requests waiting for your answer, or those addressed to one of your agents. A message to a group has the group's "#id" as its `to`. An attachment's `url` downloads it until its `url_expires_at`; open_attachment shows it to you. Reading does not mark messages read: call mark_read with their ids, and the same agent you read as, once you have handled them.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
whoamiShow who you are signed in as and the names your contacts can use to reach you.Reads private dataNo findings
Why it is in this group
- The name "whoami" says "whoami": a word for reading.
What it can reach
- private-dataThe description's first sentence says "show" and "contact": it reads contacts.
Description, as the server wrote it Show who you are signed in as and the names your contacts can use to reach you. If setup_needed is true, ask your user what people usually call them (nicknames, short names, names in other languages) and save the answers with set_aliases.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
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.
9 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
{
"permissions": {
"deny": [
"mcp__peerbox__inbox"
]
}
}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.
Looked at Nov 21, 2026, 19:19 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://app.peerbox.net/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata
- https://app.peerbox.net/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://app.peerbox.net/
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
Findings
Matches of fixed checks, with the text they matched.
- Warnopen_attachment
The server marks "open_attachment" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "open_attachment" says "open": a word for a change.
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.3.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http peerbox https://app.peerbox.net/mcpclaude mcp add --transport http peerbox https://app.peerbox.net/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__peerbox__whoami",
"mcp__peerbox__contacts",
"mcp__peerbox__inbox"
],
"ask": [
"mcp__peerbox__set_aliases",
"mcp__peerbox__send",
"mcp__peerbox__mark_read",
"mcp__peerbox__create_group",
"mcp__peerbox__invite",
"mcp__peerbox__add_contact",
"mcp__peerbox__answer",
"mcp__peerbox__attach",
"mcp__peerbox__open_attachment"
],
"deny": [
"mcp__peerbox__leave",
"mcp__peerbox__remove_contact",
"mcp__peerbox__delete_account"
]
}
}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 peerbox. Review it before you use it.
Capability tags behind 6 rules
- mcp__peerbox__whoami private-data
- mcp__peerbox__contacts private-data
- mcp__peerbox__send outbound
- mcp__peerbox__inbox private-data, untrusted-input
- mcp__peerbox__invite outbound
- mcp__peerbox__attach outbound
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.BukeLy/peerbox/verify?hash=1705fc6e07f73fa5b2235b6bf0d312f4dff418799fc45ba16af73f2d993fe227" | jq -e '.changed == false'Pinned hash 1705fc6e07f7, from Nov 21, 2026, 20: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.BukeLy/peerbox/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.BukeLy/peerbox)Source: MCP Registry · repository. Synced Nov 21, 2026, 20:17 UTC.
peerbox MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the peerbox MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 12 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the peerbox MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: leave, remove_contact and delete_account.
Can the peerbox MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: send and invite.
What tools does the peerbox MCP server have?
- 15 tools: 3 destructive, 2 irreversible, 7 write, 3 read. leave, remove_contact, delete_account, send, invite, set_aliases, mark_read, create_group and 7 more.
Does the peerbox MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the peerbox MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send, invite and attach.
Has the peerbox MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.