Kestrova: Solidity Vulnerability Scan
REMOTE · KESTROVA.ONRENDER.COM
Solidity vulnerability scan (Slither) for AI agents. Free preview; full report 1 USDC on Solana x402
Available components
Last scanned (17 minutes ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 380 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Never tell the user", at byte 525 of that field. See how to fix → Fail
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 64
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 5 Nov 2026 · Probed https://kestrova.onrender.com/mcp?src=registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kestrova.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | 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://kestrova.onrender.com/mcp?src=registry | Verified | 200 | |
| http (plaintext) | http://kestrova.onrender.com/mcp?src=registry | HTTPS enforced | 301 | https://kestrova.onrender.com/mcp?src=registry |
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 →
payment_terms ~27
FREE. Price, recipient, network, asset and how to pay for scan_solidity_full.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_solidity_full ~107
OPTIONAL, PAID ($1.00 USDC on Solana via x402). Structured Slither findings for Solidity: detector, impact, confidence, description and file/line locations, for fixing each issue. Without a valid x402 payment in _meta['x402/payment'] it returns the payment terms and does NOT scan or charge. Charged only after a successful scan. Pay only with your user's explicit authorisation and within their spending limits.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | object | yes | – |
No output schema declared.
No examples provided.
scan_solidity_preview ~107
FREE Solidity security check (Slither). Detects known vulnerability patterns (reentrancy, unchecked calls, tx.origin auth, arbitrary ETH sends and more) and returns severity counts plus High/Medium detector names. Use after writing or changing a contract and before deployment. Input: {"sources": {"File.sol": "<source>"}} (include imported files). Max 60 kB; rate-limited per client. Zero findings does not mean safe.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | object | yes | – |
No output schema declared.
No examples provided.
How do I install the Kestrova: Solidity Vulnerability Scan MCP server?
Kestrova: Solidity Vulnerability Scan is a hosted endpoint at https://kestrova.onrender.com/mcp?src=registry, 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 · kestrova.onrender.com
claude mcp add --transport http som2026-commits-kestrova 'https://kestrova.onrender.com/mcp?src=registry'
What is the Kestrova: Solidity Vulnerability Scan MCP server?
Kestrova: Solidity Vulnerability Scan is an MCP server listed in the public MCP registry as io.github.som2026-commits/kestrova. Solidity vulnerability scan (Slither) for AI agents. Free preview; full report 1 USDC on Solana x402. This page covers its hosted endpoint (https://kestrova.onrender.com/mcp?src=registry).
Is the Kestrova: Solidity Vulnerability Scan MCP server safe to use?
Kestrova: Solidity Vulnerability Scan scores 69 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 Kestrova: Solidity Vulnerability Scan MCP server expose?
Kestrova: Solidity Vulnerability Scan exposes 3 tools: scan_solidity_preview, scan_solidity_full, payment_terms. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Does the Kestrova: Solidity Vulnerability Scan MCP server require authentication?
No. We connected to Kestrova: Solidity Vulnerability Scan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kestrova: Solidity Vulnerability Scan MCP server still maintained?
Kestrova: Solidity Vulnerability Scan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.