# Competitor Tracking Trends MCP (remote · competitor-tracking.api.trendsmcp.ai)

Brand and competitor trend volume over time, with growth signals. Free key at trendsmcp.ai

- Trust score: 46/100 (low)
- Change this week: +14
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `competitor-tracking.api.trendsmcp.ai`: 46/100 (this document), [markdown](https://verifymcp.io/servers/ai-trendsmcp-competitor-tracking/competitor-tracking.md), [page](https://verifymcp.io/servers/ai-trendsmcp-competitor-tracking/competitor-tracking)

## Channel facts

- Endpoint: `https://competitor-tracking.api.trendsmcp.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Instruction-quality not yet verified: the AI judgement didn't run.
  - Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for.
  - Nothing to assess: this server has no tools to check for usage examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 0/100
  - Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-trendsmcp-competitor-tracking https://competitor-tracking.api.trendsmcp.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-trendsmcp-competitor-tracking]
url = "https://competitor-tracking.api.trendsmcp.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-trendsmcp-competitor-tracking": {
      "type": "remote",
      "url": "https://competitor-tracking.api.trendsmcp.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-trendsmcp-competitor-tracking --url https://competitor-tracking.api.trendsmcp.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-trendsmcp-competitor-tracking:
    url: "https://competitor-tracking.api.trendsmcp.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-trendsmcp-competitor-tracking": {
      "type": "http",
      "url": "https://competitor-tracking.api.trendsmcp.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 44, +11)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 33, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 33, +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.

### 2026-07-27 (score 32, +1)

- [functional regression] Tool coverage: unverified → fail
- [functional improvement] Stability: unverified → 0.03

### 2026-07-26 (score 31)

First indexed and scored.

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-trendsmcp-competitor-tracking/competitor-tracking#diagnostics

## Score history

- 2026-08-03: 46
- 2026-08-02: 45
- 2026-08-01: 45
- 2026-07-31: 44
- 2026-07-30: 33
- 2026-07-29: 33
- 2026-07-28: 32
- 2026-07-27: 32
- 2026-07-26: 31

## Links

- Remote endpoint: https://competitor-tracking.api.trendsmcp.ai/mcp
- Authorisation metadata: https://competitor-tracking.api.trendsmcp.ai/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/trendsmcp/Trends-MCP
- Website: https://trendsmcp.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-trendsmcp-competitor-tracking/competitor-tracking/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-trendsmcp-competitor-tracking/competitor-tracking/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-trendsmcp-competitor-tracking/competitor-tracking
