Ext Ops Panel
Open dashboard
Comparison

Amazon ECS MCP Server vs io.github.mikemark78/agentmark

Amazon ECS MCP Server is an MCP server published by ecs-mcp.us-east-1.api.aws. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.mikemark78/agentmark is an MCP server published by mikemark78. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
MarketplaceAmazon ECS MCP Serverio.github.mikemark78/agentmark
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (PyPI): 1 289 880
Downloads/week (PyPI): 367 235
Not marked · First seen
Listed
Version: 0.4.0
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
Not marked · First seen
PyPI (MCP servers) Listed
Version: 1.7.0
Downloads/month (PyPI): 1 289 880
Downloads/week (PyPI): 367 235
Forks (GitHub): 67
Stars (GitHub): 365
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

Amazon ECS MCP Server vs io.github.mikemark78/agentmark
FactAmazon ECS MCP Serverio.github.mikemark78/agentmark
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)3650 (last published figure)
Forks (GitHub) (differs)670 (last published figure)
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (mcp-proxy-for-aws)Remote server (agentmarket.fly.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/aws/mcp-proxy-for-awsgithub.com/mikemark78/agentmark
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-20
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (44 h ago)

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

Amazon ECS MCP Server

In its own words, on Official MCP Registry:

AI-powered Amazon ECS workload management

io.github.mikemark78/agentmark

In its own words, on Official MCP Registry:

Sell unused AI subscription capacity as finished work. SOL/USDC escrow on Solana, 0% fees.

How to run each

Amazon ECS MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio amazon-ecs-mcp-server -- uvx mcp-proxy-for-aws "https://ecs-mcp.<YOUR_REGION>.api.aws/mcp" --profile default --region "<YOUR_REGION>"

io.github.mikemark78/agentmark As a remote MCP server

Claude Code
claude mcp add --transport http agentmark https://agentmarket.fly.dev/mcp

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

Only io.github.mikemark78/agentmark 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: Amazon ECS MCP Server · What it can do: io.github.mikemark78/agentmark · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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