mcp-registry/io.github.kryp2/peck-mcp · v0.7.0
As of 2026-10-17 23:16 UTC, the Kryp2 Peck MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
BSV wallet, BRC-100 identity and 38 tools to read and write the Bitcoin Schema social graph
Claude Code
claude mcp add --transport http kryp2-peck-mcp-server https://mcp.peck.to/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"kryp2-peck-mcp-server": {
"type": "http",
"url": "https://mcp.peck.to/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
17 of 17 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
Handshake + tools/list takes ~1,809 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
In the last 30 days: 0 tool(s) removed and 5 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.kryp2%2Fpeck-mcp/fixes
{
"name": "peck_payments",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "number",
"description": "Max rows (default 50, max 200)."
},
"sender": {
"type": "string",
"description": "Filter by sender BSV address."
},
"receiver": {
"type": "string",
"description": "Filter by receiver BSV address (the tipped post's author)."
},
"context_txid": {
"type": "string",
"description": "Filter by the post that was tipped."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "peck_post_detail",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"txid"
],
"properties": {
"txid": {
"type": "string",
"description": "Transaction ID."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "peck_search",
"description": "Full-text search across all posts on the BSV social graph. Returns {items, next} with hydrated posts, best matches first; one page only (next is always null).",
"inputSchema": {
"type": "object",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"description": "Search query."
},
"limit": {
"type": "number",
"description": "Max results (default 20, max 100)."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.kryp2/peck-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.kryp2/peck-mcp"}) over MCP.
peck_feed ~488 tokenspeck_user_posts ~339 tokenspeck_messages ~296 tokenspeck_recent ~242 tokenspeck_profile ~194 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.kryp2%2Fpeck-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.kryp2%2Fpeck-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kryp2%2Fpeck-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kryp2%2Fpeck-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.kryp2%2Fpeck-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8f2a0ffa05f40549…, first seen 2026-10-17, included at leaf 1259 of 19,070. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable finance servers · most reliable data servers · most reliable communication servers · most reliable code servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 23:16 UTC, the Kryp2 Peck MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
Kryp2 Peck MCP server advertises 39 tools, including peck_apps, peck_balance, peck_block_at_height, peck_chain_tip, peck_feed.
Point your MCP client at this streamable-http endpoint: https://mcp.peck.to/mcp
Glimind scanned all 17 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.