mcpbeat Sign in

Compete Competitive Intelligence MCP Server

by niyonzimabryan Your server? Claim it
local only

Compete Competitive Intelligence runs on your own machine — the client starts it, so there is no endpoint to ping. 31 installs a week from npm.

Typed access to monitored competitive changes, evidence, dossiers, research, and collection health.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 171 · avg 26 · -43% w/w
a month agotoday
31
Installs / week
npm · compete-mcp
—
Stars
on GitHub
—
Last commit
7 releases in 90 days
—
License
language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add compete -e 'COMPETE_API_KEY=<COMPETE_API_KEY>' -e 'COMPETE_URL=<COMPETE_URL>' -- npx -y compete-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "compete": {
      "command": "npx",
      "args": [
        "-y",
        "compete-mcp"
      ],
      "env": {
        "COMPETE_API_KEY": "<COMPETE_API_KEY>",
        "COMPETE_URL": "<COMPETE_URL>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.compete]
command = "npx"
args = ["-y", "compete-mcp"]
env = { COMPETE_API_KEY = "<COMPETE_API_KEY>", COMPETE_URL = "<COMPETE_URL>" }
.cursor/mcp.json
{
  "mcpServers": {
    "compete": {
      "command": "npx",
      "args": [
        "-y",
        "compete-mcp"
      ],
      "env": {
        "COMPETE_API_KEY": "<COMPETE_API_KEY>",
        "COMPETE_URL": "<COMPETE_URL>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "compete": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "compete-mcp"
      ],
      "env": {
        "COMPETE_API_KEY": "<COMPETE_API_KEY>",
        "COMPETE_URL": "<COMPETE_URL>"
      }
    }
  }
}

Put your own values in place of <COMPETE_API_KEY> (API key for the target Compete deployment), <COMPETE_URL> (Base URL of the target Compete deployment, including https://). The author’s registry entry marks them as required.

Optional settings from the registry entry, left out of the block above: COMPETE_REPO (Optional local repository path for privacy-bounded codebase focus summaries), COMPETE_TIMEOUT_MS (Optional bounded upstream request timeout in milliseconds).

Alternatives to Compete Competitive Intelligence

same job, measured the same way
Competiflow MCP
by nyku

Competitor monitoring for AI agents: track rival pricing, docs and changelog changes with evidence.

4 installs/wk local only
Signallabs MCP
by emresemercioglu

Competitive Intelligence MCP: generate AI battlecards, track competitors, monitor market signals.

27 installs/wk local only
U
UK Source Intelligence
by pages-uk-source-intelligence

Inspect GOV.UK guidance, check quotations, and monitor recorded HMRC changes. Free agent trial.

12 tools answering
Timps
by sandeeprdy1729

Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.

10 installs/wk local only
niubiagent Signal Intelligence
by niubiagent

Search and monitor source-backed AI agent ecosystem signals, briefings, deltas, and source health.

5 tools answering
VATFind
by vatfind

Find VAT numbers and EINs, resolve company identities, and monitor company-record changes.

answering
Shopify Change Intelligence
by contentforge-press

Monitor public Shopify stores: free snapshot, paid change intel, competitor reports via x402 USDC.

13 installs/wk 5 tools answering
Carrierscore
by carrierscore

FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.

8 tools answering

Compete Competitive Intelligence — questions

Answers built from our own checks of this server.

Why is there no uptime for Compete Competitive Intelligence?
Compete Competitive Intelligence runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package compete-mcp was installed 31 times last week.
Is Compete Competitive Intelligence still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Compete Competitive Intelligence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls compete-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Compete Competitive Intelligence?
The npm package compete-mcp was installed 31 times in the last week. Week over week that is -43%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.