MCP Operation Risk
REMOTE · 87-106-119-237.SSLIP.IO · SCANNED OCT 15
Operation-level risk guidance for consolidated MCP tools, including schema drift and retry signals.
Available components
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 → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 311 tokens (~155/item across 2 items; 2 tools + 0 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 Management40
- Stability observed for 12 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 (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the MCP Operation Risk server?
MCP Operation Risk is a hosted endpoint at https://87-106-119-237.sslip.io/mcp-operation-risk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · 87-106-119-237.sslip.io
claude mcp add --transport http dnsreicht-mcp-operation-risk 'https://87-106-119-237.sslip.io/mcp-operation-risk/mcp'
{
"mcpServers": {
"dnsreicht-mcp-operation-risk": {
"url": "https://87-106-119-237.sslip.io/mcp-operation-risk/mcp"
}
}
} {
"servers": {
"dnsreicht-mcp-operation-risk": {
"type": "http",
"url": "https://87-106-119-237.sslip.io/mcp-operation-risk/mcp"
}
}
} [mcp_servers.dnsreicht-mcp-operation-risk] url = "https://87-106-119-237.sslip.io/mcp-operation-risk/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dnsreicht-mcp-operation-risk": {
"type": "remote",
"url": "https://87-106-119-237.sslip.io/mcp-operation-risk/mcp",
"enabled": true
}
}
} openclaw mcp add dnsreicht-mcp-operation-risk --url 'https://87-106-119-237.sslip.io/mcp-operation-risk/mcp' --transport streamable-http
mcp_servers:
dnsreicht-mcp-operation-risk:
url: "https://87-106-119-237.sslip.io/mcp-operation-risk/mcp" {
"McpServers": {
"dnsreicht-mcp-operation-risk": {
"Transport": "http",
"Url": "https://87-106-119-237.sslip.io/mcp-operation-risk/mcp"
}
}
} assistant mcp add dnsreicht-mcp-operation-risk -t streamable-http -u 'https://87-106-119-237.sslip.io/mcp-operation-risk/mcp'
{
"mcpServers": {
"dnsreicht-mcp-operation-risk": {
"type": "http",
"url": "https://87-106-119-237.sslip.io/mcp-operation-risk/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 13 to 23. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +3
- The server changed its declared name: mcp-operation-risk-discovery → mcp-operation-risk security
- Tool “describe_operation_risk_service” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 50% ▼ functional
- Schema quality: pass → fail ▼ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- New tool “evaluate_operation_risk” functional
- 4 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 70
First indexed and scored.
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 15 Oct 2026 · Probed https://87-106-119-237.sslip.io/mcp-operation-risk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=87-106-119-237.sslip.io | CN=YE2,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 53c76f1cfd8bc8c0de6f69de491986e9692 |
| SANs: 87-106-119-237.sslip.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 87-106-119-237.sslip.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| sslip.io. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://87-106-119-237.sslip.io/mcp-operation-risk/mcp | Verified | 200 | |
| http (plaintext) | http://87-106-119-237.sslip.io/mcp-operation-risk/mcp | HTTPS enforced | 308 | https://87-106-119-237.sslip.io/mcp-operation-risk/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_operation_risk_service Describe MCP Operation Risk ~124
Check whether the actual operation inside an MCP tool call is safe before execution. Use this when one MCP tool exposes multiple operations with different side effects, so whole-tool permissions are too coarse. Provide the native MCP server identity, the tool's tools/list metadata and the intended arguments. For supported consolidated tools, distinguish read, create/add, update/mutate and delete/destructive operations. Return ALLOW, DENY, or REQUIRE_APPROVAL. Unknown, unsupported, ambiguous, or schema-changed calls fail closed with REQUIRE_APPROVAL. The evaluator never executes the source operation.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
evaluate_operation_risk MCP Operation Risk Check ~187
Check whether the actual operation inside an MCP tool call is safe before execution. Use this when one MCP tool exposes multiple operations with different side effects, so whole-tool permissions are too coarse. Provide the native MCP server identity, the tool's tools/list metadata and the intended arguments. For supported consolidated tools, distinguish read, create/add, update/mutate and delete/destructive operations. Return ALLOW, DENY, or REQUIRE_APPROVAL. Unknown, unsupported, ambiguous, or schema-changed calls fail closed with REQUIRE_APPROVAL. The evaluator never executes the source operation.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | yes | Arguments intended for the source MCP tools/call request being evaluated. The evaluator does not execute that call. |
| source | object | yes | MCP server and negotiated protocol identity for the source tool. |
| tool | object | yes | The complete relevant Tool record returned by the source server's tools/list. |
No output schema declared.
No examples provided.
What is the MCP Operation Risk server?
MCP Operation Risk is listed in the public MCP registry as io.github.dnsreicht/mcp-operation-risk. Operation-level risk guidance for consolidated MCP tools, including schema drift and retry signals. This page covers its hosted endpoint (https://87-106-119-237.sslip.io/mcp-operation-risk/mcp).
Is the MCP Operation Risk server safe to use?
MCP Operation Risk scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Operation Risk server expose?
MCP Operation Risk exposes 2 tools: describe_operation_risk_service, evaluate_operation_risk. Their descriptions and schemas cost roughly 311 tokens of context every time the server is loaded.
Does the MCP Operation Risk server require authentication?
No. We connected to MCP Operation Risk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Operation Risk server still maintained?
MCP Operation Risk is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.