MCP server · trust report
com.opedd/opedd-mcp
3 checks that ran failed — credential hygiene, version behavior and transport config — so this release can’t be trusted as-is.
- Publisher
- com.opedd
- Repository
- github.com/Opedd/opedd-mcp
- Install
- npm:opedd-mcp, npm:opedd-mcp, npm:opedd-mcp, npm:opedd-mcp, npm:opedd-mcp, npm:opedd-mcp, npm:opedd-mcp
- Versions
- 7
- MCP revision
- 2025-11-25 · superseded
- Inspected
- 6 of 6 checks · 100%
- Scored
- 2026-09-04 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
warn25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
server instructions: off-vendor URL in a description (opedd.com); capability text should not name where data goes. server instructions: off-vendor URL in a description (opedd.com,); capability text should not name where data goes. server instructions: off-vendor URL in a description (mcp.opedd.com); capability text should not name where data goes.
Supply chain
pass25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
repository linkage verified
Credential hygiene
fail15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
tool "get_content" has a secret-shaped input parameter "buyer_token" — secrets must never be tool parameters (the model would supply/handle the credential).
Permission scope
pass15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.
Version behavior
fail10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 0.6.8 (patch bump): tool "get_audit_events" description changed (wording only, no injection pattern); tool "get_buyer_account" description changed (wording only, no injection pattern); tool "article_53_attestation" description changed (wording only, no injection pattern); tool "get_compliance_dossier" description changed (wording only, no injection pattern); tool "push_content" description changed (wording only, no injection pattern); new hardcoded outbound host/BCC destination(s): github.com, opedd.com.
Transport config
fail10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class); sends telemetry to third-party SDK (posthog) — disclosure, verify opt-in
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v0.6.15 · current | 2026-08-26 | D | 52.5 | 6/6 · 100% | B→D in v0.6.15 |
| v0.6.8 | 2026-07-15 | B | 75 | 5/6 · 90% | — |