mcpbeat Sign in

Ecosystem Monitor MCP Server

answering

Ecosystem Monitor is answering right now. Last checked 10 min ago. It exposes 2 tools.

Ecosystem monitoring: service status and x402 activity metrics

Uptime history 91 days of history · worst day 96%
91 days agonow
98.9%
Uptime 24h
90 of 91 checks
2
Tools
read from the server
467 ms
Response time
average over 24h
open, no key
Access
streamable-http

Ecosystem Monitor missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add monitor --transport http https://monitor.memoryapi.org/mcp
Settings → Connectors → Add custom connector, then paste this address
https://monitor.memoryapi.org/mcp
~/.codex/config.toml
[mcp_servers.monitor]
url = "https://monitor.memoryapi.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "monitor": {
      "url": "https://monitor.memoryapi.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "monitor": {
      "type": "http",
      "url": "https://monitor.memoryapi.org/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

x402
get_x402_activity
Get x402 paid API call activity stats from memoryapi.org nginx logs. Returns top endpoints by paid calls, unique payers, and trend data.
get_x402_ecosystem
Get x402 ecosystem intelligence from Agentic Market. Returns services by category, counts, and which memoryapi.org services are listed.

Endpoints

URLTransportStateLatencyChecked
https://monitor.memoryapi.org/mcp streamable-http answering 655 ms 10 min ago

Alternatives to Ecosystem Monitor

same job, measured the same way
vibeMK
by chexma

Query and configure CheckMK monitoring: hosts, services, rules, downtimes, metrics

115 installs/wk local only
Withings Health Data
by akutishevsky

MCP server for Withings health data — sleep, activity, heart, and body metrics.

answering
Xitoring
by xitoring

Connect AI assistants to Xitoring monitoring: servers, uptime, incidents, metrics, SSL, and alerts.

answering
Hyperping
by hyperping

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

69 tools answering
Ros MCP
by husain-zaidi

MCP for ROS 2 monitoring, debugging, and managing nodes, topics, services, and TF2 frames.

33 installs/wk local only
Riveter
by codywatters

MCP server for Riveter's enrichment, scraping, and monitoring API

742 installs/wk answering
Zabbix MCP
by mhajder

MCP server for Zabbix monitoring and automation

423 installs/wk local only
Kafka And Postgres Monitoring Stack
by getvda

Kafka and Postgres Monitoring Stack

2 tools answering

Ecosystem Monitor — questions

Answers built from our own checks of this server.

What can Ecosystem Monitor do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_x402_activity, get_x402_ecosystem. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Ecosystem Monitor working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 467 ms. The bar chart above shows every period we have measured.
How do I connect Ecosystem Monitor?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Ecosystem Monitor need an API key?
No. Ecosystem Monitor completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Ecosystem Monitor?
It answers our handshake in 467 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.