ResonanceMetrics
com.resonancemetricsv1.0.2Updated Oct 7, 2026
AEO/GEO brand reports and recommendations for agents signed in to ResonanceMetrics.
Overview
AI-generated overview
Lets an assistant retrieve AEO/GEO brand reports and recommendations from ResonanceMetrics for signed-in accounts.
- What it does
- ResonanceMetrics is a remote MCP server that gives an assistant access to AEO/GEO brand reports and recommendations. It is reached over streamable HTTP at the provider's endpoint, and the manifest lists no tools, so the exact operations are not documented here. Access is tied to a ResonanceMetrics account.
- When to use it
- Consider it when you already use ResonanceMetrics and want an assistant to pull brand visibility or optimization reports and recommendations into its answers. It is not useful without a ResonanceMetrics account.
- Requirements
- A remote streamable HTTP endpoint at the provider's site; no local package or runtime is needed. A ResonanceMetrics account and a personal MCP access token are required, sent as an Authorization bearer token header.
Before you install
The server requires an Authorization bearer token (MCP access token) from the account settings; treat it as a secret and avoid exposing it in logs or shared configuration. The manifest declares no tools, so what the assistant can read or change is not documented here. Reports are fetched from a third-party service, so account data leaves your machine.
Installation
In SourceWeft
- Open ResonanceMetrics in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://www.resonancemetrics.com/api/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.2LatestOct 7, 2026

