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.

Diogenes EVE: Frontier Sui Move MCP

REMOTE · DIOGENES-MICRO-GATEWAY.CORINTH.WORKERS.DEV

CCP Games EVE: Frontier Sui Move Smart Assembly coder, Smart Gate planner & SSU AMM.

+4 this week 66 Trust /100

Last scanned (22 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Crypto and Web3

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 Security74
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2863 tokens (~204/item across 14 items; 14 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 Management0
  • Stability check failed: schema churn in the 15 days we've observed: 9 tool removals, 0 breaking changes, 0 auth/transport breaks, 14 additions. See how to fix → Fail
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.

  • 3 Nov 26 +48
    • Stability: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • HTTPS: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 2 Nov 26 −44
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: fail → unverified ▼ security
    • HTTPS: fail → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 26 Oct 26 0
    • Tool “analyze_eve_killmail_threats” rewrote its description, which is the text the model reads security
    • Tool “audit_eve_tribe_standings” rewrote its description, which is the text the model reads security
    • Tool “compile_eve_gate_acl” rewrote its description, which is the text the model reads security
    • Tool “find_eve_ssu_arbitrage” rewrote its description, which is the text the model reads security
    • Tool “generate_eve_assembly_move” rewrote its description, which is the text the model reads security
    • Tool “inspect_eve_assembly_state” rewrote its description, which is the text the model reads security
    • Tool “monitor_eve_constellation_fuel” rewrote its description, which is the text the model reads security
    • Tool “optimize_eve_node_power” rewrote its description, which is the text the model reads security
    • Tool “plan_eve_gate_route” rewrote its description, which is the text the model reads security
    • Tool “prioritize_eve_turret_targets” rewrote its description, which is the text the model reads security
    • Tool “quote_eve_ssu_market” rewrote its description, which is the text the model reads security
    • Tool “simulate_eve_capacitor_siege” rewrote its description, which is the text the model reads security
    • Tool “simulate_eve_sui_ptb” rewrote its description, which is the text the model reads security
    • Tool “verify_eve_zklogin_character” rewrote its description, which is the text the model reads security
  • 21 Oct 26 +6
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 2.5.0 ▼ security
    • Tool “eve_gate_route_planner” was removed ▼ security
    • Tool “eve_killmail_threat_intel” was removed ▼ security
    • Tool “eve_move_assembly_coder” was removed ▼ security
    • Tool “eve_network_node_gj_optimizer” was removed ▼ security
    • Tool “eve_sovereignty_fuel_radar” was removed ▼ security
    • Tool “eve_ssu_market_maker” was removed ▼ security
    • Tool “eve_sui_ptb_simulator” was removed ▼ security
    • Tool “eve_turret_target_matrix” was removed ▼ security
    • Tool “eve_zklogin_character_verifier” was removed ▼ security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 15% → 100% ▲ functional
    • First check of Tool coverage: 100 functional
    • Schema quality: poor → excellent functional
    • New tool “analyze_eve_killmail_threats” functional
    • New tool “audit_eve_tribe_standings” functional
    • New tool “compile_eve_gate_acl” functional
    • New tool “find_eve_ssu_arbitrage” functional
    • New tool “generate_eve_assembly_move” functional
    • New tool “inspect_eve_assembly_state” functional
    • New tool “monitor_eve_constellation_fuel” functional
    • New tool “optimize_eve_node_power” functional
    • New tool “plan_eve_gate_route” functional
    • New tool “prioritize_eve_turret_targets” functional
    • New tool “quote_eve_ssu_market” functional
    • New tool “simulate_eve_capacitor_siege” functional
    • New tool “simulate_eve_sui_ptb” functional
    • New tool “verify_eve_zklogin_character” functional
  • 20 Oct 26 56

    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 4 Nov 2026 · Probed https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=corinth.workers.dev CN=YE2,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA384 633c3321385182b27c585c86398dc860724
SANs: *.corinth.workers.dev, corinth.workers.dev
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 diogenes-micro-gateway.corinth.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
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier Verified 200
http (plaintext) http://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier HTTPS enforced 301 https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier
MCP tools · 14 exposed · ~2,691 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
analyze_eve_killmail_threats ~191

Analyzes on-chain EVE Frontier killmail.move events in a solar system to quantify gatecamp ambush probability and identify dominant hostile hull doctrines. Use when assessing solar system PvP danger before jumping a hauler or fleet into a system; for computing real-time weapon target-lock priorities during active grid combat, use prioritize_eve_turret_targets instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'system_id' ('time_window' defaults to '1h'), supports '?demo=true' or L402 (30 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
system_idstringyesSolar system identifier to analyze for recent killmail activity (e.g. 'System-Frontier-01').
time_windowstring–Historical lookback window for killmail aggregation; defaults to '24h' when omitted.
NameTypeReqDescription
ambush_probabilitynumberyesEstimated probability (0.0 to 1.0) of an active stargate camp.
killmails_24hintegeryesTotal verified ship destructions recorded in the window.
system_idstringyesAnalyzed solar system identifier.
threat_levelstringyesTactical hazard classification ('MINIMAL', 'MODERATE', or 'CRITICAL_HAZARD').

No examples provided.

audit_eve_tribe_standings ~178

Audits EVE Frontier Tribe diplomatic standings, friendly/hostile reputation scores, and pilot override entries across solar systems. Use when checking diplomatic relations or detecting conflicting friendly-fire rules across tribe registries; for compiling those standings into executable Sui Move Smart Gate ACL bytecode, use compile_eve_gate_acl instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'tribe_id' ('standing_filter' defaults to 'all'), supports '?demo=true' or L402 (20 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
standing_filterstring–Filter returned diplomatic relationships by tier; defaults to 'all' when omitted.
tribe_idstringyesPrimary Tribe identifier or registry object ID to audit (e.g. 'tribe-corinth-01').
NameTypeReqDescription
acl_conflicts_detectedbooleanyesTrue if a pilot override contradicts their parent tribe standing.
allied_tribes_countintegeryesCount of tribes holding positive diplomatic standing.
hostile_tribes_countintegeryesCount of tribes flagged as hostile targets.
tribe_idstringyesAudited Tribe registry identifier.

No examples provided.

compile_eve_gate_acl ~191

Compiles EVE Frontier Tribe access control lists, diplomatic standings, and surge-pricing toll rules into Sui Move Smart Gate AccessPolicy constraints. Use when configuring on-chain jump permissions and LUX/SUI toll schedules for a player-owned Smart Gate; for calculating optimal multi-system jump routes across existing stargates, use plan_eve_gate_route instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'gate_assembly_id' ('toll_mode' defaults to 'standing_tiered'), supports '?demo=true' or L402 (30 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
gate_assembly_idstringyesTarget Smart Gate assembly identifier (e.g. 'gate-lagrange-04').
toll_modestring–Pricing curve applied to non-allied jumpers; defaults to 'standing_tiered' when omitted.
NameTypeReqDescription
access_policy_move_structstringyesCompiled Sui Move AccessPolicy struct definition and entry verifier.
base_toll_mistintegeryesCalculated base jump toll denominated in MIST/LUX units.
gate_assembly_idstringyesTarget Smart Gate object identifier.
hostile_block_enforcedbooleanyesTrue when hostile tribes are rejected at the Move witness gate.

No examples provided.

find_eve_ssu_arbitrage ~203

Scans Smart Storage Unit (SSU) bid/ask spreads across star systems against ship cargo capacity and stargate fuel costs to rank net-profitable arbitrage loops. Use when planning multi-system trade runs to maximize net LUX profit per gigajoule of fuel burned; for calculating internal bid/ask market-maker quotes for your own SSU, use quote_eve_ssu_market instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'origin_system' ('hull_cargo_class' defaults to 'light_courier'), supports '?demo=true' or L402 (30 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
hull_cargo_classstring–Trade vessel hull class determining cargo volume and fuel mass; defaults to 'medium_hauler' when omitted.
origin_systemstringyesStarting solar system for the trade vessel (e.g. 'System-Alpha').
NameTypeReqDescription
best_commoditystringyesHighest-margin commodity identified across reachable SSUs.
buy_ssu_systemstringyesSolar system where the commodity should be purchased.
net_profit_lux_after_tollsnumberyesNet LUX profit after deducting gate tolls and fuel replacement cost.
sell_ssu_systemstringyesSolar system where the commodity should be sold.

No examples provided.

generate_eve_assembly_move ~189

Generates and statically audits Sui Move smart contract modules for EVE Frontier Smart Assemblies using Witness, Capability, and HotPotato patterns. Use when authoring custom Sui Move extensions for Smart Gates, Smart Turrets, or Smart Storage Units; for simulating pre-signed Programmable Transaction Block command arrays before wallet execution, use simulate_eve_sui_ptb instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'contract_type' ('assembly_id' defaults to 'standard'), supports '?demo=true' or L402 (45 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
assembly_idstring–Optional Smart Assembly identifier to bind into module constants; defaults to 'frontier-assembly-01' when omitted.
contract_typestringyesTarget EVE Frontier Smart Assembly archetype to synthesize and audit.
NameTypeReqDescription
module_namestringyesFully qualified Sui Move module identifier (e.g. 'frontier::smart_gate').
move_patterns_usedarrayyesVerified Sui Move safety patterns enforced in the module.
security_audit_passedbooleanyesTrue when Witness drop and Capability access checks pass static verification.
sui_move_codestringyesComplete, syntactically valid Sui Move smart contract source code.

No examples provided.

inspect_eve_assembly_state ~206

Inspects live EVE Frontier Smart Assembly on-chain object metadata, owner capability ID, online power status, and attached Sui Move package digest. Use when verifying whether a Smart Turret, Smart Gate, or Smart Storage Unit is online and checking its bound Move module before interacting; for generating or auditing custom Sui Move assembly source code, use generate_eve_assembly_move instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'assembly_id' ('assembly_class' defaults to 'smart_gate'), supports '?demo=true' or L402 (20 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
assembly_classstring–Smart Assembly hardware class used to validate expected capability fields; defaults to 'smart_gate' when omitted.
assembly_idstringyesHexadecimal Sui object ID or Frontier Smart Assembly identifier (e.g. '0x8f4a...c201' or 'assembly-alpha-01').
NameTypeReqDescription
assembly_idstringyesCanonical Smart Assembly object identifier inspected.
attached_package_digeststringyesSHA-256 bytecode digest of the custom Move extension attached to this assembly.
online_statusstringyesOperational state ('ONLINE_POWERED', 'LOW_CAPACITOR', or 'OFFLINE_UNANCHORED').
owner_cap_idstringyesBound Sui Move OwnerCap object ID controlling administrative permissions.

No examples provided.

monitor_eve_constellation_fuel ~182

Monitors constellation-wide Lagrange Network Node fuel reserves, identifies the weakest sovereignty node, and calculates logistics convoy resupply urgency. Use when auditing multi-system sovereignty fuel health across an entire tribe constellation; for optimizing gigajoule load on a single individual Lagrange Network Node, use optimize_eve_node_power instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'constellation_id' ('alert_threshold_hours' defaults to '24h'), supports '?demo=true' or L402 (30 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
alert_threshold_hoursstring–Minimum remaining fuel horizon before triggering convoy dispatch; defaults to '36h' when omitted.
constellation_idstringyesConstellation or solar system cluster identifier (e.g. 'Frontier-Delta-09').
NameTypeReqDescription
constellation_idstringyesMonitored constellation identifier.
logistics_urgencystringyesConvoy dispatch recommendation ('STABLE' or 'DISPATCH_CONVOY_IMMEDIATELY').
sovereignty_health_indexnumberyesNormalized sovereignty stability score from 0.0 to 1.0.
weakest_node_idstringyesIdentifier of the Network Node closest to fuel exhaustion.

No examples provided.

optimize_eve_node_power ~179

Calculates Lagrange Network Node hourly gigajoule (GJ) fuel burn rates, capacity headroom, and offline vulnerability windows for connected Smart Assemblies. Use when balancing steady-state power allocations on a single Lagrange Network Node; for stress-testing node capacitor depletion under active hostile fleet bombardment, use simulate_eve_capacitor_siege instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'node_id' ('operating_profile' defaults to 'balanced'), supports '?demo=true' or L402 (25 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
node_idstringyesLagrange Network Node identifier (e.g. 'node-frontier-01').
operating_profilestring–Power allocation profile across connected assemblies; defaults to 'balanced' when omitted.
NameTypeReqDescription
burn_rate_gj_per_hrnumberyesHourly gigajoule (GJ) energy consumption across attached assemblies.
hours_until_fuel_depletionnumberyesRemaining operational hours before fuel reserves reach zero.
node_idstringyesEvaluated Lagrange Network Node identifier.
offline_threat_window_hoursstringyesSafety classification ('SAFE' or 'CRITICAL_OFFLINE_IMMINENT').

No examples provided.

plan_eve_gate_route ~199

Calculates optimal stargate jump routes between EVE Frontier solar systems minimizing gigajoule fuel consumption, LUX gate tolls, or jump count. Use when plotting a ship transit path across public and tribe-restricted Smart Gates; for identifying multi-system commodity arbitrage trade loops across Smart Storage Units, use find_eve_ssu_arbitrage instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'origin_system' ('destination_system' defaults to 'standard'), supports '?demo=true' or L402 (25 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
destination_systemstringyesTarget destination solar system identifier (e.g. 'System-Omega').
optimize_forstring–Routing objective function weighting fuel burn vs tolls; defaults to 'lowest_fuel' when omitted.
origin_systemstringyesStarting solar system identifier (e.g. 'System-Alpha').
NameTypeReqDescription
estimated_fuel_burn_gjnumberyesTotal ship fuel consumption in gigajoules (GJ) across the route.
optimal_hopsintegeryesTotal number of stargate jumps along the selected path.
total_gate_tolls_luxnumberyesCumulative Smart Gate transit tolls required in LUX.
waypointsarrayyesOrdered list of solar systems and Lagrange Smart Gates traversed.

No examples provided.

prioritize_eve_turret_targets ~185

Evaluates radar contacts by range, transversal velocity, and Tribe standing to output deterministic Smart Turret target-lock priorities and fire authorizations. Use when ranking active grid radar contacts for automated Smart Turret engagement; for reviewing historical solar system killmails and ambush probabilities before transit, use analyze_eve_killmail_threats instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'turret_id' ('engagement_doctrine' defaults to 'highest_threat'), supports '?demo=true' or L402 (25 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
engagement_doctrinestring–Target selection doctrine weighting range vs angular tracking; defaults to 'highest_threat' when omitted.
turret_idstringyesSmart Turret assembly identifier (e.g. 'turret-alpha-01').
NameTypeReqDescription
fire_verdictstringyesEngagement command ('ENGAGE_IMMEDIATELY' or 'HOLD_FIRE').
primary_target_lockstringyesContact ID of the highest-priority hostile vessel to engage.
sui_move_witness_verdictstringyesOn-chain witness authorization status ('AUTHORIZED_HOSTILE').
turret_idstringyesSmart Turret identifier.

No examples provided.

quote_eve_ssu_market ~195

Computes dynamic bonding-curve bid/ask quotes in LUX and per-transaction anti-drain caps for a player-owned Smart Storage Unit (SSU). Use when setting automated market-maker buy/sell prices for a single SSU vending inventory; for scanning multiple SSUs across star systems to find profitable trade routes, use find_eve_ssu_arbitrage instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'resource_type' ('pricing_regime' defaults to 'inventory_balanced'), supports '?demo=true' or L402 (25 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
pricing_regimestring–Bonding-curve slope aggressiveness; defaults to 'inventory_balanced' when omitted.
resource_typestringyesEVE Frontier commodity or ore name to price (e.g. 'Crude Fuel Ore', 'Carbonaceous Alloy').
NameTypeReqDescription
anti_drain_cap_per_txintegeryesMaximum units allowed per single transaction to prevent inventory sweeps.
recommended_buy_price_luxnumberyesBid price in LUX to offer pilots selling into the SSU.
recommended_sell_price_luxnumberyesAsk price in LUX charged to pilots buying from the SSU.
resource_typestringyesPriced EVE Frontier commodity name.

No examples provided.

simulate_eve_capacitor_siege ~191

Simulates Lagrange Network Node gigajoule (GJ) capacitor drain under sustained hostile fleet siege and computes optimal assembly load-shedding order. Use when preparing base defense power-shedding schedules against an incoming hostile fleet; for calculating routine peacetime fuel burn and reserve headroom, use optimize_eve_node_power instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'node_id' ('siege_intensity' defaults to 'skirmish_frigate_squad'), supports '?demo=true' or L402 (30 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
node_idstringyesTarget Lagrange Network Node identifier under siege simulation.
siege_intensitystring–Hostile fleet DPS and electronic-warfare drain tier; defaults to 'heavy_cruiser_wing' when omitted.
NameTypeReqDescription
capacitor_survival_minutesnumberyesMinutes before capacitor reserves drop below turret firing threshold.
defense_verdictstringyesSiege readiness assessment ('HOLDS_UNTIL_REINFORCEMENT' or 'SHED_SSU_LOAD_IMMEDIATELY').
load_shedding_sequencearrayyesOrdered list of non-essential assemblies to power down first.
node_idstringyesSimulated Lagrange Network Node identifier.

No examples provided.

simulate_eve_sui_ptb ~210

Simulates Sui Programmable Transaction Block (PTB) command sequences to detect unauthorized coin splits, object transfers, and unconsumed HotPotato receipts. Use when auditing an untrusted EVE Frontier transaction bundle before signing with a pilot wallet; for verifying pilot zkLogin JWT proofs and character ownership capabilities, use verify_eve_zklogin_character instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'ptb_commands_json' ('strictness_mode' defaults to 'strict_zero_drain'), supports '?demo=true' or L402 (35 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
ptb_commands_jsonstringyesJSON-serialized array of PTB commands or comma-separated Move calls (e.g. '[{"kind":"SplitCoins"},{"kind":"MoveCall"}]').
strictness_modestring–Simulation policy controlling whether multi-transfer PTBs are blocked; defaults to 'strict_zero_drain' when omitted.
NameTypeReqDescription
hidden_coin_transfer_detectedbooleanyesTrue if unauthorized SplitCoins or TransferObjects drains are detected.
hot_potato_receipts_balancedbooleanyesTrue if every Move HotPotato struct created in the PTB is consumed before exit.
ptb_command_countintegeryesNumber of PTB commands statically simulated.
signing_verdictstringyesFinal safety recommendation ('SAFE_EVE_FRONTIER_PTB' or 'BLOCK_SUSPICIOUS_PTB_DRAIN').

No examples provided.

verify_eve_zklogin_character ~192

Verifies EVE Frontier Sui zkLogin BN254 zero-knowledge proofs, ephemeral session signatures, and SmartCharacter ownership capabilities. Use when authenticating a pilot's off-chain OAuth/zkLogin session before granting tribe vault or dApp access; for auditing tribe-wide diplomatic standings and reputation registries, use audit_eve_tribe_standings instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'jwt_proof' ('ephemeral_scheme' defaults to 'ED25519'), supports '?demo=true' or L402 (25 sats), and returns HTTP 400 if invalid.

NameTypeReqDescription
ephemeral_schemestring–Cryptographic signature scheme of the ephemeral session key; defaults to 'ED25519' when omitted.
jwt_proofstringyesEncoded Sui zkLogin proof payload or JWT session token string (minimum 20 characters).
NameTypeReqDescription
character_verifiedbooleanyesTrue when the zkLogin BN254 proof and salt derivation are valid.
sui_address_derivedstringyesDeterministic 32-byte Sui address derived from the zkLogin issuer and salt.
tribe_acl_eligiblebooleanyesTrue if the verified SmartCharacter holds active Tribe membership.
verification_verdictstringyesAuthentication result ('AUTHENTICATED_FRONTIER_PILOT' or 'INVALID_ZK_PROOF').

No examples provided.

Install

How do I install the Diogenes EVE: Frontier Sui Move MCP server?

Diogenes EVE: Frontier Sui Move MCP is a hosted endpoint at https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier, 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 · diogenes-micro-gateway.corinth.workers.dev

# add to Claude Code
claude mcp add --transport http stand-out-of-my-sun-diogenes-eve-frontier-mcp 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier'
Common questions

What is the Diogenes EVE: Frontier Sui Move MCP server?

Diogenes EVE: Frontier Sui Move MCP is listed in the public MCP registry as io.github.stand-out-of-my-sun/diogenes-eve-frontier-mcp. CCP Games EVE: Frontier Sui Move Smart Assembly coder, Smart Gate planner & SSU AMM. This page covers its hosted endpoint (https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier).

Is the Diogenes EVE: Frontier Sui Move MCP server safe to use?

Diogenes EVE: Frontier Sui Move MCP scores 66 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 Diogenes EVE: Frontier Sui Move MCP server expose?

Diogenes EVE: Frontier Sui Move MCP exposes 14 tools: inspect_eve_assembly_state, audit_eve_tribe_standings, generate_eve_assembly_move, compile_eve_gate_acl, simulate_eve_sui_ptb, and 9 more. Their descriptions and schemas cost roughly 2,691 tokens of context every time the server is loaded.

Does the Diogenes EVE: Frontier Sui Move MCP server require authentication?

No. We connected to Diogenes EVE: Frontier Sui Move MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Diogenes EVE: Frontier Sui Move MCP server still maintained?

Diogenes EVE: Frontier Sui Move MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.