io.github.Aggrometer/aggrometer
REMOTE · AGGROMETER.COM · SCANNED SEP 20
The gaming attention graph: Steam players, Twitch live viewers, aggro ratio, hype, history.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 703 tokens (~87/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · aggrometer.com
claude mcp add --transport http aggrometer-aggrometer 'https://aggrometer.com/mcp'
{
"mcpServers": {
"aggrometer-aggrometer": {
"url": "https://aggrometer.com/mcp"
}
}
} {
"servers": {
"aggrometer-aggrometer": {
"type": "http",
"url": "https://aggrometer.com/mcp"
}
}
} [mcp_servers.aggrometer-aggrometer] url = "https://aggrometer.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aggrometer-aggrometer": {
"type": "remote",
"url": "https://aggrometer.com/mcp",
"enabled": true
}
}
} openclaw mcp add aggrometer-aggrometer --url 'https://aggrometer.com/mcp' --transport streamable-http
mcp_servers:
aggrometer-aggrometer:
url: "https://aggrometer.com/mcp" {
"McpServers": {
"aggrometer-aggrometer": {
"Transport": "http",
"Url": "https://aggrometer.com/mcp"
}
}
} assistant mcp add aggrometer-aggrometer -t streamable-http -u 'https://aggrometer.com/mcp'
{
"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.
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.
- 20 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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 7 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 20 Sept 2026 · Probed https://aggrometer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aggrometer.com | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d6b830c2ec2bca9a139a822966c2c554 |
| SANs: aggrometer.com, www.aggrometer.com, *.www.aggrometer.com | ||||||
| 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 aggrometer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aggrometer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aggrometer.com/mcp | Verified | 200 | |
| http (plaintext) | http://aggrometer.com/mcp | HTTPS enforced | 301 | https://aggrometer.com/mcp |
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 →
aggro_board ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| genre | string | – | – |
No output schema declared.
No examples provided.
game_detail ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | integer | yes | Steam app id, e.g. 1623730 for Palworld |
No output schema declared.
No examples provided.
genre_rollup ~69
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_summary ~38
Warehouse status: how many games are tracked, hours of history recorded, snapshot counts, and data freshness timestamps. Call this first to understand data coverage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hype_board ~82
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_games ~41
Find games in the tracked catalog by name (substring match). Returns app ids for use with game_detail, plus current player counts.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
top_played ~65
Top 100 games by current Steam concurrent players (updated hourly). Optionally scoped to one Steam genre.
| Name | Type | Req | Description |
|---|---|---|---|
| genre | string | – | Steam genre name, e.g. 'Action', 'RPG', 'Strategy' (exact match; see genre_rollup for the list) |
No output schema declared.
No examples provided.
top_watched ~39
Top 100 games by current live Twitch viewership (15-min updates). Optionally scoped to one Steam genre.
| Name | Type | Req | Description |
|---|---|---|---|
| genre | string | – | – |
No output schema declared.
No examples provided.
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.