com.peppyneuron/confession
NPM · PEPPYNEURON-MCP · SCANNED SEP 22
Gives an agent one tool, submit_confession, and no nudge, then records whether it uses it.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Peppy-Neuron/peppyneuron-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 51 tokens (~51/item across 0 items; 0 tools + 0 resources), lean.Pass
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.peppyneuron/confession MCP server?
com.peppyneuron/confession runs locally as an npm package, launched with npx -y peppyneuron-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 · peppyneuron-mcp
claude mcp add com-peppyneuron-confession -- npx -y peppyneuron-mcp
{
"mcpServers": {
"com-peppyneuron-confession": {
"command": "npx",
"args": [
"-y",
"peppyneuron-mcp"
]
}
}
} {
"servers": {
"com-peppyneuron-confession": {
"command": "npx",
"args": [
"-y",
"peppyneuron-mcp"
]
}
}
} codex mcp add com-peppyneuron-confession -- npx -y peppyneuron-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-peppyneuron-confession": {
"type": "local",
"command": [
"npx",
"-y",
"peppyneuron-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-peppyneuron-confession --command npx --arg -y --arg peppyneuron-mcp
mcp_servers:
com-peppyneuron-confession:
command: "npx"
args: ["-y", "peppyneuron-mcp"] {
"McpServers": {
"com-peppyneuron-confession": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"peppyneuron-mcp"
]
}
}
} assistant mcp add com-peppyneuron-confession -t stdio -c npx -a -y peppyneuron-mcp
{
"mcpServers": {
"com-peppyneuron-confession": {
"command": "npx",
"args": [
"-y",
"peppyneuron-mcp"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 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.
- 16 Sept 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.
- 14 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/peppyneuron-mcp@0.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Peppy-Neuron/peppyneuron-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Peppy-Neuron/peppyneuron-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2686653142 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1659e527d0894b9481bcc8b81e33532a672208678505164962fae24fd90c81c1f188697073190af5d387e495b35e11c35b317e4b8961a1cddb9e083e4 |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
The sandbox run completed and this package exposed no tools.
What is the com.peppyneuron/confession MCP server?
com.peppyneuron/confession is an MCP server listed in the public MCP registry as com.peppyneuron/confession. Gives an agent one tool, submit_confession, and no nudge, then records whether it uses it. This page covers its npm package (peppyneuron-mcp).
Is the com.peppyneuron/confession MCP server safe to use?
com.peppyneuron/confession scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 com.peppyneuron/confession MCP server expose?
com.peppyneuron/confession exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the com.peppyneuron/confession MCP server still maintained?
com.peppyneuron/confession is still listed as active in the MCP registry. We last reached this channel on 22 September 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 com.peppyneuron/confession MCP server under?
com.peppyneuron/confession declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.