Routescore vs MediaWiki MCP Server

In-depth architectural comparison of the Routescore and MediaWiki MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

R

Choose Routescore when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: quote_mev_cover, quote_bridge_refund, quote_lrt_slashing.

Explore Routescore Details

Choose MediaWiki MCP Server when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: compare-pages, get-category-members, get-file.

Explore MediaWiki MCP Server Details

Feature & Specification Comparison

Specification	R Routescore Developer Tools	MediaWiki MCP Server Developer Tools
Summary	Read-only pre-sign evidence for onchain agents: route quality, MEV exposure, clear/caution verdict.	MCP server enabling AI clients to interact with any MediaWiki wiki through standard tools
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "routescore": {
      "command": "npx",
      "args": [
        "-y",
        "@routescore/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "mediawiki-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@professional-wiki/mediawiki-mcp-server@latest"
      ]
    }
  }
}

Related MCP Server Comparisons