LeashIndex Get the report

Index / other

Steam (read-only)

io-github-sarg338-steam-mcp declares 41 capabilities across 41 tools, with 3 critical issues.

63/100 exposureElevated

Manifest recorded 2026-10-13 from tools/list answered by the PyPI package steam-mcp==1.19.0 (published to PyPI as steam-mcp, listed in the official MCP registry as io.github.Sarg338/steam-mcp 1.19.0), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 41 tools

41 of 41 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 1 of 41 tools

1 tool is classified as irreversible and declares no limit.

critical · uncapped-spend · 1 of 41 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 41 tools

41 of 41 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 41 tools

41 of 41 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

low · uncapped-read · 40 of 41 tools

40 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
steam_get_deck_compatibilityread declared
steam_resolve_vanity_urlread declared
steam_get_player_summaryread declared
steam_get_steam_levelread declared
steam_get_player_bansread declared
steam_get_friend_listread declared
steam_find_friends_who_ownread declared
steam_get_owned_gamesread declared
steam_get_recently_played_gamesread declared
steam_get_player_achievementsread declared
steam_get_game_schemaread declared
steam_get_global_achievement_percentagesread declared
steam_get_user_game_statsread declared
steam_get_rarest_unlocksread declared
steam_search_appsread declared
steam_get_app_detailsread declared
steam_get_dlcread declared
steam_get_app_tagsread declared
steam_discoverread declared
steam_get_app_reviewsread declared
steam_analyze_app_reviewsread declared
steam_compare_gamesread declared
steam_get_update_impactread declared
steam_analyze_gameread declared
steam_get_featured_specialsread declared
steam_get_store_highlightsread declared
steam_get_wishlistread declared
steam_get_current_playersread declared
steam_get_app_newsread declared
steam_get_player_badgesread declared
steam_get_package_detailsread declared
steam_compare_playersread declared
steam_analyze_libraryread declared
steam_should_i_buypay inferred
steam_recommendread declared
steam_plan_coop_nightread declared
steam_get_app_regional_pricingread declared
steam_get_workshop_itemread declared
steam_get_user_groupsread declared
steam_get_inventoryread declared
steam_get_market_priceread declared
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.