# Kestrova Solidity Security Scan (remote · kestrova-api.onrender.com)

Free Slither scan of Solidity contracts for AI coding agents; optional paid report (1 USDC, x402).

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `kestrova-api.onrender.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-onrender-kestrova-api-kestrova/kestrova-api.md), [page](https://verifymcp.io/servers/com-onrender-kestrova-api-kestrova/kestrova-api)

## Channel facts

- Endpoint: `https://kestrova-api.onrender.com/mcp?src=registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 758 tokens (~189/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 50/100
  - 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 895 of that field.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Kestrova Solidity Security Scan MCP server?

Kestrova Solidity Security Scan is a hosted endpoint at https://kestrova-api.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.

### Claude

```bash
claude mcp add --transport http com-onrender-kestrova-api-kestrova 'https://kestrova-api.onrender.com/mcp?src=registry'
```

### Cursor

```json
{
  "mcpServers": {
    "com-onrender-kestrova-api-kestrova": {
      "url": "https://kestrova-api.onrender.com/mcp?src=registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-onrender-kestrova-api-kestrova": {
      "type": "http",
      "url": "https://kestrova-api.onrender.com/mcp?src=registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-onrender-kestrova-api-kestrova]
url = "https://kestrova-api.onrender.com/mcp?src=registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-onrender-kestrova-api-kestrova": {
      "type": "remote",
      "url": "https://kestrova-api.onrender.com/mcp?src=registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-onrender-kestrova-api-kestrova --url 'https://kestrova-api.onrender.com/mcp?src=registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-onrender-kestrova-api-kestrova:
    url: "https://kestrova-api.onrender.com/mcp?src=registry"
```

### Netclaw

```json
{
  "McpServers": {
    "com-onrender-kestrova-api-kestrova": {
      "Transport": "http",
      "Url": "https://kestrova-api.onrender.com/mcp?src=registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-onrender-kestrova-api-kestrova -t streamable-http -u 'https://kestrova-api.onrender.com/mcp?src=registry'
```

### Other

```json
{
  "mcpServers": {
    "com-onrender-kestrova-api-kestrova": {
      "type": "http",
      "url": "https://kestrova-api.onrender.com/mcp?src=registry"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, +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.

### 2026-11-20 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 571 → 758
- [functional] New tool “scan_solidity_findings”

### 2026-11-19 (score 66, +1)

- [security regression] Injection markers: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-18 (score 65, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.13 → unverified
- [security regression] Tool safety: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-17 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “payment_terms” rewrote its description, which is the text the model reads
- [security] Tool “scan_solidity_full” rewrote its description, which is the text the model reads
- [security] Tool “scan_solidity_preview” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 163 → 190

### 2026-11-16 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 64, 0)

- [security] Tool “scan_solidity_full” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 148 → 163
- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 64)

First indexed and scored.

## MCP tools (4)

### `scan_solidity_preview` (~174 tokens)

FREE Solidity security check (Slither static analysis), no key and no wallet. Detects known vulnerability patterns (reentrancy, unchecked calls, tx.origin authorisation, arbitrary ETH sends, unprotected functions and more) and returns severity counts, High/Medium detector names and one representative finding (sample_finding; every finding is in scan_solidity_full). Use after writing or changing a contract and before deployment. Input: {"sources": {"File.sol": "<source>"}} (include imported files; package imports such as @openzeppelin/contracts/... stay as written when the package files are submitted under that path, node_modules/ or lib/openzeppelin-contracts/contracts/). Up to 15 KB / 10 files; rate-limited per client. Zero findings does not mean safe.

Input parameters:

- `sources` (object, required)

### `scan_solidity_full` (~159 tokens)

OPTIONAL, PAID ($1.00 USDC via x402 on Base or Solana). Structured Slither findings for Solidity: detector, impact, confidence, description and file/line locations, for fixing each issue. counts and findings cover every finding; each finding's scope is "application" or "dependency" (located only in uploaded lib/<package>/, node_modules/ or @scope/package/ code; original severity kept), with application_counts and dependency_counts. 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.

Input parameters:

- `sources` (object, required)

### `scan_solidity_findings` (~155 tokens)

OPTIONAL, PAID ($0.25 USDC via x402 on Base or Solana). Agent tier: every Slither finding for Solidity with detector, impact, confidence, Slither's description and file/line locations, as JSON; each finding's scope is "application" or "dependency". scan_solidity_full ($1.00 USDC) adds a plain-English explanation and fix for every finding plus PDF and SARIF report files. 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.

Input parameters:

- `sources` (object, required)

### `payment_terms` (~50 tokens)

FREE. Price, recipients, every accepted network (payment_options) and step-by-step x402 payment (how_to_pay) for scan_solidity_full. Read this before paying; no scan, no charge.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-onrender-kestrova-api-kestrova/kestrova-api#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 65
- 2026-11-15: 64
- 2026-11-14: 64
- 2026-11-13: 64

## Common questions

### What is the Kestrova Solidity Security Scan MCP server?

Kestrova Solidity Security Scan is an MCP server listed in the public MCP registry as com.onrender.kestrova-api/kestrova. Free Slither scan of Solidity contracts for AI coding agents; optional paid report (1 USDC, x402). This page covers its hosted endpoint (https://kestrova-api.onrender.com/mcp?src=registry).

### Is the Kestrova Solidity Security Scan MCP server safe to use?

Kestrova Solidity Security Scan scores 67 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 Security Scan MCP server expose?

Kestrova Solidity Security Scan exposes 4 tools: scan_solidity_preview, scan_solidity_full, scan_solidity_findings, payment_terms. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.

### Does the Kestrova Solidity Security Scan MCP server require authentication?

No. We connected to Kestrova Solidity Security Scan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Kestrova Solidity Security Scan MCP server still maintained?

Kestrova Solidity Security Scan is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Kestrova Solidity Security Scan MCP server?

VerifyMCP ran 13 checks on Kestrova Solidity Security Scan, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://kestrova-api.onrender.com/mcp?src=registry
- Website: https://kestrova-api.onrender.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-onrender-kestrova-api-kestrova/kestrova-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-onrender-kestrova-api-kestrova/kestrova-api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-onrender-kestrova-api-kestrova/kestrova-api.json
- HTML version of this page: https://verifymcp.io/servers/com-onrender-kestrova-api-kestrova/kestrova-api
