Ext Ops Panel
Open dashboard
Comparison

three.ws Developer Tools vs io.github.tedfytw1209/mcp-server-EVEfleet

three.ws Developer Tools is a plugin bundle for AI coding tools published by nirholas. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.tedfytw1209/mcp-server-EVEfleet is an MCP server published by tedfytw1209. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacethree.ws Developer Toolsio.github.tedfytw1209/mcp-server-EVEfleet
Community marketplace nirholas/three.ws Listed
Version: 1.0.0
Forks (GitHub): 68
Stars (GitHub): 249
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (PyPI): 61
Downloads/week (PyPI): 27
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

three.ws Developer Tools vs io.github.tedfytw1209/mcp-server-EVEfleet
Factthree.ws Developer Toolsio.github.tedfytw1209/mcp-server-EVEfleet
Marketplaces that list it11
Stars (GitHub) (differs)249 (better)1 (worse)
Forks (GitHub) (differs)68 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@three-ws/mcp-server)On your machine (mcp-server-evefleet)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 01, secrets among them: 1
Parts of the bundle (differs)4Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/nirholas/three.wsgithub.com/tedfytw1209/mcp-server-evefleet
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

three.ws Developer Tools

In its own words, on Community GitHub marketplaces:

Developer tools for three.ws — scaffold agents, configure MCP servers, and get runnable code examples for paid MCP tools.

io.github.tedfytw1209/mcp-server-EVEfleet

In its own words, on Official MCP Registry:

An MCP server that provides tools for EVE Online players to manage their fleets

How to run each

three.ws Developer Tools As a Claude Code plugin

Claude Code
/plugin marketplace add nirholas/three.ws
/plugin install three-ws-developer@three-ws

io.github.tedfytw1209/mcp-server-EVEfleet As a local MCP server: PyPI package

Claude Code
claude mcp add --env "YOUR_API_KEY=<YOUR_YOUR_API_KEY>" --transport stdio mcp-server-evefleet -- uvx mcp-server-evefleet

Requires: YOUR_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only three.ws Developer Tools asks for

  • MCP_SVM_PAYMENT_ADDRESS

Only io.github.tedfytw1209/mcp-server-EVEfleet asks for

  • YOUR_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: three.ws Developer Tools · What it can do: io.github.tedfytw1209/mcp-server-EVEfleet · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built