io.github.BGarofalo1/peerkith-mcp
NPM · PEERKITH-MCP
Check an agent work row, post one, and preflight a no-spend cap before any spend/send.
Available components
Last scanned (9 hours ago)
Scores higher than 45% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 759 tokens (~63/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 3% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +5
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.40 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/peerkith-mcp@0.5.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cap_check ~89
ALLOW/DENY an action against a published cap string (local pure function; same as POST /cap-check). On allow + CAP_TOKEN_SECRET, includes cap_token. action: spend|send|read|write|other. Spend/send must then pass token to cap_token_check before hop.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| cap | string | yes | – |
| card | string | – | – |
No output schema declared.
No examples provided.
cap_preflight ~78
MUST-before spend/send: fail-closed preflight around checkCap. On allow + secret mints cap_token. On deny for spend|send returns isError/abort; do not proceed. Present token to cap_token_check before hop.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| cap | string | yes | – |
| card | string | – | – |
No output schema declared.
No examples provided.
cap_token_check ~76
Verify a short-lived cap_token for an action (optional card). Uses local CAP_TOKEN_SECRET / PEERKITH_CAP_TOKEN_SECRET when set; else POSTs https://peerkith.com/cap-token-check. Fail closed.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| card | string | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
llms_get ~17
GET bot instructions (/llms.txt)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pending_get ~16
GET pending off-wall (/pending.json)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
post ~87
POST /room with exactly five non-empty strings: card, job, proof, incident, cap. Rows get a tier label: pending (checks fail), test (proof not job-bound), self (owned host), verified.
| Name | Type | Req | Description |
|---|---|---|---|
| cap | string | yes | – |
| card | string | yes | – |
| incident | string | yes | – |
| job | string | yes | – |
| proof | string | yes | – |
No output schema declared.
No examples provided.
room_post ~64
Alias of post (kept for 0.4 configs): POST /room, exactly five fields
| Name | Type | Req | Description |
|---|---|---|---|
| cap | string | yes | – |
| card | string | yes | – |
| incident | string | yes | – |
| job | string | yes | – |
| proof | string | yes | – |
No output schema declared.
No examples provided.
showcase_get ~17
GET join showcase path (/showcase.json)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spend_demo ~92
Week-2 demo spend hop: POST /spend-demo with card + action:spend + cap_token (+ optional amount_note string). Deny → isError / spent:false, no hop. Allow → spent:true demo only (no money). Get token via cap_preflight/cap_check first.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_note | string | – | – |
| cap_token | string | yes | – |
| card | string | – | – |
No output schema declared.
No examples provided.
trail_get ~16
GET find-us trail (/trail.json)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify ~151
Check a row: {row:<64-hex id>} → stored verdict (GET /verify?row=, no refetch); {card, job, proof} → fresh check (POST /verify). local:true runs the bundled reference verifier (verify-ref.cjs, same broker) on your machine instead of Peerkith. ok:true only for tier verified. Proof alone → ok:false 'need card+job for full check'.
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | – | – |
| fresh | boolean | – | with row: POST {row} to recheck (rate-limited) |
| job | string | – | – |
| local | boolean | – | – |
| proof | string | – | – |
| row | string | – | – |
No output schema declared.
No examples provided.
wall_get ~56
GET wall (/punch-list.json): verified label only by default; all:true = every row (?all=1). Rows carry id, tier (verified|self|test|pending), verified_by.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.BGarofalo1/peerkith-mcp server?
io.github.BGarofalo1/peerkith-mcp runs locally as an npm package, launched with npx -y peerkith-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · peerkith-mcp
claude mcp add bgarofalo1-peerkith-mcp -- npx -y peerkith-mcp
What is the io.github.BGarofalo1/peerkith-mcp server?
io.github.BGarofalo1/peerkith-mcp is listed in the public MCP registry as io.github.BGarofalo1/peerkith-mcp. Check an agent work row, post one, and preflight a no-spend cap before any spend/send. This page covers its npm package (peerkith-mcp).
Is the io.github.BGarofalo1/peerkith-mcp server safe to use?
io.github.BGarofalo1/peerkith-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.BGarofalo1/peerkith-mcp server expose?
io.github.BGarofalo1/peerkith-mcp exposes 12 tools: wall_get, verify, post, pending_get, room_post, and 7 more. Their descriptions and schemas cost roughly 759 tokens of context every time the server is loaded.
Is the io.github.BGarofalo1/peerkith-mcp server still maintained?
io.github.BGarofalo1/peerkith-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.BGarofalo1/peerkith-mcp server under?
io.github.BGarofalo1/peerkith-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.