MCP server

A hosted Model Context Protocol server over Streamable HTTP (JSON-RPC 2.0). It exposes the same determination engine as the website and the REST API — one behaviour, three surfaces.

Endpoint

https://benefily.com/api/mcp

Tools

check_prior_auth: Does this payer require prior authorization for this drug? Returns status, plan breakdown and the CMS citation.
list_payers: Payer slugs to pass to check_prior_auth, with the CMS contract entities behind each brand.
search_drugs: Resolve a brand or ingredient name to RxNorm products and rxcui identifiers.
get_source: Provenance: document title, publisher, licence, effective date, SHA-256 and record counts.

Claude Code

claude mcp add --transport http benefily https://benefily.com/api/mcp \
  --header "x-api-key: ben_test_sandbox"

Any MCP client

{
  "mcpServers": {
    "benefily": {
      "type": "http",
      "url": "https://benefily.com/api/mcp",
      "headers": { "x-api-key": "ben_test_sandbox" }
    }
  }
}

Verify by hand

curl -X POST "https://benefily.com/api/mcp" \
  -H "content-type: application/json" \
  -H "x-api-key: ben_test_sandbox" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

What to tell your users

The server’s initialize response carries an instructions string stating the coverage boundary and the meaning of each status. Relay it: an assistant that reports a Part D answer as though it applied to a commercial plan has been misled by us, not by its user.

Always surface the notices array verbatim.

REST API documentation · Methodology