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.

Euvra

REMOTE · EUVRA.DEV

Discover, compare, route, and execute machine-accessible capabilities for AI agents.

Available components

+4 this week 74 Trust /100

Last scanned (2 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 17 Oct 2026.

Category AI and Machine Learning

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 Security63
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 448 tokens (~149/item across 3 items; 3 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 Management57
  • Stability observed for 17 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 (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_capability" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • 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 current MCP spec version (2026-07-28).Pass
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.

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 11 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.

  • 10 Oct 26 +1
    • Schema quality: pass → fail ▼ functional
  • 6 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.

  • 4 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.

  • 2 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.

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 17 Oct 2026 · Probed https://euvra.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=euvra.dev CN=YR1,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 RSA 2048 SHA256-RSA 5067b8a8cf8adad480c2a38aeab33fc3f46
SANs: euvra.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of euvra.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
euvra.dev. 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
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://euvra.dev/mcp Verified 200
http (plaintext) http://euvra.dev/mcp HTTPS enforced 308 https://euvra.dev/mcp
MCP tools · 3 exposed · ~401 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
compare_capabilities ~57

Ask Euvra to compare discovered providers for a request and select the strongest route candidate. This does not execute the provider.

NameTypeReqDescription
limitinteger–Maximum alternative routes to return.
querystringyesNatural-language capability request.

Structured output declared, but exposes no named fields.

No examples provided.

discover_capabilities ~60

Discover and rank machine-accessible capabilities that may satisfy a natural-language request. Returns evidence, operational status, and ranking signals without executing a provider.

NameTypeReqDescription
limitinteger–Maximum results to return.
querystringyesNatural-language capability request.

Structured output declared, but exposes no named fields.

No examples provided.

execute_capability ~284

Execute a real action using a live MCP provider selected by Euvra. Use discover_capabilities to find available capabilities and compare_capabilities to inspect route readiness before execution. Call this tool only when the user wants the action performed, not merely researched or compared. Supply a specific natural-language query describing the desired action and an arguments object containing the selected provider tool inputs when known. Euvra independently re-plans the route and does not accept caller-selected provider IDs, endpoints, or tool names. Execution may return NO_ROUTE, AUTH_REQUIRED, or BLOCKED if no eligible live tool is available. Paid execution requires an x402 payment of 0.01 USDC on the configured network; a client without payment support may receive payment requirements instead of an executed result. Do not claim the action succeeded until the response confirms success.

NameTypeReqDescription
argumentsobject–Optional provider-tool input values, keyed by the selected tool's expected parameter names. Inspect compare_capabilities selected.inputSchema when available. For example, a search tool might accept {…
querystringyesRequired. Describe the concrete action to execute in natural language, including the target and desired outcome. Euvra uses this text to choose and verify a live MCP provider.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Euvra MCP server?

Euvra is a hosted endpoint at https://euvra.dev/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 · euvra.dev

# add to Claude Code
claude mcp add --transport http dev-euvra-euvra 'https://euvra.dev/mcp'
Common questions

What is the Euvra MCP server?

Euvra is an MCP server listed in the public MCP registry as dev.euvra/euvra. Discover, compare, route, and execute machine-accessible capabilities for AI agents. This page covers its hosted endpoint (https://euvra.dev/mcp).

Is the Euvra MCP server safe to use?

Euvra scores 74 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 Euvra MCP server expose?

Euvra exposes 3 tools: discover_capabilities, compare_capabilities, execute_capability. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.

Does the Euvra MCP server require authentication?

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

Is the Euvra MCP server still maintained?

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