Skip to content
External endpointresponds

needmoar.games

Ranks Steam games by how much players like them, learned from head-to-head duels.

Endpoint URL
https://needmoar.games/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
518 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
games.needmoar/needmoar

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
needmoar.games
Version
1.0.0
Capability keys
tools, resources, prompts
Tool names
search_games, versus, game_detail
Instructions excerpt

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: - "which do people prefer, A or B?" → versus - "how popular / well-liked is X?" → game_detail - "games similar to X?" → game_detail (its "also like" neighbours are real co-preference, not tags) Workflow: resolve every game name to a Steam appid with search_games first, then call versus or game_detail with the appid(s). Every result includes the canonical needmoar.games URL for that game or matchup — cite it. Scores come from a finite duelling community, so player counts are small; report them honestly and treat a low count as a weak signal. The tool results above are the crowd consensus, the same for everyone. Whe

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 313ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 798ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 511ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 518ms