Local MCP server/Finance

Resolved Markets MCP server

Local MCP server

Resolved Markets gives an agent Polymarket order-book data, including live books, historical snapshots, OHLC candles, trades and settlement results, plus Hyperliquid perpetual books. The provider documents a local npx package, @elcara-hq/resolvedmarkets-mcp, and an optional self-hosted HTTP mode on port 3002. It does not document the hosted mcp.resolvedmarkets.com endpoint, so the local path is primary. An X-API-Key header with an rm_ key is required; only public stats work without a key.

API key (X-API-Key rm_...) Source checked Nov 12, 2026 Local install path Reviewed 2026-11-16
About

Where it fits

Prediction-market analysts who want order-book and settlement data in an agent.

  • Pull live Polymarket order books.
  • Fetch historical snapshots and OHLC candles.
  • Review trades and settlement results.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Run the Resolved Markets stdio server

Set HF_API_URL=https://api.resolvedmarkets.com and HF_API_KEY=rm_.... The provider documents the local npx package and an optional self-hosted HTTP mode on port 3002, not a hosted mcp.resolvedmarkets.com endpoint.

npx -y @elcara-hq/resolvedmarkets-mcp

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Resolved Markets documentationhttps://resolvedmarkets.com/ai-agents