# io.github.Aggrometer/aggrometer (remote · aggrometer.com)

The gaming attention graph: Steam players, Twitch live viewers, aggro ratio, hype, history.

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `aggrometer.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/aggrometer-aggrometer/aggrometer.md), [page](https://verifymcp.io/servers/aggrometer-aggrometer/aggrometer)

## Channel facts

- Endpoint: `https://aggrometer.com/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-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 703 tokens (~87/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 40% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.Aggrometer/aggrometer MCP server?

io.github.Aggrometer/aggrometer is a hosted endpoint at https://aggrometer.com/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.

### Claude

```bash
claude mcp add --transport http aggrometer-aggrometer 'https://aggrometer.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "aggrometer-aggrometer": {
      "url": "https://aggrometer.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aggrometer-aggrometer": {
      "type": "http",
      "url": "https://aggrometer.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.aggrometer-aggrometer]
url = "https://aggrometer.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aggrometer-aggrometer": {
      "type": "remote",
      "url": "https://aggrometer.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aggrometer-aggrometer --url 'https://aggrometer.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aggrometer-aggrometer:
    url: "https://aggrometer.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "aggrometer-aggrometer": {
      "Transport": "http",
      "Url": "https://aggrometer.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add aggrometer-aggrometer -t streamable-http -u 'https://aggrometer.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "aggrometer-aggrometer": {
      "type": "http",
      "url": "https://aggrometer.com/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-09-20 (score 71, +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.

### 2026-09-18 (score 70, +1)

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

### 2026-09-16 (score 69, +1)

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

### 2026-09-14 (score 68, +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-09-12 (score 67, +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-09-10 (score 66, +1)

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

### 2026-09-08 (score 65, +1)

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

### 2026-09-07 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `get_summary` (~38 tokens)

Warehouse status: how many games are tracked, hours of history recorded, snapshot counts, and data freshness timestamps. Call this first to understand data coverage.

### `top_played` (~65 tokens)

Top 100 games by current Steam concurrent players (updated hourly). Optionally scoped to one Steam genre.

Input parameters:

- `genre` (string): Steam genre name, e.g. 'Action', 'RPG', 'Strategy' (exact match; see genre_rollup for the list)

### `top_watched` (~39 tokens)

Top 100 games by current live Twitch viewership (15-min updates). Optionally scoped to one Steam genre.

Input parameters:

- `genre` (string)

### `aggro_board` (~76 tokens)

Aggrometer's signature metric: aggro = live Twitch viewers / concurrent Steam players, same hour, per game (min 500 players). Above 1.0 means more people watch than play — spectacle games, watch-to-learn genres. A sudden aggro jump is an early attention signal.

Input parameters:

- `genre` (string)

### `genre_rollup` (~69 tokens)

Every Steam genre aggregated: game count, combined players, combined live viewers, genre-level aggro ratio, and combined hype (anticipation) of the genre's unreleased games. The whitespace signal: high players + low hype = an underserved genre; low players + high hype = a wave arriving.

### `hype_board` (~82 tokens)

Aggrometer Anticipation Index: top-wishlisted unreleased Steam games scored with pre-release Twitch attention and Wikipedia attention surges (score = wishlist-rank points + log-scaled live viewers + log-scaled pageview surge vs 30-day average). A relative index - compare games against each other; week-over-week change is the launch-anticipation signal.

### `game_detail` (~122 tokens)

Full profile of one game by Steam app id: hourly player history, Twitch viewer history, daily viewer-hours, price/discount history, top-seller rank appearances, clips-per-day virality, review counts and review-activity buckets back to launch, Wikipedia pageview history (monthly since 2018 + daily), developer news velocity, achievement-completion depth, and metadata (genres, developer, publisher). Use search_games first if you only know the name.

Input parameters:

- `app_id` (integer, required): Steam app id, e.g. 1623730 for Palworld

### `search_games` (~41 tokens)

Find games in the tracked catalog by name (substring match). Returns app ids for use with game_detail, plus current player counts.

Input parameters:

- `query` (string, required)

## Diagnostics

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

## Score history

- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 65
- 2026-09-08: 65
- 2026-09-07: 64
- 2026-09-06: 64
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36
- 2026-09-02: 36

## Common questions

### What is the io.github.Aggrometer/aggrometer MCP server?

io.github.Aggrometer/aggrometer is an MCP server listed in the public MCP registry as io.github.Aggrometer/aggrometer. The gaming attention graph: Steam players, Twitch live viewers, aggro ratio, hype, history. This page covers its hosted endpoint (https://aggrometer.com/mcp).

### Is the io.github.Aggrometer/aggrometer MCP server safe to use?

io.github.Aggrometer/aggrometer scores 71 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.github.Aggrometer/aggrometer MCP server expose?

io.github.Aggrometer/aggrometer exposes 8 tools: get_summary, top_played, top_watched, aggro_board, genre_rollup, and 3 more. Their descriptions and schemas cost roughly 532 tokens of context every time the server is loaded.

### Does the io.github.Aggrometer/aggrometer MCP server require authentication?

No. We connected to io.github.Aggrometer/aggrometer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.Aggrometer/aggrometer MCP server still maintained?

io.github.Aggrometer/aggrometer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://aggrometer.com/mcp
- Authorisation metadata: https://aggrometer.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/Aggrometer/aggrometer
- Website: https://aggrometer.com/
- Changelog RSS feed: https://verifymcp.io/servers/aggrometer-aggrometer/aggrometer.xml
- Changelog JSON feed: https://verifymcp.io/servers/aggrometer-aggrometer/aggrometer.json
- HTML version of this page: https://verifymcp.io/servers/aggrometer-aggrometer/aggrometer