INDIVIDUAL MCP TOOL

search_drugs

Resolve a brand or ingredient name to RxNorm drug products and their rxcui identifiers.

benefily.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://www.benefily.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for search_drugs and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.benefily]
url = "https://www.benefily.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "benefily": {
      "type": "http",
      "url": "https://www.benefily.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: benefily
Remote MCP URL: https://www.benefily.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "benefily": {
      "url": "https://www.benefily.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "benefily": {
      "type": "http",
      "url": "https://www.benefily.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "benefily",
  "transport": "streamable-http",
  "url": "https://www.benefily.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

check_prior_auth — Determine whether a Medicare Part D payer requires prior authorization for a drug, based on the payer's own formulary filed with CMS.
list_payers — List the payers that file Medicare Part D formularies, with the slug to pass to check_prior_auth and the CMS contract entities grouped under each brand.
get_source — Return the provenance of the underlying data: the CMS document title, publisher, licence, effective date, retrieval time, SHA-256 of the ingested file, and record counts.