RuneScape Wiki RS3
https://runescape-wiki-mcp.fly.dev/mcp ↗
Description
This MCP server provides AI assistants with real-time access to RuneScape 3 game data through the RuneScape Wiki APIs. It enables AI systems to retrieve current Grand Exchange prices, detailed item information (including stats, examine text, and alchemy values), historical price trends with configurable time intervals, and player statistics from the official hiscores across different game modes (normal, ironman, hardcore ironman). The server acts as a bridge between AI applications and RuneScape's extensive database, allowing for dynamic queries about items, market analysis, player progression tracking, and game-related assistance without requiring direct API knowledge or authentication from the end user.
What our measurements say
RuneScape Wiki RS3 is a remote MCP server published at runescape-wiki-mcp.fly.dev. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 6,825 ms, a delay an agent will notice. It offers a narrow, focused set of 12 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are generally descriptive and indicate purpose (e.g., 'lookup_item' vs 'get_item_price')
- Descriptions often specify when to use tools (e.g., 'prefer this before get_item_price')
- Clear differentiation between summary vs detailed data tools (e.g., 'summarize_price_history' vs 'get_item_graph')
Weaknesses
- Some parameter requirements are unclear (e.g., 'buyPrice/sellPrice' in estimate_flip lacks explicit required/optional status)
- Tool overlap exists between lookup_item and get_item_price for name-based queries
- Error handling documentation is inconsistent across tools
- Some descriptions lack context for why specific data (e.g., 'letter counts' in get_category_info) is useful
get_ge_info— Metadata description lacks context for 'lastConfigUpdateRuneday'estimate_flip— Parameter requirements (buyPrice/sellPrice) not explicitly definedget_category_info— Purpose of 'letter counts' not explained in descriptionlookup_item— Overlap with get_item_price for name-based queriessummarize_price_history— Could be more explicit about data aggregation timeframe
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'dual' · indicates a shift in operational mode with potential compliance implications
- 2026-09-11T07:35:54.413Z — complianceScore improved from null to 100 · suggests successful validation of new era configuration
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 161ms → warm 156ms (penalty 5ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Incomplete probe — one leg did not answer, era result not counted
- Server build: — → 1.1.0
- Supported versions: — → 2026-07-28
- Era changed: Auth-gated → Dual-era
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/birdwell-runescape-wiki-mcp)<a href="https://mcpmetrics.io/servers/birdwell-runescape-wiki-mcp"><img src="https://mcpmetrics.io/badge/birdwell/runescape-wiki-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see