Ecosystem Monitor

org.memoryapiPublished by memoryapi.orgOfficial publisherv1.0.0Updated Oct 24, 2026

Ecosystem monitoring: service status and x402 activity metrics

The publisher's own server: AI/ML Research Papers

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

A remote MCP server that gives an assistant read-only x402 payment activity stats and ecosystem intelligence for memoryapi.org services.

What you can do
Retrieve x402 paid API call activity from memoryapi.org nginx logs, including top endpoints by paid calls, unique payers and trend data. Look up x402 ecosystem intelligence from Agentic Market, covering services by category, counts, and which memoryapi.org services are listed.
When to use it
Useful when you want an assistant to report on x402 paid API usage or survey the x402 service landscape, for example to check which endpoints attract payers or where a service sits in the ecosystem.
Requirements
A remote streamable HTTP endpoint at monitor.memoryapi.org; no packages, environment variables, headers or authentication are declared. Network access to that endpoint is needed.
Before you install
The server is read-only and asks for no credentials, but its figures come from memoryapi.org logs and Agentic Market, so results reflect those third parties' data and may be incomplete or lag behind.

Installation

In SourceWeft

  1. Open Ecosystem Monitor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.memoryapi%2Fmonitor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ecosystem-monitor": {
      "type": "http",
      "url": "https://monitor.memoryapi.org/mcp"
    }
  }
}

Tools

2

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.

Parametershoursservice

get_x402_ecosystem

Get x402 ecosystem intelligence from Agentic Market. Returns services by category, counts, and which memoryapi.org services are listed.

Parameterssortcategory

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Memoryapi integrations