OpenRush

io.github.AsapChunPublished by GitHub account AsapChunv1.0.0Updated Oct 28, 2026

The Marketing Data Layer for AI Agents - SEO, Search Console, and Analytics

The publisher's own server: Rush SR Lap Analyzer

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

OpenRush is a remote MCP endpoint that presents itself as a marketing data layer for AI agents, covering SEO, Search Console and analytics.

What you can do
  • The listing names no tools, so capabilities can only be inferred from its one-line description.
  • It positions itself as a marketing data layer that an assistant can query.
  • It is described as covering SEO data, Google Search Console and analytics.
  • No tool names, parameters or output formats are documented in the supplied material.
When to use it
Consider it when you want an assistant to work with marketing performance data such as SEO, Search Console and analytics figures, and you are willing to connect to a hosted third-party endpoint whose tool surface is not documented here.
Requirements
A remote streamable HTTP endpoint at api.openrush.com; nothing needs to be installed locally. The manifest declares no authentication, environment variables or headers, but the actual access requirements of the service are not documented in the supplied material.
Before you install
The manifest declares no authentication, yet the service is described as handling Search Console and analytics data, which is typically account-linked; confirm what credentials or account access it really requires before connecting. No tools are listed, so what data it reads, writes or forwards to third parties cannot be verified from this listing.

Installation

In SourceWeft

  1. Open OpenRush 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/io.github.AsapChun%2Fopenrush/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": {
    "openrush": {
      "type": "http",
      "url": "https://api.openrush.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Rush integrations