Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
Rivalize is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
2
downloads a day
local
runs on your machine
474
downloads in 30d
What it does
Competitive intelligence for agents: competitor teardowns, pricing, ads, reviews and momentum.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'RIVALIZE_API_KEY=${RIVALIZE_API_KEY}' --transport stdio rivalize-mcp '--' npx -y @rivalize/mcp
# 2 — ask your agent for something these tools do
# list_universe_companies, get_universe_company, teardown_competitor and 11 more
It needs RIVALIZE_API_KEY: this reads it from your environment, so export it first.
Rivalize costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
RIAll 1 server
rivalize1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Rivalize as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads RIVALIZE_API_KEY (Your Rivalize API key (rk_live_...). Create one at rivalize.ai under Settings, API Keys. Free plans get rate-limited reads) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx RIVALIZE_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'RIVALIZE_API_KEY=${RIVALIZE_API_KEY}' --transport stdio rivalize-mcp '--' npx -y @rivalize/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: RIVALIZE_API_KEY — Your Rivalize API key (rk_live_...). Create one at rivalize.ai under Settings, API Keys. Free plans get rate-limited reads.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List companies from the Rivalize universe — the cross-customer competitive-intelligence dataset (not your own tracked competitors; for those use list_competitors). Search by keyword, filter by category or by which intelligence layer is populated, and paginate. Args: - q (string, optional):…
No parameter schema on file.
Get the universe profile for one company by domain, including every populated intelligence layer (identity, pricing, features, ads, social, reviews, funding/hiring, rankings, signals, momentum). Args: - domain (string, required): the company domain or any URL on it (e.g. "linear.app" or…
No parameter schema on file.
Produce a full strategy teardown of one competitor by domain — their positioning/hooks, pricing, ads (the creatives they are running), social presence, reviews, hiring, momentum, plus weaknesses to attack. Returns a ready-to-read Markdown teardown, not raw JSON. This is the one-call competitor…
No parameter schema on file.
List the projects in YOUR Rivalize account. A project is one of your products and the competitors tracked against it. Args: none. Returns JSON: { data: Project[] }. Each Project includes id, name, url, competitor_count, last_refreshed_at, created_at. Use the returned project id with…
No parameter schema on file.
List the competitive-intelligence reports in YOUR Rivalize account, newest first. Reading is free; this never generates a report. Args: - project_id (string, optional): only this project's reports. Call list_projects first for the id. - limit (number, optional): page size 1-100 (default 20)…
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Get the latest stored intelligence for one tracked competitor. Args: - competitor_id (string, required): the competitor UUID (from list_competitors) Returns JSON: { data: { competitor_name, momentum_score, intelligence, latest_snapshot, source, source_report_id, source_report_date, report } }.…
No parameter schema on file.
Get the cited sales battlecard for one tracked competitor — Why We Win, Their Weaknesses, Objection Handlers, Discovery Questions. Every claim carries citations resolving to the collected source; claims that could not be cited were WITHHELD, not asserted. Args: - competitor_id (string,…
No parameter schema on file.
Get a receipt-linked timeline of competitor activity across Pricing, Product, People, Funding, and Content/Social lanes. Args: - project_id (string, required): the project's UUID. Call list_projects first for the id. - days ("30" | "90" | "180", optional): history window, default 90 -…
No parameter schema on file.
Get the current or stored weekly competitor positions on activity × strategic importance. Args: - project_id (string, required): the project's UUID. Call list_projects first for the id. - week (YYYY-MM-DD, optional): a stored ISO week; omit for current positions. The json format lists stored…
No parameter schema on file.
How current your Rivalize data is for one project: the date of its latest report, and for EACH tracked competitor the date Rivalize last actually observed it and how. Reading is free; this never fetches anything. Args: - project_id (string, required): the project's UUID. Call list_projects…
No parameter schema on file.
The sources behind the facts for ONE subject: your own product (omit competitor_id) or one tracked competitor. Taken from the latest readable report in the project that analysed the subject, as the report serves it: claims the report withholds as unverified are withheld here too, and a figure the…
No parameter schema on file.
Add one or more competitor URLs to a project in your account. This is the two-way write half of the data layer: adding a competitor Rivalize has not seen before ALSO queues a crawl of that company across 8 intelligence layers, which adds it to the Rivalize universe of tracked companies. Args: -…
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Rivalize or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 0.3.2 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest6b77dc016c2016e3b1fafe1b816326af096efbc45af8654929a6820d4c4d92fe
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (14 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
1 of the 14 recovered tools are registered only when !allowWrites is false (dist/tools.js:986) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 13.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
13 tools are registered unconditionally · 1 more only when !allowWrites is false (dist/tools.js:986) — typically when a key or option is configured. All 14 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_universe_companies | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_universe_company | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| teardown_competitor | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_projects | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_reports | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_report | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_competitors | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_competitor_intelligence | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_battlecard | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_strategic_timeline | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_competitive_landscape | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_freshness | untrusted-input | untrusted-input: keyword "crawl", declares openWorldHint: true (interacts with entities outside the server) |
| get_evidence | untrusted-input | untrusted-input: keyword "web_search", declares openWorldHint: true (interacts with entities outside the server) |
| add_competitor conditional | untrusted-inputexternal-sink | untrusted-input: keyword "crawl"; external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest6b77dc016c2016e3
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.2. Pin a release below and the command asks for exactly that one.
0.3.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Rivalize can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.