Skip to content

Kestrova Solidity Security Scan MCP server

com.onrender.kestrova-api/kestrovakestrova-api.onrender.comstreamable-httpv0.5.0Scanned

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

3 tools: 1 do something that can't be undone, 1 change things and 1 only read.

Tools: 0 delete, 1 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Kestrova Solidity Security Scan MCP server can do

The Kestrova Solidity Security Scan MCP server is published by kestrova-api.onrender.com, a domain the MCP Registry verified. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (payment_terms) and create or change data (1 tool: scan_solidity_full), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (scan_solidity_full).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.5.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Can't be undone 1Claude Code: ask
  • payment_termsFREE.1 finding

    Why it is in this group

    • The name "payment_terms" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "payment_terms" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_terms" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    FREE. Price, recipient, network, asset and how to pay for scan_solidity_full.

    Annotations the server declares

    • title: Payment terms
    • readOnlyHint: true
    • openWorldHint: false
Changes things 1Claude Code: ask
  • scan_solidity_fullOPTIONAL, PAID ($1.00 USDC via x402 on Base or Solana).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. 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.

    Annotations the server declares

    • title: Solidity full scan (paid)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • scan_solidity_previewFREE Solidity security check (Slither static analysis), no key and no wallet.No findings

    Why it is in this group

    • The name "scan_solidity_preview" says "preview": a word for reading.
    Description, as the server wrote it
    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 plus High/Medium detector names. Use after writing or changing a contract and before deployment. Input: {"sources": {"File.sol": "<source>"}} (include imported files). Up to 15 KB / 10 files; rate-limited per client. Zero findings does not mean safe.

    Annotations the server declares

    • title: Solidity scan preview (free)
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:21 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://kestrova-api.onrender.com/mcp?src=registry: tools/list returned 4 tools to an anonymous client, including payment_terms (irreversible), scan_solidity_full (write), scan_solidity_findings (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 2 to 3

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "payment_terms" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_terms" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3

Install

Pinned to version 0.5.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__kestrova__scan_solidity_preview"
    ],
    "ask": [
      "mcp__kestrova__scan_solidity_full",
      "mcp__kestrova__payment_terms"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as kestrova. Review it before you use it.

Capability tags behind 1 rule
  • mcp__kestrova__scan_solidity_full untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.onrender.kestrova-api/kestrova/verify?hash=5c3841aa9c5af67f22364d13c974fc0eca235352409176ca8a788eda681c0f70" | jq -e '.changed == false'

Pinned hash 5c3841aa9c5a, from Nov 13, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.onrender.kestrova-api/kestrova/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.onrender.kestrova-api/kestrova
[![Anlyon Radar](https://radar.anlyon.com/badge/com.onrender.kestrova-api/kestrova.svg)](https://radar.anlyon.com/servers/com.onrender.kestrova-api/kestrova)

Source: MCP Registry. Synced Nov 13, 2026, 11:17 UTC.

Kestrova Solidity Security Scan MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Kestrova Solidity Security Scan MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Kestrova Solidity Security Scan MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Kestrova Solidity Security Scan MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: payment_terms.

What tools does the Kestrova Solidity Security Scan MCP server have?

3 tools: 1 irreversible, 1 write, 1 read. payment_terms, scan_solidity_full and scan_solidity_preview.

Does the Kestrova Solidity Security Scan MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Kestrova Solidity Security Scan MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Kestrova Solidity Security Scan MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.