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

needmoar.games

https://needmoar.games

Registry code: 01535c3d16a85900

api record

needmoar.games ranks Steam games by how much players like them, learned from head-to-head duels: each player pits games from their own library against each other, and every game's score is the share of a typical library it beats (its "beats-%", 0-100). This is a taste/preference consensus, not a review-score aggregator.

Use this server to answer, with citable data:

endpoint
https://needmoar.games/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 needmoar.games live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is needmoar.games free to use?
Yes — the hub reached it with no key and no payment.
What tools does needmoar.games have?
3 tools: game_detail, search_games, versus.
Is needmoar.games 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
98.8%

90 days 98.7%· all time 98.7%

latency
235ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 305 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· HTTP 503
  • degraded → live
_ what it is for
used for
  • compare which of two games players prefer
  • check how well liked a game is
  • find games similar to a game
takes → gives
text → data
tools
3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • game_detail reads unknown 19h ago

    The community consensus for one game on needmoar.games: how liked it is (the share of a typical library it beats), its tier and rank, the full distribution of opinions, and the games players who like it also like or dislike — useful for "how popular / well-liked is X?" and "games similar to X". Also, in the players' own words, what they liked about it and what kept them from ranking it higher (short tags with counts), once enough players said so. Pass a Steam appid — resolve names with search_games first. The response links to the game's page you can cite.

    mcp-tool

    {
      "type": "object",
      "required": [
        "appid"
      ],
      "properties": {
        "appid": {
          "type": "integer",
          "description": "Steam appid of the game (resolve names with search_games)."
        }
      }
    }
    arguments 12 lines
  • search_games reads unknown 19h ago

    Resolve one or more game names to their Steam appids on needmoar.games. Call this first to turn a title like "Hollow Knight" into the numeric appid the versus and game_detail tools need. Accepts several names at once — pass every game the user mentioned in a single call and match each to its result.

    mcp-tool

    {
      "type": "object",
      "required": [
        "queries"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "description": "Max matches to return per name (1-10, default 5)."
        },
        "queries": {
          "type": "array",
          "items": {
            "type": "string",
            "description": "A game name to resolve, e.g. \"Hollow Knight\"."
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "Game names to look up. Pass every title the user mentioned at once."
        }
      }
    }
    arguments 23 lines
  • versus reads unknown 19h ago

    Head-to-head verdict for two games on needmoar.games: which one players like more, each game's community score (the share of a library it beats) and rank, and the full distribution of opinions on both. Use this to answer "do people prefer A or B?". Pass Steam appids — resolve names with search_games first. The response links to the matching /vs page you can cite.

    mcp-tool

    {
      "type": "object",
      "required": [
        "appid_a",
        "appid_b"
      ],
      "properties": {
        "appid_a": {
          "type": "integer",
          "description": "Steam appid of the first game (resolve names with search_games)."
        },
        "appid_b": {
          "type": "integer",
          "description": "Steam appid of the second game."
        }
      }
    }
    arguments 17 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 01535c3d16a85900.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/01535c3d16a85900/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/01535c3d16a85900/badge.svg)](https://brick.blue/agent/01535c3d16a85900?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
70%

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.