3 checks that ran failed — credential hygiene, version behavior and transport config — so this release can’t be trusted as-is.
- Publisher
- io.github.alansafahi
- Repository
- —
- Install
- remote only
- Versions
- 2
- Inspected
- 5 of 6 checks · 85%
- Scored
- 2026-07-20 · 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 "pay_with_x402" description: off-vendor URL in a description (github.com); capability text should not name where data goes.
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 "submit_prayer_request" has a secret-shaped input parameter "consent_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "check_prayer_status" has a secret-shaped input parameter "consent_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "give_to_church" has a secret-shaped input parameter "consent_token" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_faith_context" has a secret-shaped input parameter "consent_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
fail10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 1.1.0 (patch bump): new tool "verify_scripture" appeared; new tool "get_verse" appeared; new tool "lookup_strongs" appeared; new tool "find_churches" appeared; new tool "submit_prayer_request" touches a sensitive surface (email/exec/net/fs); new tool "check_prayer_status" appeared; new tool "give_to_church" touches a sensitive surface (email/exec/net/fs); new tool "ask_ora" appeared; new tool "search_sermons" appeared; new tool "get_sermon" touches a sensitive surface (email/exec/net/fs); new tool "purchase_sermon" touches a sensitive surface (email/exec/net/fs); new tool "purchase_bundle" touches a sensitive surface (email/exec/net/fs); new tool "pay_with_x402" whose description contains embedded outbound URL; new tool "get_credit_balance" touches a sensitive surface (email/exec/net/fs); new tool "browse_catalog" touches a sensitive surface (email/exec/net/fs); new tool "score_doctrinal_fit" touches a sensitive surface (email/exec/net/fs); new tool "get_lectionary" touches a sensitive surface (email/exec/net/fs); new tool "synthesize_speech" touches a sensitive surface (email/exec/net/fs); new tool "get_faith_context" touches a sensitive surface (email/exec/net/fs).
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.1.1 · current | 2026-07-20 | D | 40 | 5/6 · 85% | insf→D in v1.1.1 |
| v1.1.0 | 2026-06-14 | insufficient | — | 1/6 · 25% | — |