mcp-ca-medi-cal-fee-schedule
California Medi-Cal fee-for-service maximum rates per procedure code, from the California Department of Health Care Services (DHCS) monthly Medi-Cal rates extract.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/pipeworx-io--mcp-ca-medi-cal-fee-schedule)HTML
<a href="/listings/pipeworx-io--mcp-ca-medi-cal-fee-schedule"><img src="/api/listings/pipeworx-io--mcp-ca-medi-cal-fee-schedule/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"ca-medi-cal-fee-schedule": {
"url": "https://gateway.pipeworx.io/ca-medi-cal-fee-schedule/mcp"
}
}
}What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/ca-medi-cal-fee-schedule/mcp` returns the tools in the table above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`, `discover_tools`, `search_within`, `remember`/`recall` and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's `initialize` response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via `ask_pipeworx`, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 2034+ data sources. The only difference is which pack's tools are listed **directly**; `ask_pipeworx` reaches all of them from either one.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 155 lines
- # @pipeworx/ca-medi-cal-fee-schedule
- California Medi-Cal (Medicaid) fee-for-service maximum rates per procedure code: for a CPT or HCPCS code, the unit value, basic, child and emergency-room rates and the conversion indicator that prices it, from the California Department of Health Care Services (DHCS) monthly Medi-Cal rates table.
- Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2034+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
- ## Tools
- - `ca_medi_cal_rate_lookup(code, proc_type?)` — every listing of a procedure code (a code can appear under several proc types) with its rates and the publisher's indicator columns, plus `data_as_of`. An unmatched code returns the nearest codes instead of an empty result.
- - `ca_medi_cal_rate_search(query?, code_prefix?, proc_type?, limit?)` — search by description words (all must appear) and/or code prefix. Word search reaches HCPCS Level II and the state's own codes; CPT codes are found by `code_prefix`. An unmatched query returns the rows matching some of its words.
- - `ca_medi_cal_conversion_factors(conv_ind?)` — the conversion factors behind the rates (by service category, patient age and provider group), the table's size and proc types, and `data_as_of`.
- ## Auth
- Keyless.
- ## Data sources
- - California Department of Health Care Services (DHCS), Medi-Cal rates — the monthly "all Medi-Cal rates" table with its conversion-factor table. The table is dated the 15th of each month and posted the 16th; `data_as_of` is that date (2026-11-15 in the first edition). Stored copy, refreshed by hand (see below).
- Things worth knowing:
- - **Fee-for-service maximum rates, per code.** Not what a Medi-Cal managed-care plan pays, not clinic (FQHC/RHC) per-visit rates (that is `ca-medicaid-rates`) and not Medicare (`medicare-pricing`).
- - **Column meanings** were read off the published workbook's header row: Proc Type, Proc Code, Procedure Description, Unit Value, Basic Rate, Child Rate, ER Rate, Conv Ind, ER Ind, Cutback Ind, Prof %, Rental Rate, Non-Physn Med Prac Ind. The extract does not define Proc Type, ER Ind, Cutback Ind or Prof %, so they are returned as published and not interpreted. A code listed under several proc types has one row per type with its own rates; compare them.
- - **Rates are built from conversion factors.** On every non-zero row in the first edition (17,046 of 17,046), `basic_rate` = `unit_value` x a conversion factor listed for the row's `conv_ind`; the bake reports this check. Which factor applies depends on provider type, patient age and place of service (`ca_medi_cal_conversion_factors`).
- - **CPT descriptor decision (fleet #4664).** The workbook's own first row reads "CPT codes and descriptors are copyright 2002 American Medical Association". We hold no AMA licence, so CPT codes (5 digits, or 4 digits plus a letter) return `description: null` with a `descriptor_note`; the code and rates are unchanged. Four-digit revenue codes (NUBC titles) are treated the same way. HCPCS Level II and the state's own codes keep the publisher's description (abbreviated and cut to about 40 characters). The bake strips descriptors itself, and `src/index.test.ts` fails if any CPT or revenue row carries text, so a refresh cannot bring it back. Same call as `ny-medicaid-fee-schedule`.
- - **Reuse terms.** The State of California's Conditions of Use say: "In general, information presented on this website, unless otherwise indicated, is considered in the public domain. It may be distributed or copied as permitted by law." DHCS's own terms page sits behind the same bot challenge as the data and could not be read; nothing on the downloaded files restricts reuse beyond the AMA line above. A stored copy is redistribution, so this is recorded here and the CPT text is withheld.
- - A rate of 0.00 is returned as 0. Some codes are listed with no payable rate.
- - `scripts/bake-index.mjs` reads the publisher's zip and refuses a malformed row, a changed layout, a duplicate (type, code), fewer than 19,000 rows or more than 10% fewer than the previous bake.
- ## Refresh
- Runner: **human**. The publisher serves the download only behind a bot challenge, so a person downloads "Download All Medi-Cal Rates" in a browser each month after the 16th and puts the zip where the chief of staff drops it (machine 0, `pipeworx-inbox/ca-medi-cal-ffs/rates_files.zip`). Then:
- ```
- node mcps/ca-medi-cal-fee-schedule/scripts/bake-index.mjs --zip path/to/rates_files.zip
- node scripts/check-baked-indexes.mjs
- ```
- and commit `src/ca-medi-cal-data.ts`. The staleness entry is in `scripts/baked-index-freshness.json` (monthly tier).
- ## Budget
- # BUDGET: one-time load $0 (one KV object of about 1.4 MB, written by the normal gateway deploy step). Steady state under $0.01/month: 12 refreshes a year x 1 KV write ($5/M) is about $0.0001/year; reads are one KV read per gateway isolate cold start ($0.50/M), about 3,000 a month at 1,000 calls/day = $0.002/month. No D1, Durable Object, R2 or Queue. Rejected: D1 (about 19.6k rows written a month is only $0.02, but it adds a second store for a table one KV read already serves) and R2 (unneeded under 2 MB). Far below the $50 one-time and $25/month lines in CLAUDE.md.
- Not covered: Medi-Cal's managed-care rates, drug (NDC) rates, and the publisher's other rate files; only this table is served.
- ## Quick Start
- Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
- ```json
- {
- "mcpServers": {
- "ca-medi-cal-fee-schedule": {
- "url": "https://gateway.pipeworx.io/ca-medi-cal-fee-schedule/mcp"
- }
- }
- }
- ```
- ### What this endpoint actually serves
- `tools/list` at `https://gateway.pipeworx.io/ca-medi-cal-fee-schedule/mcp` returns the tools in the table
- above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
- `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
- gateway-wide set. So the tool count you see is larger than this table: a
- single-pack endpoint currently lists roughly 30 shared tools alongside the
- pack's own. The connection's `initialize` response states its exact scope, and
- is the authoritative answer for a given day.
- This is deliberate, not multiplexing by accident. The meta-tools are what let a
- scoped connection answer a question this pack does not cover — via
- `ask_pipeworx`, which routes across the whole catalog — without you adding a
- second MCP server. There is currently no way to mount a pack endpoint without
- them; if the extra schemas cost you more context than the routing is worth,
- connect to the full gateway once rather than to several pack endpoints.
- Or connect to the full Pipeworx gateway to get every pack's tools listed
- directly, instead of just this one's:
- ```json
- {
- "mcpServers": {
- "pipeworx": {
- "url": "https://gateway.pipeworx.io/mcp"
- }
- }
- }
- ```
- Both URLs reach the same gateway and the same 2034+ data sources. The
- only difference is which pack's tools are listed **directly**; `ask_pipeworx`
- reaches all of them from either one.
- ## No MCP client? Call it over HTTP
- ```bash
- curl -X POST https://gateway.pipeworx.io/v1/tools/ca_medi_cal_rate_lookup \
- -H 'Content-Type: application/json' \
- -d '{"code":"99213"}'
- ```
- No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/ca_medi_cal_rate_lookup`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
- ## Run it from npm
- `@pipeworx/mcp-ca-medi-cal-fee-schedule` is a local stdio bridge to the Pipeworx gateway: your MCP client
- starts it with `npx`, and it forwards every call to the same
- `https://gateway.pipeworx.io/ca-medi-cal-fee-schedule/mcp` endpoint shown above. It needs network access;
- there is no offline mode.
- ```json
- {
- "mcpServers": {
- "ca-medi-cal-fee-schedule": {
- "command": "npx",
- "args": ["-y", "@pipeworx/mcp-ca-medi-cal-fee-schedule"]
- }
- }
- }
- ```
- Without a key it calls anonymously, capped at 50 calls a day. A free account
- raises that to 200 a day: get a key at https://pipeworx.io/signup and add
- `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
- The key is sent as a Bearer token, the same way a hosted connection sends it,
- so calls are metered and billed exactly as they are there.
- It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
- also list `ask_pipeworx` and the other gateway-wide tools.
- Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
- default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
- your Node version's documentation.
- ## Using with ask_pipeworx
- Instead of calling tools directly, you can ask questions in plain English —
- this works on the pack endpoint above as well as on the full gateway:
- ```
- ask_pipeworx({ question: "your question about Ca Medi Cal Fee Schedule data" })
- ```
- The gateway picks the right tool and fills the arguments automatically.
- ## More
- - [Docs and guides](https://pipeworx.io/docs)
- - [pipeworx.io](https://pipeworx.io)
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.