Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

imho.run game recommendations

REMOTE · IMHO.RUN

Steam games like any game you name, facts about a game, and finding a game from a description.

Available components

+3 this week 73 Trust /100

Last scanned (23 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2099 tokens (~262/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Oct 26 −1
    • Tool coverage: 80% → 69% ▼ functional
    • Schema quality: pass → fail ▼ functional
    • First check of Tool coverage: 100 functional
  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Oct 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Probed https://imho.run/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=imho.run CN=YE1,O=Let's Encrypt,C=US 3 Sept 2026 2 Dec 2026 ECDSA 256 ECDSA-SHA384 5bd0bc05c0955ab5c40b97bbc80f8b3819d
SANs: *.imho.run, imho.run
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of imho.run. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
run. present 37315 8 Verified
imho.run. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://imho.run/mcp Verified 200
http (plaintext) http://imho.run/mcp HTTPS enforced 301 https://imho.run/mcp
MCP tools · 8 exposed · ~1,877 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_game_by_description ~300

Identify a game from a description of what the user remembers (plot, look, platform, era). Returns ranked candidates with a reason each, a `confidence`, and `find_game_url`: imho.run's /find-game page with the description filled in (the user presses the button; nothing runs by itself). Pass what the user said about the platform, the release years and the camera as `platform`, `year_min` / `year_max` and `perspective` instead of leaving them only in the text. When `confidence` is not high or no result fits, give the user `find_game_url` so they can add details there. Slow (LLM) and rate-limited: use it only when the user does not know the title; for games similar to a known game use games_like or recommend. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

NameTypeReqDescription
descriptionstringyesWhat the user remembers about the game, in their words.
langstring––
perspectivestring–Camera: first person, third person, top-down or side view.
platformstring–Where the user played it, if they said (a platform family).
year_maxinteger–Latest plausible release year, if the user gave an era.
year_mininteger–Earliest plausible release year, if the user gave an era.
NameTypeReqDescription
attributionstringyes–
confidence–––
find_game_url––/find-game with the description filled in, for the user to refine.
langstringyes–
resultsarrayyes–
sourcestringyes–
tool_urlstringyes–

No examples provided.

game_facts ~147

Public facts about one Steam game: year, developers, genres, top tags, price, Steam Deck status, review numbers, a review-mined summary and links. For a few single-player games, `coop_via_mod` names a reviewed fan mod for co-op, with caveats. Use it to answer questions about a game the user names; for similar games use games_like or recommend. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

NameTypeReqDescription
gamestringyesGame name (typos and Russian names are fine), Steam appid or Steam store URL.
langstring–Language of the `why` lines.
NameTypeReqDescription
attributionstringyes–
gameobjectyes–
generated_atstringyes–
langstringyes–
other_matchesarray––
querystringyes–
sourcestringyes–

No examples provided.

games_like ~263

Steam games similar to ONE game, ranked by imho.run's recommender (the list on that game's imho.run page), each with a one-line reason, price, Steam Deck status, year, review numbers, the imho.run page URL and the Steam URL. Use it for 'games like X', optionally only free, co-op or Steam Deck games. Use `recommend` instead when the user names 2-3 games, wants other filters (no PvP, no microtransactions, release years, niche) or describes what they want in words. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

NameTypeReqDescription
coopboolean–Only co-op games.
coop_modestring–Kind of co-op (implies coop): online co-op (Remote Play Together does not count), or local same-screen / split-screen co-op.
freeboolean–Only free games.
gamestringyesGame name (typos and Russian names are fine), Steam appid or Steam store URL.
langstring–Language of the `why` lines.
ninteger––
steam_deckstring–Steam Deck verified, or playable-or-better.
NameTypeReqDescription
attributionstringyes–
filtersobjectyes–
generated_atstringyes–
langstringyes–
list_urlstringyesThe same list on imho.run.
other_matchesarray–Other games the query could mean; pass one's appid as `q` to switch.
querystringyes–
resultsarrayyes–
seedobjectyes–
sourcestringyesAlways "imho.run".

No examples provided.

library_recs ~228

Steam games for a player, ranked against their own public Steam library (what they play most), the way imho.run's library mode does it; owned games are left out. Use it when the user gives their Steam profile and wants picks for their taste in general; for 'games like X' use games_like or recommend. Takes a SteamID64 or a steamcommunity.com/profiles/<SteamID64> link (not a custom /id/ name) and works only for public profiles imho.run already has; otherwise it returns one 'unavailable' error with a link the user can open to paste their profile. Each pick names the most-played game it is closest to (`similar_to`). Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

NameTypeReqDescription
filtersobject–All optional, same meaning as in recommend.
langstring–Language of the `why` lines.
ninteger––
profilestringyesSteamID64 or steamcommunity.com/profiles/<SteamID64> link.
NameTypeReqDescription
attributionstringyes–
based_onarray–The profile's most-played games the reasons refer to.
filtersobjectyes–
generated_atstringyes–
langstringyes–
resultsarrayyes–
sourcestringyes–
tool_urlstringyesimho.run's library mode, where the user can paste the link.

No examples provided.

new_releases ~244

Games released on Steam in the last 30 days that players rate well (70%+ positive, 50+ positive reviews), or with `upcoming` the upcoming games that have a release date; optionally co-op only. The site's New releases list, with price, Steam Deck status, release date and links. Released games carry `release_kind`: `new`, or `ea_exit` for a game that just left Early Access (its 1.0; it was playable before), so call those 'out of Early Access', not new. `ea_exits`: include (default), exclude (brand-new games only) or only. Use it for 'what's new / coming out'; for what is gaining players now use trending. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

NameTypeReqDescription
coopboolean––
ea_exitsstring–Games that just left Early Access: include them, exclude them (only brand-new launches) or return only them.
langstring–Language of the `why` lines.
ninteger––
upcomingboolean––
NameTypeReqDescription
attributionstringyes–
coopboolean––
ea_exitsstring–The Early Access exits filter this list was built with.
kindstringyes–
langstringyes–
page_urlstringyes–
resultsarrayyes–
sourcestringyes–

No examples provided.

recommend ~437

Steam games for someone who likes 1-3 given games, ranked by imho.run's recommender: the list imho.run's own tool shows for those games and filters. Use it instead of games_like when the user names several games, wants filters beyond free / co-op / Steam Deck (no PvP, no microtransactions, no grind, not too hard, no Early Access, release years, more niche or more popular), or says what they want in words: pass that as `preferences` ('cozy base building, no combat'); the result says which Steam tags it was read as. When the user reacts to the picks, call it again with `liked` / `disliked`: liked games join the seeds, disliked ones never come back. Each pick has a one-line reason naming the seed it is closest to (`similar_to`), price, Steam Deck status, year, reviews, the imho.run URL and the Steam URL, plus `tool_url` (these games in imho.run's tool). Not for naming a game from a description (find_game_by_description) or facts about one game (game_facts). Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

NameTypeReqDescription
dislikedarray–Games the user disliked or already played: never recommended. Pass earlier picks the user rejected to get fresh ones.
filtersobject–All optional. Leave out what the user did not ask for.
langstring–Language of the `why` lines.
likedarray–Other games the user said they liked (e.g. from earlier answers). They fill free seed slots after `seeds` (3 in all); the rest are listed in `ignored`.
ninteger––
preferencesstring–What the user wants or wants to avoid, in their words (any language), e.g. 'dragons and crafting, no horror, no grind'. Read as Steam tags.
seedsarrayyes1-3 games the user likes: names, Steam appids or Steam URLs.
NameTypeReqDescription
attributionstringyes–
filtersobjectyes–
generated_atstringyes–
ignoredarray–liked / disliked games not used: no match, or liked past the 3 seed slots.
langstringyes–
preferences––How `preferences` were read as Steam tags.
preferences_applied––null without `preferences`; false when they could not be read.
preferred_tagsarray––
queryobjectyes–
resultsarrayyes–
seedsarrayyes–
sourcestringyes–
tool_urlstringyesimho.run's tool with these games picked; the user can tune filters there.

No examples provided.

search_games ~116

Find Steam games by title (typos, partial names, Russian names and acronyms are fine): appid, year, imho.run page and Steam link for each match. Use it to check which game the user means or to get an appid; the other tools also accept names directly. For a game the user can only describe, use find_game_by_description. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

NameTypeReqDescription
ninteger––
querystringyes–
NameTypeReqDescription
querystringyes–
resultsarrayyes–
sourcestringyes–

No examples provided.

trending ~142

Steam games trending right now (imho.run/trending): `rising` = established games gaining reviews and players against their own recent baseline, `breakouts` = new games taking off. Each has reviews this week, growth in %, price, Steam Deck status and links. Use it for 'what's hot / popular right now on Steam'; for new releases use new_releases, for games like a given game use games_like. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.

NameTypeReqDescription
kindstring––
langstring–Language of the `why` lines.
ninteger––
NameTypeReqDescription
attributionstringyes–
kindstringyes–
langstringyes–
page_urlstringyes–
resultsarrayyes–
sourcestringyes–
statusstringyescollecting: the lists are not ready yet; results is empty.
updated_at–––

No examples provided.

Install

How do I install the imho.run game recommendations MCP server?

imho.run game recommendations is a hosted endpoint at https://imho.run/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · imho.run

# add to Claude Code
claude mcp add --transport http run-imho-games 'https://imho.run/mcp'
Common questions

What is the imho.run game recommendations MCP server?

imho.run game recommendations is an MCP server listed in the public MCP registry as run.imho/games. Steam games like any game you name, facts about a game, and finding a game from a description. This page covers its hosted endpoint (https://imho.run/mcp).

Is the imho.run game recommendations MCP server safe to use?

imho.run game recommendations scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the imho.run game recommendations MCP server expose?

imho.run game recommendations exposes 8 tools: games_like, recommend, library_recs, game_facts, find_game_by_description, and 3 more. Their descriptions and schemas cost roughly 1,877 tokens of context every time the server is loaded.

Does the imho.run game recommendations MCP server require authentication?

No. We connected to imho.run game recommendations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the imho.run game recommendations MCP server still maintained?

imho.run game recommendations is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.