aggrometer MCP server
io.github.Aggrometer/aggrometerAggrometerstreamable-httpv1.0.1Scanned
The gaming attention graph: Steam players, Twitch live viewers, aggro ratio, hype, history.
8 tools: 6 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the aggrometer MCP server can do
The aggrometer MCP server is published by the GitHub account Aggrometer. It has 8 tools. It can create or change data (6 tools: top_played, top_watched, aggro_board, genre_rollup and 2 more), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 6Claude Code: ask
aggro_boardAggrometer's signature metric: aggro = live Twitch viewers / concurrent Steam players, same hour, per game (min 500 players).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
game_detailFull 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 viral…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
genre_rollupEvery Steam genre aggregated: game count, combined players, combined live viewers, genre-level aggro ratio, and combined hype (anticipation) of the genre's unreleased games.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_boardAggrometer Anticipation Index: top-wishlisted unreleased Steam games scored with pre-release Twitch attention and Wikipedia attention surges (score = wishlist-rank points + log-sca…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
top_playedTop 100 games by current Steam concurrent players (updated hourly).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Top 100 games by current Steam concurrent players (updated hourly). Optionally scoped to one Steam genre.
top_watchedTop 100 games by current live Twitch viewership (15-min updates).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Top 100 games by current live Twitch viewership (15-min updates). Optionally scoped to one Steam genre.
Only reads 2Show 2 read-only tools
get_summaryWarehouse status: how many games are tracked, hours of history recorded, snapshot counts, and data freshness timestamps.No findings
Why it is in this group
- The name "get_summary" says "get": a word for reading.
Description, as the server wrote it Warehouse status: how many games are tracked, hours of history recorded, snapshot counts, and data freshness timestamps. Call this first to understand data coverage.
search_gamesFind games in the tracked catalog by name (substring match).No findings
Why it is in this group
- The name "search_games" says "search": a word for reading.
Description, as the server wrote it Find games in the tracked catalog by name (substring match). Returns app ids for use with game_detail, plus current player counts.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:56 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://aggrometer.com/mcp: tools/list returned 8 tools to an anonymous client, including top_played (write), top_watched (write), aggro_board (write), genre_rollup (write), hype_board (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http aggrometer https://aggrometer.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http aggrometer https://aggrometer.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__aggrometer__get_summary",
"mcp__aggrometer__search_games"
],
"ask": [
"mcp__aggrometer__top_played",
"mcp__aggrometer__top_watched",
"mcp__aggrometer__aggro_board",
"mcp__aggrometer__genre_rollup",
"mcp__aggrometer__hype_board",
"mcp__aggrometer__game_detail"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as aggrometer. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Aggrometer/aggrometer/verify?hash=5056470dc2e02448de0842f72ebca825fec668cc57eebaa8083c26af8a23220f" | jq -e '.changed == false'Pinned hash 5056470dc2e0, from Nov 15, 2026, 16:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Aggrometer/aggrometer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Aggrometer/aggrometer)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:14 UTC.
aggrometer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the aggrometer MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the aggrometer MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the aggrometer MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the aggrometer MCP server have?
- 8 tools: 6 write, 2 read. top_played, top_watched, aggro_board, genre_rollup, hype_board, game_detail, get_summary and search_games.
Does the aggrometer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the aggrometer MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the aggrometer MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.