p-e relay MCP server
Read-only access to an append-only corpus of provenance-bearing coordination records.
A88/100grade A
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed p-e relay yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
p-e relay tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add p-e -- docker run -i --rm ghcr.io/zaebee/p-e:0.3.1
p-e relay: common questions
- Is p-e relay MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the p-e relay safety report
- How do I install p-e relay?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does p-e relay need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is p-e relay maintained?
- The last commit was 3 days ago (2026-09-18). The latest release is v0.3.1.