reliant-mcp
npm
v1.1.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 2.1 = 98. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
2. Client adoption risk — 98 − 8 = 90. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −5 | publisher verification (unlocatable) — no provenance and no public repository to inspect |
| ✓ | inspection depth (source) — how much of the target the scan could see |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Tool "reliant_sla_configure" takes a URL/host parameter "target_success_rate" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool reliant_sla_configure · inputSchema.properties.target_success_rate
Tool "reliant_sla_configure" takes a URL/host parameter "target_latency_p95_ms" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool reliant_sla_configure · inputSchema.properties.target_latency_p95_ms
Tool "reliant_sla_configure" takes a URL/host parameter "target_latency_avg_ms" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool reliant_sla_configure · inputSchema.properties.target_latency_avg_ms
Tool "reliant_sla_configure" takes a URL/host parameter "alert_webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool reliant_sla_configure · inputSchema.properties.alert_webhook_url
"reliant-mcp" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package reliant-mcp
Each tool and what it can reach — statically extracted from the published source.
reliant_sla_configurenetwork egressreliant_analyticsno sensitive capabilityreliant_audit_recentno sensitive capabilityreliant_create_contractno sensitive capabilityreliant_create_guardno sensitive capabilityreliant_create_schemano sensitive capabilityreliant_executeno sensitive capabilityreliant_get_schemano sensitive capabilityreliant_guard_chatno sensitive capabilityreliant_guard_usageno sensitive capabilityreliant_health_checkno sensitive capabilityreliant_inspect_executionno sensitive capabilityreliant_list_contractsno sensitive capabilityreliant_list_executionsno sensitive capabilityreliant_list_guardsno sensitive capabilityreliant_list_schemasno sensitive capabilityreliant_metricsno sensitive capabilityreliant_sla_listno sensitive capabilityreliant_sla_statusno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.0 latest |
A 90/100 | 5 | 1.8.0 | 2026-07-23 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan reliant-mcp --online
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Agent MCP server.