Competitor Tracker & Co. MCP server

Which servers in the official MCP registry are Competitor Tracker & Co.'s own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to Competitor Tracker & Co.

Whose server it is

Registry nameio.competitortracker/mcpverified in the MCP registry

The registry name sits under competitortracker.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19

Stateanswerschecked 2026-10-19
Tools1
Server calls itselfcompetitor-tracker
Server version1.0.0
Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 466 ms.

Measured dailydaily checks: 1, the first on 2026-10-19

Answeredmeasuring1 of the 7 daily checks it takes to print a share
Median first answer208 ms
Space in an agent's context≈ 464 tokensthe definitions of all its tools (1), which an agent carries on every turn
Tool definitionsA · 100 of 100

Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work.

Tools it offers1 tools · read 2026-10-19

start_tracking_competitors
Set someone up with competitor tracking before they have an account, and hand them a link to take it over. Name the companies they care about, by name or by domain. We match them against the companies we already track and the first three…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "competitortracker": {
      "type": "http",
      "url": "https://mcp.competitortracker.io/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.