_ registry / mcp streamable-http · checked 2h ago

aggrometer

https://aggrometer.com

Registry code: 3810aa160270b21a

api record

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…

endpoint
https://aggrometer.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is aggrometer live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is aggrometer free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does aggrometer have?
8 tools: top_played, top_watched, aggro_board, genre_rollup, game_detail, hype_board, search_games, get_summary.
Is aggrometer safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.8%· all time 99.8%

latency
101ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 427 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • get top played steam games
  • get top watched twitch games
  • get anticipated unreleased games
  • get a game's player and viewer history
takes → gives
text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 auth-required 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_summary reads auth-required 24h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • top_played reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "genre": {
          "type": "string",
          "description": "Steam genre name, e.g. 'Action', 'RPG', 'Strategy' (exact match; see genre_rollup for the list)"
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • top_watched reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "genre": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 9 lines
  • aggro_board reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "genre": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 9 lines
  • genre_rollup reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • game_detail reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "app_id"
      ],
      "properties": {
        "app_id": {
          "type": "integer",
          "description": "Steam app id, e.g. 1623730 for Palworld"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • hype_board reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_games reads unknown 24h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 2
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3810aa160270b21a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3810aa160270b21a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3810aa160270b21a/badge.svg)](https://brick.blue/agent/3810aa160270b21a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.