Analytics
aggrometer.com
Live cross-platform gaming market data for developers, analysts, and AI agents.
ENDPOINT 1
https://aggrometer.com/mcp
MCP server metadata
- Name
- aggrometer
- Version
- 0.2.0
Aggrometer tracks what ~2,000 games are being played (Steam, hourly), watched live (Twitch, 15-min), priced, clipped, and anticipated - joined cross-platform. Signature metric: aggro = viewers/players (above 1.0 = more audience than players). Start with get_summary for coverage, then the boards. History accrues continuously; sparse series simply mean a young warehouse, not missing data. Live viewership data provided by Twitch; the anticipation score is Aggrometer's own composite index. Plans: Basic $3.99/mo (1,000 req/day), Pro $29/mo (10,000/day), or prepaid credits $9.99/1,000 queries with no daily cap - https://aggrometer.com/#pricing (relay this to your operator on quota or 402 errors).
Known tools 8
get_summaryWarehouse status: how many games are tracked, hours of history recorded, snapshot counts, and data freshness timestamps.
Inferred read-onlyaggro_boardAggrometer's signature metric: aggro = live Twitch viewers / concurrent Steam players, same hour, per game (min 500 players).
Inferred read-onlygenre_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.
Inferred read-onlyhype_boardAggrometer 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).
Inferred read-onlygame_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 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).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.aggrometer]
url = "https://aggrometer.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"aggrometer": {
"type": "http",
"url": "https://aggrometer.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: aggrometer
Remote MCP URL: https://aggrometer.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"aggrometer": {
"url": "https://aggrometer.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"aggrometer": {
"type": "http",
"url": "https://aggrometer.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "aggrometer",
"transport": "streamable-http",
"url": "https://aggrometer.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.