Ext Ops Panel
Open dashboard
Comparison

Infrawise vs Aether-X Port Delay Intelligence

Infrawise is an MCP server published by Sidd27. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). Aether-X Port Delay Intelligence is an MCP server published by belegante-byte. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceInfrawiseAether-X Port Delay Intelligence
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (npm): 1 026
Downloads/week (npm): 100
Forks (GitHub): 5
Stars (GitHub): 22
Not marked · First seen
Listed
Version: 0.4.4
Downloads/month (PyPI): 967
Downloads/week (PyPI): 84
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.0.0
Downloads/month (npm): 1 026
Downloads/week (npm): 100
Forks (GitHub): 5
Stars (GitHub): 22
Not marked · First seen
Not listed

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

Infrawise vs Aether-X Port Delay Intelligence
FactInfrawiseAether-X Port Delay Intelligence
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)22 (better)0 (worse)
Forks (GitHub) (differs)5 (better)0 (worse)
Last release (differs)2026-10-21Not published
Where it runs (differs)On your machine (infrawise)Remote server (aetherx.aether-grid.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/sidd27/infrawisegithub.com/belegante-byte/aetherx-oracle-engine
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-13

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

Infrawise

In its own words, on Official MCP Registry:

Live AWS, database & Kafka infrastructure context for AI coding assistants via MCP.

Aether-X Port Delay Intelligence

In its own words, on Official MCP Registry:

Port delay exposure with p50/p90 confidence intervals, demurrage impact and a free public feed.

How to run each

Infrawise As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio infrawise -- npx -y infrawise

Aether-X Port Delay Intelligence As a remote MCP server

Claude Code
claude mcp add --transport http aetherx-mcp https://aetherx.aether-grid.io/mcp

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

Only Aether-X Port Delay Intelligence has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Infrawise · What it can do: Aether-X Port Delay Intelligence · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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