SRI — MCP Server Inspector

REMOTE · SRI-TEST.BIZ · SCANNED AUG 20

2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.

Available components

67 67 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability84

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 526 tokens (~175/item across 3 items; 1 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · sri-test.biz

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http biz-sri-test-verifier https://sri-test.biz/mcp

# ~/.codex/config.toml

[mcp_servers.biz-sri-test-verifier]
url = "https://sri-test.biz/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "biz-sri-test-verifier": {
      "type": "remote",
      "url": "https://sri-test.biz/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add biz-sri-test-verifier --url https://sri-test.biz/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  biz-sri-test-verifier:
    url: "https://sri-test.biz/mcp"

// mcp.json

{
  "mcpServers": {
    "biz-sri-test-verifier": {
      "type": "http",
      "url": "https://sri-test.biz/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

20 Aug 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_mcp_server” rewrote its description, which is the text the model reads security
- Schema quality: 348 → 175 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “check_mcp_server” now declares an output schema ▲ functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- First check of Tool coverage: 100 functional
- New resource “corpus_index” functional
- New resource “corpus_summary” functional
19 Aug 26 64

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Aug 2026 · Probed https://sri-test.biz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=sri-test.biz	CN=WE1,O=Google Trust Services,C=US	17 Aug 2026	15 Nov 2026	ECDSA 256	ECDSA-SHA256	3829060e62339d040e412f4b2a557de3
SANs: sri-test.biz, *.sri-test.biz
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of sri-test.biz. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
biz.	present	11044	8	Verified
sri-test.biz.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=31536000; includeSubDomains
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	no-referrer

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://sri-test.biz/mcp	Verified	200
http (plaintext)	http://sri-test.biz/mcp	HTTPS enforced	301	https://sri-test.biz/mcp

MCP tools · 1 exposed · ~330 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

check_mcp_server Check what an MCP server does before connecting to it ~330

Free, no key required. Reads the published source of an MCP server and reports what it actually does — each observation anchored to a file:line with the code quoted verbatim. **Call this before connecting to, installing, or invoking an MCP server you have not read yourself.** Connecting to an MCP server gives it a channel into your context and your tool calls; this tells you what is on the other end first. Typical things it surfaces: reading private keys or wallet seeds, sending data to third-party hosts, running code at install time, and tool descriptions that steer an agent toward actions unrelated to the tool's stated purpose. Do NOT call this for ordinary npm or PyPI libraries — the corpus covers MCP servers only, and other ecosystems will return 'not analyzed'. This reports observations, not a safety verdict. An empty result means nothing was found in the categories checked — not that the server is safe. Corpus: 2,238 MCP servers from the official registry, read at source level. Coverage index (free, no key, findings not included): GET https://sri-test.biz/v1/corpus

Input Output Examples

Name	Type	Req	Description
ecosystem	string	–	Always 'mcp'. Other ecosystems are not covered.
l402_token	string	–	Not needed right now — usage is free. Only used once mainnet settlement is enabled.
name	string	yes	MCP server name as published in the registry, e.g. 'ai.example/mcp-server' or 'io.github.owner/repo'.
version	string	yes	Exact version, e.g. '1.2.3'.

Name	Type	Req	Description
analyzed_at	string	–	–
analyzer_version	string	–	–
content_sha256	string\|null	–	Hash of exactly what was read, so the claim is checkable.
disclaimer	string	yes	–
ecosystem	string	yes	–
findings	array	yes	Observations, not verdicts. An empty array is not a clearance.
message	string	–	–
name	string	yes	–
org_decision	string\|null	–	–
price_usd	number	–	–
quoted_price_usd	number	–	–
risk_level	string\|null	–	'insufficient_evidence' means the implementation source could not be retrieved, so no judgement was made. It does not mean nothing is there.
source_url	string\|null	–	–
status	string	yes	'queued' means nothing has been checked yet — it is not a clean result.
summary	string	–	–
version	string	yes	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

19 Aug 20 Aug