Skip to content

com.dropwatchhq/payer-api-directory

by dropwatchhq.com · remote · no sign-in to list tools · v1.0.0 · published by com.dropwatchhq

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

Changes · 2

4 tools: 2 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http payer-api-directory https://clearinghouse.dropwatchhq.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 2Claude Code: ask
  • recommend_clearinghouseTransparently rank vendors for a practice.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Transparently rank vendors for a practice. Returns scored shortlist with the reasoning for each. Inputs: functions needed, dev-integration flag, budget-sensitive flag.
  • vendors_by_functionWhich vendors support a given X12 function.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Which vendors support a given X12 function. function slug one of: eligibility, claims, era, claim-status, prior-auth.
Only reads 2Claude Code: allow
  • get_clearinghouseFull record for one vendor: what it does, dated+confidence-tagged pricing signals, access requirements, and small-practice fit.No findings

    Why it is in this group

    • The name "get_clearinghouse" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_clearinghousesList all medical clearinghouse / payer-API vendors in the directory with their access model, API style, supported X12 functions, and whether pricing is public.No findings

    Why it is in this group

    • The name "list_clearinghouses" says "list": a word for reading.
    Description, as the server wrote it
    List all medical clearinghouse / payer-API vendors in the directory with their access model, API style, supported X12 functions, and whether pricing is public.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http payer-api-directory https://clearinghouse.dropwatchhq.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__payer-api-directory__list_clearinghouses",
      "mcp__payer-api-directory__get_clearinghouse"
    ],
    "ask": [
      "mcp__payer-api-directory__vendors_by_function",
      "mcp__payer-api-directory__recommend_clearinghouse"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as payer-api-directory. Review it before you use it.