Skip to content

io.competitortracker/mcp

by competitortracker.io · remote · no sign-in to list tools · v1.0.0 · published by io.competitortracker

Track competitors from your AI assistant: change feed, page snapshots, labels and alerts.

Changes · 1
CompareRegistry entry

1 tool: 1 change things.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http competitortracker https://mcp.competitortracker.io/mcp

Findings

Matches of fixed checks, with the text they matched.

1 info
  • Infostart_tracking_competitors

    The input schema at properties.sessionId.description mentions "credential".

    Matched text

    inputSchema.properties.sessionId.description: "...re it started and is never treated as a credential. Leave it out if you have none."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Changes things 1Claude Code: ask
  • start_tracking_competitorsSet someone up with competitor tracking before they have an account, and hand them a link to take it over.1 finding

    Why it is in this group

    • The name "start_tracking_competitors" says "start": a word for a change.

    Findings

    • Info

      The input schema at properties.sessionId.description mentions "credential".

      Matched text

      inputSchema.properties.sessionId.description: "...re it started and is never treated as a credential. Leave it out if you have none."

      What this check looks for
    Description, as the server wrote it
    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 you list go on file, with their change history readable straight away. We do not fetch an address you supply: a company we do not track yet comes back in `shortfalls`, which is not a failure — it is something the person can add themselves once they have claimed. Call this ONCE per person, with every company you know about. If more come up later, use `add_tracked_competitors` to fill the remaining slots on the same organization rather than calling this again — a second call here starts a second organization with a second link, and the person ends up with two things to claim instead of one. Nothing is charged to anyone, no email is sent and the organization is removed after four days unless someone claims it. The claim link comes back in the response and travels no further, so pass it on and tell them what went on file and what did not.

    Annotations the server declares

    • title: Start tracking competitors for someone
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http competitortracker https://mcp.competitortracker.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__competitortracker__start_tracking_competitors"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as competitortracker. Review it before you use it.