competitor-tracker
https://mcp.competitortracker.io
Registry code: 64bb8b133c9bf6de
Track competitors from your AI assistant: change feed, page snapshots, labels and alerts.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.competitortracker.io/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is competitor-tracker live?
- Yes — it answered the hub's last check (checked 33m ago). It answered 99% of checks over the last 30 days.
- Is competitor-tracker free to use?
- Not measured yet.
- What tools does competitor-tracker have?
- 1 tool: start_tracking_competitors.
- Is competitor-tracker safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.4%· all time 99.4%
last good check
of 1 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- set up competitor tracking
- get alerts on competitor website changes
- takes → gives
- text → data
- tools
- 1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
start_tracking_competitors changes data unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "companies" ], "properties": { "companies": { "type": "array", "items": { "type": "string", "maxLength": 200, "minLength": 1 }, "maxItems": 20, "minItems": 1, "description": "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 shortfalls." }, "sessionId": { "type": "string", "maxLength": 200, "minLength": 1, "description": "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." } } }arguments 26 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id64bb8b133c9bf6de.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/64bb8b133c9bf6de/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/64bb8b133c9bf6de?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.