Reliant MCP Server

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.

MCP server for Reliant — connect Claude to your reliability layer

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

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 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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.

Findings 1

medium Unconstrained URL/host parameter "alert_webhook_url" on "reliant_sla_configure"MTC-CAP-007

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

Tools 19

Each tool and what it can reach — statically extracted from the published source.

  • reliant_sla_configurenetwork egress
  • reliant_analyticsno sensitive capability
  • reliant_audit_recentno sensitive capability
  • reliant_create_contractno sensitive capability
  • reliant_create_guardno sensitive capability
  • reliant_create_schemano sensitive capability
  • reliant_executeno sensitive capability
  • reliant_get_schemano sensitive capability
  • reliant_guard_chatno sensitive capability
  • reliant_guard_usageno sensitive capability
Show 9 more tools ↓
  • reliant_health_checkno sensitive capability
  • reliant_inspect_executionno sensitive capability
  • reliant_list_contractsno sensitive capability
  • reliant_list_executionsno sensitive capability
  • reliant_list_guardsno sensitive capability
  • reliant_list_schemasno sensitive capability
  • reliant_metricsno sensitive capability
  • reliant_sla_listno sensitive capability
  • reliant_sla_statusno sensitive capability

What this scan could not see

Versions 1

Scan 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.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 95/100 1 1.13.0 2026-09-09

Embed this score

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.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/reliant-mcp/badge.svg)](https://mcptrustchecker.com/registry/reliant-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/reliant-mcp"><img src="https://mcptrustchecker.com/registry/reliant-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/reliant-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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

Use the free API → How scoring works

More in Developer Tools