Home / MCP registry index / wiki.rust/rust-wiki

rust.wiki

wiki.rust/rust-wiki in the official MCP registry. Endpoint https://rust.wiki/mcp.

The registry describes it as: Live data for the game Rust: skin prices and history, items, item store, loot tables, servers.

We read its 57 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http rust-wiki https://rust.wiki/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "rust-wiki": {
      "url": "https://rust.wiki/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"rust-wiki","type":"http","url":"https://rust.wiki/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_items browse_items get_item get_item_skins search_skins browse_skins get_skin get_skin_price get_skin_price_history list_skin_collections get_skin_collection find_skin_deals get_market_cap get_market_movers get_item_store get_item_store_history get_store_rotation search_workshop list_monuments get_monument list_loot_sources get_loot_table get_cctv_codes search_commands search_world_entities get_world_entity get_building_piece get_raid_costs get_upkeep_rules get_rust_updates search_servers get_top_servers get_recent_wipes get_server get_data_freshness get_skin_orderbook get_skin_marketplace_history get_market_index compare_market get_server_player_history get_server_stats get_twitch_drops search_guides calculate_craft_cost calculate_recycle_yield calculate_raid_cost calculate_upkeep genetics_best_layout genetics_predict resolve_steam_profile get_player_stats get_inventory_leaderboard get_inventory get_inventory_value_history get_inventory_valuation list_inventory_snapshots get_inventory_snapshot

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 9ad97df8c83e71b6. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/wiki-rust-rust-wiki/badge.svg)](https://lazaretto.dev/mcp-registry/wiki-rust-rust-wiki)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.