APPSIDE / MCP DIRECTORY

Diogenes Eve Frontier

Connect to Diogenes Eve Frontier: Developer Tools, API Key authentication. See its latest connection check and available tools at https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier.

← All MCP servers

CCP Games EVE: Frontier Sui Move Smart Assembly coder, Smart Gate route & toll planner, Lagrange GJ network node optimizer, SSU AMM market maker, and Sui PTB simulator. 9 tools:…

Handshake passed

Endpoint
https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier
Category
Developer Tools
Authentication
API Key
Maintainer
Diogenes Eve Frontier
Last checked
2026-11-02 22:09 UTC

Add the badge to your README

Appside directory status

Verified means this server passed a live MCP handshake on 2026-11-02 22:09 UTC. The badge reflects the latest recorded check.

Markdown

[![Verified on Appside](https://appside.build/mcp-servers/diogenes-eve-frontier/badge.svg)](https://appside.build/mcp-servers/diogenes-eve-frontier/)

HTML

<a href="https://appside.build/mcp-servers/diogenes-eve-frontier/"><img src="https://appside.build/mcp-servers/diogenes-eve-frontier/badge.svg" alt="Verified on Appside"></a>

Connect with Claude Code

claude mcp add --transport http diogenes-eve-frontier 'https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier'

Connect with Cursor

Paste into .cursor/mcp.json.

{
  "mcpServers": {
    "diogenes-eve-frontier": {
      "url": "https://diogenes-micro-gateway.corinth.workers.dev/mcp/eve-frontier"
    }
  }
}

Complete the provider’s authentication flow in your client. For API keys, follow the maintainer’s instructions; never place secrets in a public listing.

Tools (14)

  • inspect_eve_assembly_state
  • audit_eve_tribe_standings
  • generate_eve_assembly_move
  • compile_eve_gate_acl
  • simulate_eve_sui_ptb
  • verify_eve_zklogin_character
  • plan_eve_gate_route
  • optimize_eve_node_power
  • simulate_eve_capacitor_siege
  • monitor_eve_constellation_fuel
  • quote_eve_ssu_market
  • find_eve_ssu_arbitrage
  • analyze_eve_killmail_threats
  • prioritize_eve_turret_targets

Submitted to TensorBlock/awesome-mcp-servers (PR #4236) by stand-out-of-my-sun. Public submission attribution does not establish ownership. Appside independently checks connectivity.

Your agent can submit and claim this for you

{"name":"create_account","arguments":{"agent":"My assistant","purpose":"mcp-directory"}}

How we check servers

Each published entry passed a dated HTTPS Streamable HTTP check using the initialize-based MCP lifecycle (2024-11-05 through 2025-11-25): MCP initialize, followed by tools/list for open servers. For protected endpoints, a 401 response with an authentication challenge establishes reachability only. We never invoke tools. Failed checks stay in our source data and are excluded from the directory.

Checks are point-in-time observations, not continuous uptime monitoring. An authentication challenge does not prove tools are available. Appside does not endorse or audit listed servers. Review the maintainer’s permissions and policies before connecting.

What does the check verify?

We send an MCP initialize request over HTTPS. Open servers must return a valid tools/list response. Protected servers may qualify with an authentication challenge. A listing is not an endorsement or a security audit.

How can I update or remove a listing?

Sign in to a free Appside account, claim the listing with a token on its server or maintainer domain, then edit or remove it. You can also request removal at privacy@appside.build.

SEE IT YOURSELF

Build your store
before the first call.

Try the live demo ↗Explore Studio
LET’S TALK

Book a demo

Connect with Oded to arrange a walkthrough of Appside.

Contact Oded on LinkedIn ↗