ClinX 340B server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
ClinX 340B server
A small program that lets an AI assistant look things up in ClinX's open tables about the federal 340B drug pricing program: the state laws on the books, the bills in Congress and the state legislatures, the rules and notices federal agencies publish, and a calendar of their dates.
Status: running at https://clinx.org/mcp since 15 November 2026. Give that address to an
assistant that accepts connectors (MCP servers); there is no key and no account. It is not
published as a package yet, so to run your own copy you start it yourself, as shown below.
What it is, in plain words
Assistants such as Claude can be given "tools": small lookups they may call while answering a question. The Model Context Protocol (MCP) is the common way to offer such tools. This is an MCP server with nine of them.
Ask an assistant "which states passed a contract pharmacy law this year?" and, with this server connected, it does not have to guess or search the web. It asks the server, gets rows from the same tables anyone can download from clinx.org/data, and answers with the link to each official page.
The server holds no data of its own. It reads the four public files from clinx.org, keeps them in memory for an hour, and answers from that copy. It only reads. It has no sign-in, no key, no account, and it keeps nothing about who asked what.
Related MCP server: Lawmesh MCP Server
The nine tools
Tool | What it answers |
| State laws on the books that name 340B, by state, kind or words. |
| One law in full: citation, who it binds, what it limits, how it is enforced, dates, the passage that names 340B. |
| Bills that name 340B, by state (or |
| One bill in full, with its sponsor, stage, latest step and every dated step. |
| Federal rules, proposed rules and notices that name 340B, by kind of document, role, words, day of publication, or whether comments are still open. |
| One rule or notice in full: the agency that wrote it, what it does about 340B, its comment deadline, the day it takes effect and every other day it sets. |
| Dated steps, hearings, session days and federal dates. With no dates given: what is coming up from today. |
| One place at a glance: a state's laws, its bills by stage, and what is next. |
| Where the tables come from, when each was last brought up to date, the licence. |
Every row in an answer carries the link to the official page it came from, and every answer says the day its table was last brought up to date. The plain sentences about each law, bill and notice were written by a person reading the official text. They are a reading aid, not legal advice, and a bill's sentence can trail a newer version of its text. Dates on the calendar can move.
Three codes name a place. A state has its two letters, such as RI. Congress is US. Federal
agencies, which write rules and notices and not bills, are FED.
"Coming up" and "open for comment" go by the day the question is asked, not by the day the tables were last brought up to date. A federal notice nobody has read yet is still listed, with the Federal Register's own facts and no sentence; the answer says so.
A mistake in what was asked (a state that is not a two-letter code, a date in the wrong shape, a bill that is not in the table) is said back in plain words, so the assistant can correct itself.
Try it
The quick way. Give an assistant the address https://clinx.org/mcp as a connector (an MCP
server) and ask it a question. Nothing to install.
Your own copy. You need Node.js 20 or newer. Nothing else is installed: the server uses no outside packages.
git clone https://github.com/VVillBerchtold/clinx-mcp.git
cd clinx-mcp
npm testAs a helper program for an assistant app. Most apps take a small piece of configuration that names the program to start. For Claude Desktop and similar apps:
{
"mcpServers": {
"clinx-340b": {
"command": "node",
"args": ["/full/path/to/clinx-mcp/src/stdio.js"]
}
}
}For Claude Code:
claude mcp add clinx-340b -- node /full/path/to/clinx-mcp/src/stdio.jsOver the web, on your own computer.
node src/serve.jsIt listens at http://127.0.0.1:8340/mcp, on your computer only. Ask it something with curl:
curl -s http://127.0.0.1:8340/mcp -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"state_overview","arguments":{"state":"RI"}}}'From files on disk instead of clinx.org. Set CLINX_DATA_DIR to a folder that holds
340b-state-laws.json, 340b-bills.json, 340b-notices.json and 340b-events.json.
What is in this folder
File | What it does |
| The server itself: reads one message, writes one answer. |
| The nine tools: what each takes and how it answers from the tables. |
| Fetches the four public files and keeps them for an hour. |
| Reads the four files from a folder instead, for a program on your own computer. |
| Describes a request by kind, for a host that wants to count what is asked. See below. |
| The door for a helper program on your own computer. |
| The door for the web. One request in, one answer out, nothing remembered. |
| Runs the web door on your own computer. |
| The web door shaped for an edge host that runs it by itself. Not deployed: clinx.org serves the same door from the site's own program (clinx-org, |
| The shapes of the pieces above, for a host written in TypeScript. |
| The tests, and small real slices of the four tables ( |
Which versions of the protocol it speaks
MCP changed shape in its revision of 28 July 2026. Before it, a client opened with a handshake
(initialize) and the two sides agreed a version once. Since it, there is no handshake: every
request names its version, and a client can ask server/discover what a server speaks.
Both kinds of client are in use, so the server answers both: the 2026-07-28 revision, and the older 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05. A request that names the newer version is answered the newer way. Everything else is answered the older way.
On 15 November 2026 Claude Code 2.1.306 was pointed at the server. It opened with
server/discover, was told 2026-07-28, and listed the tools (seven then, nine now). Those exact messages are now
one of the tests. A whole question asked through an assistant, start to finish, has not been
tried yet; nor has any other client.
Safety and privacy
Read-only. No tool changes anything anywhere.
Nothing about the asker is kept. No log of questions, no cookies, no sessions, no sign-in. Run on your own computer, the server counts nothing at all.
It cannot be turned on another site. The only addresses it ever fetches are the four table files on clinx.org, at most once an hour, whatever it is asked.
Small requests only. The web door takes
POSTwith JSON, up to 64 KB, and nothing else.On your own computer it listens on
127.0.0.1only and refuses calls from web pages that are not on that computer, so a page you visit cannot reach it.If clinx.org cannot be reached, a tool says so. If a refetch fails, the copy already held is still served.
Counting what is asked, without knowing who asked
Whoever hosts the server for others will want to know which questions people bring to it, so
the work goes where it is used. The web door can hand a host a short description of each
request (counted, in src/http.js). The server keeps nothing itself; the host decides where
the descriptions go.
A description has eight fields and never more:
Field | Example | What it is |
|
| The kind of request. |
|
| The tool called, if one was. |
|
| Answered, a mistake in what was asked, refused, or the tables could not be reached. |
|
| The state asked about, |
|
| The filters used, by name. |
|
| The public row a "get" tool found. |
|
| The name the assistant program gives itself. |
|
| The protocol version it asked for. |
What is left out matters more than what is kept:
Never the words. Search words, dates and anything else typed freely are not kept. A filter is kept by name only (
text), and its value only when it is one of the tool's own listed choices (kind=contract-pharmacy).Never the asker. No internet address, no browser or device description, nothing that could tell one asker from another.
A looked-up id comes from the answer, not from what was typed: it is a public row the server found and gave back.
A client's name is cut down to plain letters and forty characters.
test/usage.test.js checks each of these with a made-up name, number and email address typed
into every field, and fails if any of it comes out the other side.
The copy at clinx.org/mcp is counted this way and no other. The site's Privacy page says the same to its readers.
Tests
npm test # 45 tests, no network
npm run test:live # one more, against the published tables at clinx.orgThe tests cover both protocol eras, every tool, every kind of mistaken input, what a host is told about a request and what it is not, the helper program started and driven as an app would drive it, and the web door both as a function and as a real server on a local port.
What is not done
It is not published as a package, so there is no one-line install.
It answers from the state law, bills, federal notices and calendar tables only. The 340B scorecards and the registry tables are not offered yet.
Federal notices go back to January 2025. Court cases, and which drug makers an agency has approved for the rebate pilot, are not in the tables.
Hearings appear once a legislature posts an agenda that names a listed bill. In November 2026, with most legislatures out of session, there are none.
Licence
The code is under the MIT licence. The tables it reads are under Creative Commons Attribution 4.0; credit them as "ClinX, clinx.org, retrieved , CC BY 4.0".
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
DEA registration & controlled-substance authority tracking for prescribers — read-only demo.
Read-only tools: EMS protocols, courts and judges, NPI and FDA data, GPU fit for open models.
U.S. law library for AI: court decisions, statutes, court rules and citation checks. Read-only.
Government contracts, business registration, FDA recalls and product-price data as agent tools.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to access Washington State Legislature data for bill tracking, committee meetings, legislator lookup, and legislative document retrieval via conversational interfaces.91MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to query U.S. legislative data, including jurisdictions, legislators, and bills, via the OpenStates API.1-
- AlicenseNot gradedqualityDmaintenanceEnables querying US regulated-care providers (GLP-1 clinics) with tools for searching, retrieving details, and checking compliance, using natural language or function calls.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to pull the full text of any state statute by citation, and to search official section catchlines by topic or keyword to find matching citations. Keyless, and handles citation suffixes such as "12.1-16-01" or "47-16-13.1".331 npmMIT