io.competitortracker/mcp
REMOTE · MCP.COMPETITORTRACKER.IO · SCANNED SEP 22
Track competitors from your AI assistant: change feed, page snapshots, labels and alerts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 335 tokens (~335/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.competitortracker/mcp server?
io.competitortracker/mcp is a hosted endpoint at https://mcp.competitortracker.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.competitortracker.io
claude mcp add --transport http io-competitortracker-mcp 'https://mcp.competitortracker.io/mcp'
{
"mcpServers": {
"io-competitortracker-mcp": {
"url": "https://mcp.competitortracker.io/mcp"
}
}
} {
"servers": {
"io-competitortracker-mcp": {
"type": "http",
"url": "https://mcp.competitortracker.io/mcp"
}
}
} [mcp_servers.io-competitortracker-mcp] url = "https://mcp.competitortracker.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-competitortracker-mcp": {
"type": "remote",
"url": "https://mcp.competitortracker.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-competitortracker-mcp --url 'https://mcp.competitortracker.io/mcp' --transport streamable-http
mcp_servers:
io-competitortracker-mcp:
url: "https://mcp.competitortracker.io/mcp" {
"McpServers": {
"io-competitortracker-mcp": {
"Transport": "http",
"Url": "https://mcp.competitortracker.io/mcp"
}
}
} assistant mcp add io-competitortracker-mcp -t streamable-http -u 'https://mcp.competitortracker.io/mcp'
{
"mcpServers": {
"io-competitortracker-mcp": {
"type": "http",
"url": "https://mcp.competitortracker.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://mcp.competitortracker.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=competitortracker.io | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | faaf73b0d2a84d90e00b1aa51e37e7e |
| SANs: competitortracker.io, mcp.competitortracker.io, *.mcp.competitortracker.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.competitortracker.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| competitortracker.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.competitortracker.io/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.competitortracker.io/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.competitortracker.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.competitortracker.io |
| Authorisation server | https://auth.competitortracker.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.competitortracker.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.competitortracker.io/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
start_tracking_competitors Start tracking competitors for someone ~335
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | Company names or domains, in the order they matter to the person you are acting for, e.g. ['Notion', 'linear.app']. The first three we already track get the slots; everything else comes back in short… |
| sessionId | string | – | Your own id for the conversation this ask came from. It ties the claim link back to where it started and is never treated as a credential. Leave it out if you have none. |
No output schema declared.
No examples provided.
What is the io.competitortracker/mcp server?
io.competitortracker/mcp is listed in the public MCP registry as io.competitortracker/mcp. Track competitors from your AI assistant: change feed, page snapshots, labels and alerts. This page covers its hosted endpoint (https://mcp.competitortracker.io/mcp).
Is the io.competitortracker/mcp server safe to use?
io.competitortracker/mcp scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.competitortracker/mcp server expose?
io.competitortracker/mcp exposes 1 tool: start_tracking_competitors. Their descriptions and schemas cost roughly 335 tokens of context every time the server is loaded.
Does the io.competitortracker/mcp server require authentication?
Yes. io.competitortracker/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.competitortracker/mcp server still maintained?
io.competitortracker/mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.