Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RUNaDIVA

REMOTE · RUNADIVA.COM · SCANNED OCT 1

Autonomous Decision Intelligence for evaluating economic decisions before value is committed.

Available components

60 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 131 tokens (~65/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 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 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 3 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
Install

How do I install the RUNaDIVA MCP server?

RUNaDIVA is a hosted endpoint at https://runadiva.com/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 · runadiva.com

# add to Claude Code
claude mcp add --transport http com-runadiva-runadiva 'https://runadiva.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-runadiva-runadiva": {
      "url": "https://runadiva.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-runadiva-runadiva": {
      "type": "http",
      "url": "https://runadiva.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-runadiva-runadiva]
url = "https://runadiva.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-runadiva-runadiva": {
      "type": "remote",
      "url": "https://runadiva.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-runadiva-runadiva --url 'https://runadiva.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-runadiva-runadiva:
    url: "https://runadiva.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-runadiva-runadiva": {
      "Transport": "http",
      "Url": "https://runadiva.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-runadiva-runadiva -t streamable-http -u 'https://runadiva.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-runadiva-runadiva": {
      "type": "http",
      "url": "https://runadiva.com/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.

  • 30 Sept 26 +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.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 58

    First indexed and scored.

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 1 Oct 2026 · Probed https://runadiva.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=runadiva.com CN=YE2,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 5e69eda25af57dcedd6df37676fc2764e02
SANs: *.runadiva.com, runadiva.com
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 runadiva.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
runadiva.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://runadiva.com/mcp Verified 200
http (plaintext) http://runadiva.com/mcp HTTPS enforced 301 https://runadiva.com/mcp
MCP tools · 2 exposed · ~108 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. 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 →

Tool Tokens
evaluate_economic_decision ~80

Evaluate a proposed economic option against caller-supplied alternatives and constraints. Returns EXECUTE, SWITCH, VERIFY, or BLOCK with transparent evidence and measurable savings when available. Does not search external markets.

NameTypeReqDescription
constraintsobject––
currencystringyes–
optionsarrayyes–
proposed_option_idstringyes–

No output schema declared.

No examples provided.

evaluate_sandbox_case ~28

Evaluate one fixed synthetic RUNaDIVA sandbox case.

NameTypeReqDescription
casestringyes–

No output schema declared.

No examples provided.

Common questions

What is the RUNaDIVA MCP server?

RUNaDIVA is an MCP server listed in the public MCP registry as com.runadiva/runadiva. Autonomous Decision Intelligence for evaluating economic decisions before value is committed. This page covers its hosted endpoint (https://runadiva.com/mcp).

Is the RUNaDIVA MCP server safe to use?

RUNaDIVA scores 60 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 RUNaDIVA MCP server expose?

RUNaDIVA exposes 2 tools: evaluate_sandbox_case, evaluate_economic_decision. Their descriptions and schemas cost roughly 108 tokens of context every time the server is loaded.

Does the RUNaDIVA MCP server require authentication?

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

Is the RUNaDIVA MCP server still maintained?

RUNaDIVA is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.