Back to Browse

Hms MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Remote MCP over two HMS x402 origins: scored Ohio RE data + car-rental rates. Tokenless x402 USDC.

About

Remote MCP over two HMS x402 origins: scored Ohio RE data + car-rental rates. Tokenless x402 USDC.

Remote endpoints: streamable-http: https://hms-mcp.ares-hms.workers.dev/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

21 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-areshms-hms-mcp": {
      "url": "https://hms-mcp.ares-hms.workers.dev/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

hms-mcp — HMS x402 Data Origins MCP Server

Remote MCP server (Streamable HTTP) that exposes both HMS x402 data origins as MCP tools for AI agents. Tokenless: no API keys, no wallets. Free tools answer directly; paid tools surface the origin's x402 v2 Payment Required challenge (USDC on Base) so an x402-capable agent can settle and re-call.

  • Endpoint: https://hms-mcp.ares-hms.workers.dev/mcp
  • Transport: Streamable HTTP (POST, JSON-RPC 2.0). No SSE required.
  • Owner: HMS LLC (Blake Hightower) — areshms

Origins behind this server

Connect (ready-to-copy configs)

{ "mcpServers": { "hms-mcp": { "url": "https://hms-mcp.ares-hms.workers.dev/mcp" } } }

Tools (19 + meta)

ToolMaps toPrice (per call)
refinery_searchGET /search$0.05
refinery_propertiesGET /properties (city filter)$0.03
refinery_properties_zpidGET /properties/{zpid}$0.03
refinery_properties_zpid_price_historyGET /properties/{zpid}/price-history$0.02
refinery_properties_zpid_tax_historyGET /properties/{zpid}/tax-history$0.02
refinery_properties_zpid_schoolsGET /properties/{zpid}/schools$0.02
refinery_foreclosuresGET /foreclosures$0.05
refinery_tax_salesGET /tax-sales$0.05
refinery_auctionsGET /auctions$0.05
refinery_preforeclosuresGET /preforeclosures?county= (19 Ohio counties)$0.05
refinery_cash_buyersGET /cash-buyers$0.50–$2.50
refinery_healthGET /healthFree
refinery_coverage / refinery_v1_coverageGET /coverage (real record counts)Free
refinery_creditsGET /creditsFree
sf_v1_rental_ratesGET /v1/rental/rates?city=$0.03 (live)
sf_v1_truck_sleep_stopsGET /v1/truck/sleep-stopsFree (until data)
sf_healthGET /healthFree
sf_v1_coverageGET /v1/coverage (honesty gate)Free
hms_get_originsmeta: origins + payment flowFree

How paid tools work (tokenless)

  1. Call a paid tool. The wrapper forwards to the origin and returns its HTTP 402 payload, including the x402 v2 challenge (network: eip155:8453 (Base), token: USDC, amount, receiver, facilitator).
  2. Settle the challenge with any x402 client (USDC on Base).
  3. Re-call the same tool with the same params, passing the produced header value as x402_payment — the wrapper forwards it as X-PAYMENT and returns your data.

The wrapper never holds funds or keys. Prices are set by the origin workers.

Deployment

Cloudflare Worker (plain JS, no build step): npx wrangler deploy in this directory. Uses Cloudflare service bindings to call the two origin workers on the same account (re-data-refinery, storefront-data-hms) — same-account *.workers.dev fetches are blocked (error 1042) without bindings.

Local verification:

curl -s -X POST https://hms-mcp.ares-hms.workers.dev/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Known limitation

Cloudflare's workers.dev edge bans the bare Python-urllib/x client signature (error 1010, browser_signature_banned) across all *.workers.dev hosts — this is zone-level, not something this worker can allowlist. Python clients that send any normal User-Agent (e.g. requests with a browser-like UA) are unaffected.

License

MIT

Reviews

No reviews yet

Be the first to review this server!