Home / MCP registry index / io.github.areshms/hms-mcp

HMS x402 Data Origins (RE Data Refinery + Storefront)

io.github.areshms/hms-mcp in the official MCP registry. Endpoint https://hms-mcp.ares-hms.workers.dev/mcp. Source: github.com/areshms/hms-mcp.

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

Connect it

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

claude mcp add --transport http hms-mcp https://hms-mcp.ares-hms.workers.dev/mcp

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

code --add-mcp '{"name":"hms-mcp","type":"http","url":"https://hms-mcp.ares-hms.workers.dev/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.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

refinery_auctions refinery_cash_buyers refinery_coverage refinery_credits refinery_foreclosures refinery_health refinery_preforeclosures refinery_properties refinery_properties_zpid refinery_properties_zpid_price_history refinery_properties_zpid_schools refinery_properties_zpid_tax_history refinery_search refinery_tax_sales refinery_v1_coverage sf_health sf_v1_coverage sf_v1_rental_rates sf_v1_truck_fuel_prices sf_v1_truck_sleep_stops hmt_trending hmt_trending_batch hms_get_origins

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-11-13): 85c2c3cbc8d0deab. 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.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-areshms-hms-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-areshms-hms-mcp)

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. How tool poisoning works. What we found across the registry. Check another server.

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

Related

Crypto and Web3 MCP servers