← Registry

General Tools

benefily.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint4 known toolsFirst detected September 15, 2026Last detected September 15, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name
benefily
Version
1.0.0
Capabilities
tools
Server instructions

Determine whether a Medicare Part D payer requires prior authorization for a drug. Answers are deterministic projections of payers' own formularies as filed with CMS — no model is in the path, and identical input always yields identical output. Every answer cites the CMS document and its effective date. FOUR BOUNDARIES BELONG IN ANY ANSWER YOU GIVE A USER: (1) This covers Medicare Part D DRUG benefits only — never medical or procedure prior authorization, never commercial/employer plans, never Medicaid. (2) A status of `not_on_formulary` means the drug is NOT COVERED by that payer's plans; it does not mean prior authorization is unnecessary, and it is generally a worse outcome for the patient. (3) A status of `varies` means requirements differ across that payer's plans — the member's specific plan, on their insurance card, decides. (4) `unknown` means we hold no filing; it never means 'no prior authorization required'. This is administrative information, not medical advice, not a coverage guarantee and not an authorization. Always surface `notices` verbatim.

Known tools 4

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.

Inferred read-only
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.

Inferred read-only
search_drugs

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

Inferred read-only
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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.