mcpbeat

Payer API Directory MCP Server

com.dropwatchhq/payer-api-directory
answering

Payer API Directory is answering right now. Last checked 15 min ago. It exposes 4 tools.

Directory of US clearinghouse/payer APIs (Availity, Optum, Waystar) with pricing & access signals.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
68 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add payer-api-directory --transport http https://clearinghouse.dropwatchhq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "payer-api-directory": {
      "url": "https://clearinghouse.dropwatchhq.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.payer-api-directory]
url = "https://clearinghouse.dropwatchhq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "payer-api-directory": {
      "url": "https://clearinghouse.dropwatchhq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "payer-api-directory": {
      "url": "https://clearinghouse.dropwatchhq.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

clearinghouse
get_clearinghouse
Full record for one vendor: what it does, dated+confidence-tagged pricing signals, access requirements, and small-practice fit. confidence is one of published/reported/none.
clearinghouses
list_clearinghouses
List all medical clearinghouse / payer-API vendors in the directory with their access model, API style, supported X12 functions, and whether pricing is public.
recommend
recommend_clearinghouse
Transparently rank vendors for a practice. Returns scored shortlist with the reasoning for each. Inputs: functions needed, dev-integration flag, budget-sensitive flag.
vendors
vendors_by_function
Which vendors support a given X12 function. function slug one of: eligibility, claims, era, claim-status, prior-auth.

Endpoints

URLTransportStateLatencyChecked
https://clearinghouse.dropwatchhq.com/mcp streamable-http answering 103 ms 15 min ago

Payer API Directory — questions

Answers built from our own checks of this server.

What can Payer API Directory do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_clearinghouse, list_clearinghouses, recommend_clearinghouse, vendors_by_function. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Payer API Directory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 68 ms. The bar chart above shows every period we have measured.
How do I connect Payer API Directory?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Payer API Directory need an API key?
No. Payer API Directory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Payer API Directory?
It answers our handshake in 68 ms on average, which is faster than 94% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.