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.

io.github.mdimamhosen/jev-guide

REMOTE · JEV-GUIDE.JEVROUTER.WORKERS.DEV

Set up the JEV model router for Claude Code, Codex and Cursor, and install MCP servers.

68 Trust /100

Last scanned (57 minutes ago)

Scores higher than 57% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Developer Tools

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 Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 309 tokens (~77/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

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

  • 15 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Oct 26 67

    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 17 Oct 2026 · Probed https://jev-guide.jevrouter.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jevrouter.workers.dev CN=YE1,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA384 523c23c608ad359d679889bd343a4acd23c
SANs: *.jevrouter.workers.dev, jevrouter.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 jev-guide.jevrouter.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jev-guide.jevrouter.workers.dev/mcp Verified 200
http (plaintext) http://jev-guide.jevrouter.workers.dev/mcp Served over HTTP 200
MCP tools · 4 exposed · ~278 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
get_client_setup ~98

Returns the exact configuration that points Claude Code, Codex or Cursor at a JEV gateway. Use when a user asks how to connect a coding agent to JEV.

NameTypeReqDescription
clientstringyesWhich coding agent to configure
keystring–JEV API key, if the gateway requires one
urlstring–JEV gateway base URL (default http://127.0.0.1:4000)

No output schema declared.

No examples provided.

get_mcp_install_commands ~90

Returns the commands that install a remote MCP server into Claude Code, Codex and Cursor, plus a one-click Cursor install link. Use when a user wants to add an MCP server URL to their agents.

NameTypeReqDescription
namestringyesShort server name, e.g. "weather"
urlstringyesStreamable HTTP MCP URL, e.g. https://example.com/mcp

No output schema declared.

No examples provided.

list_model_aliases ~41

Lists the JEV model names (jev-auto, jev-fast, …) and what each one does. Use when choosing which model name to configure.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

route_prompt ~49

Shows which task class and model tier JEV's jev-auto router would pick for a coding prompt. Use to explain or predict routing decisions.

NameTypeReqDescription
promptstringyesThe user prompt to classify

No output schema declared.

No examples provided.

Install

How do I install the io.github.mdimamhosen/jev-guide MCP server?

io.github.mdimamhosen/jev-guide is a hosted endpoint at https://jev-guide.jevrouter.workers.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 · jev-guide.jevrouter.workers.dev

# add to Claude Code
claude mcp add --transport http mdimamhosen-jev-guide 'https://jev-guide.jevrouter.workers.dev/mcp'
Common questions

What is the io.github.mdimamhosen/jev-guide MCP server?

io.github.mdimamhosen/jev-guide is an MCP server listed in the public MCP registry as io.github.mdimamhosen/jev-guide. Set up the JEV model router for Claude Code, Codex and Cursor, and install MCP servers. This page covers its hosted endpoint (https://jev-guide.jevrouter.workers.dev/mcp).

Is the io.github.mdimamhosen/jev-guide MCP server safe to use?

io.github.mdimamhosen/jev-guide scores 68 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 io.github.mdimamhosen/jev-guide MCP server expose?

io.github.mdimamhosen/jev-guide exposes 4 tools: route_prompt, get_client_setup, get_mcp_install_commands, list_model_aliases. Their descriptions and schemas cost roughly 278 tokens of context every time the server is loaded.

Does the io.github.mdimamhosen/jev-guide MCP server require authentication?

No. We connected to io.github.mdimamhosen/jev-guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.mdimamhosen/jev-guide MCP server still maintained?

io.github.mdimamhosen/jev-guide 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.