Ripples Metrics

sh.ripplesPublished by ripples.shOfficial publisherv1.0.0Updated Oct 24, 2026

Analytics for founders: traffic, search, ad spend, revenue and retention per product.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Ripples Metrics is a remote MCP server that gives an assistant access to founder-focused analytics: traffic, search, ad spend, revenue and retention per product

What you can do
The manifest lists no tools, so capabilities come from the description only. It is presented as an analytics service for founders, covering traffic, search, ad spend, revenue and retention, broken down per product. An assistant connected to it would be expected to help review these metrics and compare products. No specific operations are documented.
When to use it
Useful for founders or small teams who want an assistant to look at product-level analytics — traffic, search performance, ad spend, revenue and retention — without switching dashboards. Only worth adding if you already use Ripples for this data.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. Authentication is OAuth and required, so you need a Ripples account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server requires OAuth access to your Ripples analytics account, which likely exposes business data such as revenue, ad spend and retention to the assistant and its model provider. No tools are listed, so what it can read or change cannot be verified from the manifest; review the granted scopes before connecting.

Installation

In SourceWeft

  1. Open Ripples Metrics in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/sh.ripples%2Fripples/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ripples-metrics": {
      "type": "http",
      "url": "https://mcp.ripples.sh/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 23, 2026

Score

67% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.