ResonanceMetrics MCP Server

by resonancemetrics Your server? Claim it

answering

ResonanceMetrics is answering right now. Last checked 8 min ago.

AEO/GEO brand reports and recommendations for agents signed in to ResonanceMetrics.

Uptime history 4 days of history · worst day 97%

4 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

115 ms

Response time

average over 24h

authentication required

Access

streamable-http

ResonanceMetrics does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://www.resonancemetrics.com/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://www.resonancemetrics.com/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://www.resonancemetrics.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://www.resonancemetrics.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://www.resonancemetrics.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://www.resonancemetrics.com/api/mcp	streamable-http	needs auth	134 ms	8 min ago

Alternatives to ResonanceMetrics

same job, measured the same way

LLM Pulse

by llm-pulse

AI visibility analytics for brand mentions, citations, sentiment, and GEO reports

answering

X402 Ads MCP

by forgemeshlabs

x402 ad recommendations, intent analytics, and machine-commerce demand reports.

414 installs/wk local only

Huntress

by wyre-technology

MCP server for Huntress — accounts, organizations, agents, incidents, and reports.

local only

Huntress

by wyre-ai

MCP server for Huntress — accounts, organizations, agents, incidents, and reports.

local only

Shopify Multi Store

by alex-brecher

Connect AI agents to multiple Shopify Admin stores for reports, comparisons, and guarded updates.

142 installs/wk local only

TMTB Marketing AI Platform

by tmtb

AI marketing skills for e-commerce brands: reports, campaign management, and creative generation.

answering

TestChimp

by testchimp

QA platform for agents: coverage signals, in-repo test plans, verified tests and release governance.

1 330 installs/wk answering

Decaframe

by decaframe

Presentations, slides, reports and one-pagers your agent designs and you edit. Exports to one file.

67 installs/wk local only

ResonanceMetrics — questions

Answers built from our own checks of this server.

Why is there no tool list for ResonanceMetrics?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is ResonanceMetrics working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 115 ms. The bar chart above shows every period we have measured.

How do I connect ResonanceMetrics?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does ResonanceMetrics need an API key?

Yes. Every time we knock, ResonanceMetrics answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is ResonanceMetrics?

It answers our handshake in 115 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.