Medicare Coverage vs Git

A side-by-side look at the Medicare Coverage and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Medicare Coverage logoMedicare CoverageBiology & Bioinformatics · Local subprocess (stdio)Medicare coverage policy from CMS: national and local coverage determinations, plus open analyses56GoodAuth: not declaredGit logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth required

Verdict: choose Medicare Coverage for biology & bioinformatics work as a local process; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Medicare Coverage logoChoose Medicare Coverage when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like medicare_ncd_search, medicare_ncd_detail, medicare_lcd_search.
Explore Medicare Coverage

Git logoChoose Git when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like repo_path, context_lines, target.
Explore Git

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMedicare Coverage logoMedicare CoverageGit logoGit
CategoryBiology & BioinformaticsVersion Control
Quality signal56/100 · Good81/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars091,512
Directory activity 0 views 0 installs 0 upvotes 49 views 0 installs 0 upvotes
Tools2716

Tools & capabilities

Medicare Coverage tools 27

  • medicare_ncd_searchANSWERS "does Medicare cover X" / "is X covered by Medicare" / "what is Medicare's coverage policy for X" — searches current Medicare National Coverage Determinations (NCDs), the national policy documents that say whether Medicare covers a drug, device, procedure or therapy. Search by everyday prod…
  • medicare_ncd_detailRetrieve one official Medicare National Coverage Determination by CMS document ID and optional version, including covered indications, limitations, effective dates, benefit category, and revision text.
  • medicare_lcd_searchSearch current final Medicare Local Coverage Determinations (LCDs), optionally restricted to a state. LCDs are contractor- and jurisdiction-specific and can differ across locations.
  • medicare_lcd_detailRetrieve one Medicare LCD by document ID and version. Detailed LCD text requires a CMS license-agreement bearer token because documents may contain licensed AMA/ADA/AHA material; pass _licenseToken obtained directly from CMS after accepting those terms.
  • medicare_nca_searchSearch National Coverage Analyses (NCAs) and Coverage Analyses for Labs (CALs), including open and completed CMS evidence reviews. An open analysis is a policy process, not a coverage decision.
  • medicare_nca_detailRetrieve one CMS National Coverage Analysis by document ID, including request, issue, benefit category, dates, decision memo, and public-comment status when supplied by CMS.
  • medicare_recent_coverage_changesRecently published or updated national Medicare coverage documents from CMS, including NCDs, NCAs, CALs, MEDCAC meetings, and technology assessments.
  • medicare_coverage_statesList CMS Coverage API state identifiers used to scope local Medicare coverage searches.
  • medicare_article_code_profileRetrieve one CMS Medicare Coverage Article with its CPT/HCPCS codes and contractor records. Licensed AMA/ADA/AHA content requires a caller-provided CMS license token. Code inclusion describes billing guidance, not guaranteed coverage or payment.
  • medicare_local_coverage_variationCompare final LCD search matches across 1–15 states and Medicare Administrative Contractors. Different matching document counts or titles are policy signals, not proof of unequal beneficiary access or payment.
  • medicare_coverage_timelineRetrieve official CMS version or revision history for a Medicare NCD, NCA, CAL, or LCD. Accepts either identifier CMS publishes for a coverage document: the public one that appears in the policy text and in every citation of it — an NCD section number such as 310.1 or 90.2, an NCA/CAL tracking numb…
  • medicare_hcpcs_utilization_trendShow annual Medicare Physician & Other Practitioners national utilization and payment metrics for one HCPCS code. Claims are fee-for-service aggregates with suppression and methodology limits; they do not measure total US use, coverage, demand, or company revenue.
  • +15 more on the listing page

Git tools 16

  • repo_path
  • context_lines
  • target
  • message
  • MERGE_HEAD
  • HEAD
  • files
  • max_count
  • start_timestamp
  • end_timestamp
  • branch_name
  • base_branch
  • +4 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Medicare Coverage

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "medicare-coverage": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-medicare-coverage"
      ]
    }
  }
}

Git

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "installations"
      ]
    }
  }
}

Frequently asked questions

Medicare Coverage is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Medicare Coverage for biology & bioinformatics work and Git for version control.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Medicare Coverage has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add medicare-coverage and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Medicare Coverage has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars.