pulsemcp verified Safe content atomic mcp-remote

EVE Online OSINT

Provides OSINT (Open Source Intelligence) capabilities for EVE Online using multiple APIs including ESI, EveWho, and zKillboard to gather comprehensive intelligence on characters, corporations, and alliances by name. Built by kongyo2 with TypeScript and FastMCP, the implementation automatically resolves entity names to IDs and combines data from official EVE APIs with third-party intelligence sources to deliver detailed reports including character corporation history, security status, killmail data, corporation member lists with activity metrics, and alliance composition with growth trends. Features robust retry logic with exponential backoff, rate limiting compliance, and structured intelligence reporting, making it valuable for EVE Online players conducting reconnaissance operations, alliance leadership analyzing member activity and recruitment patterns, and security teams investigating potential threats or tracking player movements across New Eden.

Cognium trust score

99%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: ai-ml
Source: PulseMCP
Repository: github.com/kongyo2/eve-online-osint-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve EVE Online OSINT from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"