# 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.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `diogenes-micro-gateway.corinth.workers.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-eve-frontier-mcp/mcp-eve-frontier.md), [page](https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-eve-frontier-mcp/mcp-eve-frontier)

## Channel facts

- Endpoint: `https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 16 days we've observed: 9 tool removals, 0 breaking changes, 0 auth/transport breaks, 14 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http stand-out-of-my-sun-diogenes-eve-frontier-mcp 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier'
```

### Cursor

```json
{
  "mcpServers": {
    "stand-out-of-my-sun-diogenes-eve-frontier-mcp": {
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stand-out-of-my-sun-diogenes-eve-frontier-mcp": {
      "type": "http",
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier"
    }
  }
}
```

### Codex

```toml
[mcp_servers.stand-out-of-my-sun-diogenes-eve-frontier-mcp]
url = "https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stand-out-of-my-sun-diogenes-eve-frontier-mcp": {
      "type": "remote",
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stand-out-of-my-sun-diogenes-eve-frontier-mcp --url 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  stand-out-of-my-sun-diogenes-eve-frontier-mcp:
    url: "https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier"
```

### Netclaw

```json
{
  "McpServers": {
    "stand-out-of-my-sun-diogenes-eve-frontier-mcp": {
      "Transport": "http",
      "Url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier"
    }
  }
}
```

### Vellum

```bash
assistant mcp add stand-out-of-my-sun-diogenes-eve-frontier-mcp -t streamable-http -u 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier'
```

### Other

```json
{
  "mcpServers": {
    "stand-out-of-my-sun-diogenes-eve-frontier-mcp": {
      "type": "http",
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 66, +48)

- [security regression] Stability: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] HTTPS: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100

### 2026-11-02 (score 18, −44)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: fail → unverified
- [security regression] HTTPS: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-26 (score 62, 0)

- [security] 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

### 2026-10-21 (score 62, +6)

- [security regression] Stability: unverified → fail
- [security regression] A breaking change shipped without a version bump: still 2.5.0
- [security regression] Tool “eve_gate_route_planner” was removed
- [security regression] Tool “eve_killmail_threat_intel” was removed
- [security regression] Tool “eve_move_assembly_coder” was removed
- [security regression] Tool “eve_network_node_gj_optimizer” was removed
- [security regression] Tool “eve_sovereignty_fuel_radar” was removed
- [security regression] Tool “eve_ssu_market_maker” was removed
- [security regression] Tool “eve_sui_ptb_simulator” was removed
- [security regression] Tool “eve_turret_target_matrix” was removed
- [security regression] Tool “eve_zklogin_character_verifier” was removed
- [functional regression] Schema quality: pass → fail
- [functional improvement] 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”

### 2026-10-20 (score 56)

First indexed and scored.

## MCP tools (14)

### `inspect_eve_assembly_state` (~206 tokens)

EVE Frontier Smart Assembly On-Chain State & Capability Inspector

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.

Input parameters:

- `assembly_class` (string): Smart Assembly hardware class used to validate expected capability fields; defaults to 'smart_gate' when omitted.
- `assembly_id` (string, required): Hexadecimal Sui object ID or Frontier Smart Assembly identifier (e.g. '0x8f4a...c201' or 'assembly-alpha-01').

Output parameters:

- `assembly_id` (string): Canonical Smart Assembly object identifier inspected.
- `attached_package_digest` (string): SHA-256 bytecode digest of the custom Move extension attached to this assembly.
- `online_status` (string): Operational state ('ONLINE_POWERED', 'LOW_CAPACITOR', or 'OFFLINE_UNANCHORED').
- `owner_cap_id` (string): Bound Sui Move OwnerCap object ID controlling administrative permissions.

### `audit_eve_tribe_standings` (~178 tokens)

EVE Frontier Tribe Diplomatic Standings & Access Matrix Auditor

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.

Input parameters:

- `standing_filter` (string): Filter returned diplomatic relationships by tier; defaults to 'all' when omitted.
- `tribe_id` (string, required): Primary Tribe identifier or registry object ID to audit (e.g. 'tribe-corinth-01').

Output parameters:

- `acl_conflicts_detected` (boolean): True if a pilot override contradicts their parent tribe standing.
- `allied_tribes_count` (integer): Count of tribes holding positive diplomatic standing.
- `hostile_tribes_count` (integer): Count of tribes flagged as hostile targets.
- `tribe_id` (string): Audited Tribe registry identifier.

### `generate_eve_assembly_move` (~189 tokens)

EVE Frontier Sui Move Smart Assembly Contract Generator & Auditor

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.

Input parameters:

- `assembly_id` (string): Optional Smart Assembly identifier to bind into module constants; defaults to 'frontier-assembly-01' when omitted.
- `contract_type` (string, required): Target EVE Frontier Smart Assembly archetype to synthesize and audit.

Output parameters:

- `module_name` (string): Fully qualified Sui Move module identifier (e.g. 'frontier::smart_gate').
- `move_patterns_used` (array): Verified Sui Move safety patterns enforced in the module.
- `security_audit_passed` (boolean): True when Witness drop and Capability access checks pass static verification.
- `sui_move_code` (string): Complete, syntactically valid Sui Move smart contract source code.

### `compile_eve_gate_acl` (~191 tokens)

EVE Frontier Smart Gate Tribe ACL & Dynamic Toll Bytecode Compiler

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.

Input parameters:

- `gate_assembly_id` (string, required): Target Smart Gate assembly identifier (e.g. 'gate-lagrange-04').
- `toll_mode` (string): Pricing curve applied to non-allied jumpers; defaults to 'standing_tiered' when omitted.

Output parameters:

- `access_policy_move_struct` (string): Compiled Sui Move AccessPolicy struct definition and entry verifier.
- `base_toll_mist` (integer): Calculated base jump toll denominated in MIST/LUX units.
- `gate_assembly_id` (string): Target Smart Gate object identifier.
- `hostile_block_enforced` (boolean): True when hostile tribes are rejected at the Move witness gate.

### `simulate_eve_sui_ptb` (~210 tokens)

EVE Frontier Sui Move PTB Coin-Drain & HotPotato Safety Simulator

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.

Input parameters:

- `ptb_commands_json` (string, required): JSON-serialized array of PTB commands or comma-separated Move calls (e.g. '[{"kind":"SplitCoins"},{"kind":"MoveCall"}]').
- `strictness_mode` (string): Simulation policy controlling whether multi-transfer PTBs are blocked; defaults to 'strict_zero_drain' when omitted.

Output parameters:

- `hidden_coin_transfer_detected` (boolean): True if unauthorized SplitCoins or TransferObjects drains are detected.
- `hot_potato_receipts_balanced` (boolean): True if every Move HotPotato struct created in the PTB is consumed before exit.
- `ptb_command_count` (integer): Number of PTB commands statically simulated.
- `signing_verdict` (string): Final safety recommendation ('SAFE_EVE_FRONTIER_PTB' or 'BLOCK_SUSPICIOUS_PTB_DRAIN').

### `verify_eve_zklogin_character` (~192 tokens)

EVE Frontier Sui zkLogin BN254 Proof & SmartCharacter Verifier

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.

Input parameters:

- `ephemeral_scheme` (string): Cryptographic signature scheme of the ephemeral session key; defaults to 'ED25519' when omitted.
- `jwt_proof` (string, required): Encoded Sui zkLogin proof payload or JWT session token string (minimum 20 characters).

Output parameters:

- `character_verified` (boolean): True when the zkLogin BN254 proof and salt derivation are valid.
- `sui_address_derived` (string): Deterministic 32-byte Sui address derived from the zkLogin issuer and salt.
- `tribe_acl_eligible` (boolean): True if the verified SmartCharacter holds active Tribe membership.
- `verification_verdict` (string): Authentication result ('AUTHENTICATED_FRONTIER_PILOT' or 'INVALID_ZK_PROOF').

### `plan_eve_gate_route` (~199 tokens)

EVE Frontier Multi-Hop Smart Gate Fuel & Toll Route Planner

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.

Input parameters:

- `destination_system` (string, required): Target destination solar system identifier (e.g. 'System-Omega').
- `optimize_for` (string): Routing objective function weighting fuel burn vs tolls; defaults to 'lowest_fuel' when omitted.
- `origin_system` (string, required): Starting solar system identifier (e.g. 'System-Alpha').

Output parameters:

- `estimated_fuel_burn_gj` (number): Total ship fuel consumption in gigajoules (GJ) across the route.
- `optimal_hops` (integer): Total number of stargate jumps along the selected path.
- `total_gate_tolls_lux` (number): Cumulative Smart Gate transit tolls required in LUX.
- `waypoints` (array): Ordered list of solar systems and Lagrange Smart Gates traversed.

### `optimize_eve_node_power` (~179 tokens)

EVE Frontier Lagrange Network Node Gigajoule & Fuel Burn Optimizer

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.

Input parameters:

- `node_id` (string, required): Lagrange Network Node identifier (e.g. 'node-frontier-01').
- `operating_profile` (string): Power allocation profile across connected assemblies; defaults to 'balanced' when omitted.

Output parameters:

- `burn_rate_gj_per_hr` (number): Hourly gigajoule (GJ) energy consumption across attached assemblies.
- `hours_until_fuel_depletion` (number): Remaining operational hours before fuel reserves reach zero.
- `node_id` (string): Evaluated Lagrange Network Node identifier.
- `offline_threat_window_hours` (string): Safety classification ('SAFE' or 'CRITICAL_OFFLINE_IMMINENT').

### `simulate_eve_capacitor_siege` (~191 tokens)

EVE Frontier Lagrange Node Siege Capacitor Depletion Simulator

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.

Input parameters:

- `node_id` (string, required): Target Lagrange Network Node identifier under siege simulation.
- `siege_intensity` (string): Hostile fleet DPS and electronic-warfare drain tier; defaults to 'heavy_cruiser_wing' when omitted.

Output parameters:

- `capacitor_survival_minutes` (number): Minutes before capacitor reserves drop below turret firing threshold.
- `defense_verdict` (string): Siege readiness assessment ('HOLDS_UNTIL_REINFORCEMENT' or 'SHED_SSU_LOAD_IMMEDIATELY').
- `load_shedding_sequence` (array): Ordered list of non-essential assemblies to power down first.
- `node_id` (string): Simulated Lagrange Network Node identifier.

### `monitor_eve_constellation_fuel` (~182 tokens)

EVE Frontier Constellation Sovereignty & Multi-Node Fuel Radar

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.

Input parameters:

- `alert_threshold_hours` (string): Minimum remaining fuel horizon before triggering convoy dispatch; defaults to '36h' when omitted.
- `constellation_id` (string, required): Constellation or solar system cluster identifier (e.g. 'Frontier-Delta-09').

Output parameters:

- `constellation_id` (string): Monitored constellation identifier.
- `logistics_urgency` (string): Convoy dispatch recommendation ('STABLE' or 'DISPATCH_CONVOY_IMMEDIATELY').
- `sovereignty_health_index` (number): Normalized sovereignty stability score from 0.0 to 1.0.
- `weakest_node_id` (string): Identifier of the Network Node closest to fuel exhaustion.

### `quote_eve_ssu_market` (~195 tokens)

EVE Frontier Smart Storage Unit (SSU) Bonding-Curve Market Pricer

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.

Input parameters:

- `pricing_regime` (string): Bonding-curve slope aggressiveness; defaults to 'inventory_balanced' when omitted.
- `resource_type` (string, required): EVE Frontier commodity or ore name to price (e.g. 'Crude Fuel Ore', 'Carbonaceous Alloy').

Output parameters:

- `anti_drain_cap_per_tx` (integer): Maximum units allowed per single transaction to prevent inventory sweeps.
- `recommended_buy_price_lux` (number): Bid price in LUX to offer pilots selling into the SSU.
- `recommended_sell_price_lux` (number): Ask price in LUX charged to pilots buying from the SSU.
- `resource_type` (string): Priced EVE Frontier commodity name.

### `find_eve_ssu_arbitrage` (~203 tokens)

EVE Frontier Multi-System SSU Commodity Arbitrage Route Finder

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.

Input parameters:

- `hull_cargo_class` (string): Trade vessel hull class determining cargo volume and fuel mass; defaults to 'medium_hauler' when omitted.
- `origin_system` (string, required): Starting solar system for the trade vessel (e.g. 'System-Alpha').

Output parameters:

- `best_commodity` (string): Highest-margin commodity identified across reachable SSUs.
- `buy_ssu_system` (string): Solar system where the commodity should be purchased.
- `net_profit_lux_after_tolls` (number): Net LUX profit after deducting gate tolls and fuel replacement cost.
- `sell_ssu_system` (string): Solar system where the commodity should be sold.

### `analyze_eve_killmail_threats` (~191 tokens)

EVE Frontier On-Chain Killmail Threat & Gatecamp Ambush Analyzer

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.

Input parameters:

- `system_id` (string, required): Solar system identifier to analyze for recent killmail activity (e.g. 'System-Frontier-01').
- `time_window` (string): Historical lookback window for killmail aggregation; defaults to '24h' when omitted.

Output parameters:

- `ambush_probability` (number): Estimated probability (0.0 to 1.0) of an active stargate camp.
- `killmails_24h` (integer): Total verified ship destructions recorded in the window.
- `system_id` (string): Analyzed solar system identifier.
- `threat_level` (string): Tactical hazard classification ('MINIMAL', 'MODERATE', or 'CRITICAL_HAZARD').

### `prioritize_eve_turret_targets` (~185 tokens)

EVE Frontier Smart Turret Angular Tracking & Target Priority Calculator

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.

Input parameters:

- `engagement_doctrine` (string): Target selection doctrine weighting range vs angular tracking; defaults to 'highest_threat' when omitted.
- `turret_id` (string, required): Smart Turret assembly identifier (e.g. 'turret-alpha-01').

Output parameters:

- `fire_verdict` (string): Engagement command ('ENGAGE_IMMEDIATELY' or 'HOLD_FIRE').
- `primary_target_lock` (string): Contact ID of the highest-priority hostile vessel to engage.
- `sui_move_witness_verdict` (string): On-chain witness authorization status ('AUTHORIZED_HOSTILE').
- `turret_id` (string): Smart Turret identifier.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-eve-frontier-mcp/mcp-eve-frontier#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 18
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 62
- 2026-10-29: 62
- 2026-10-28: 62
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 62
- 2026-10-24: 62
- 2026-10-23: 62
- 2026-10-22: 62
- 2026-10-21: 62
- 2026-10-20: 56

## 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier
- Repository: https://github.com/stand-out-of-my-sun/diogenes-eve-frontier-mcp
- Website: https://diogenes-micro-gateway.corinth.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-eve-frontier-mcp/mcp-eve-frontier.xml
- Changelog JSON feed: https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-eve-frontier-mcp/mcp-eve-frontier.json
- HTML version of this page: https://verifymcp.io/servers/stand-out-of-my-sun-diogenes-eve-frontier-mcp/mcp-eve-frontier