MCP server · trust report
dev.workers.cronping-oren.cronping/heartbeat-monitor
2 checks that ran failed — credential hygiene and transport config — so this release can’t be trusted as-is.
- Publisher
- dev.workers.cronping-oren.cronping
- Repository
- —
- Install
- remote only
- Versions
- 4
- MCP revision
- 2024-11-05 · superseded
- Inspected
- 5 of 6 checks · 85%
- Scored
- 2026-09-03 · 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).
tool "delete_heartbeat" description: cross-tool redirection ('instead of call…').
Supply chain
warn25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
no resolvable repository linked to the package (provenance unverifiable)
Credential hygiene
fail15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
tool "ping_heartbeat" has a secret-shaped input parameter "progress_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_heartbeat_status" has a secret-shaped input parameter "claim_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "set_heartbeat_alert" has a secret-shaped input parameter "claim_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "delete_heartbeat" has a secret-shaped input parameter "claim_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "pause_heartbeat" has a secret-shaped input parameter "claim_token" — secrets must never be tool parameters (the model would supply/handle the credential).
Permission scope
unscannable15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
No source files, package.json, or pyproject were fetched; cannot infer capability scope.
Version behavior
pass10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
tool surface, capabilities, install scripts, and publisher unchanged vs prior version 1.3.0 (minor bump); no rug-pull drift.
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)
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 |
|---|---|---|---|---|---|
| v1.4.0 · current | 2026-08-29 | D | 50 | 5/6 · 85% | ±0 |
| v1.3.0 | 2026-08-21 | D | 45 | 5/6 · 85% | C→D in v1.3.0 |
| v1.2.0 | 2026-08-05 | C | 62.5 | 5/6 · 85% | ±0 |
| v1.1.0 | 2026-07-30 | C | 62.5 | 4/6 · 75% | — |