
carefeed
io.github.CloudCorpRecords/carefeed
Healthcare provider registry lookup, new OIG-LEIE exclusions feed, FDA enforcement actions.
Documentation
carefeed
Who is a provider, who just landed on the federal exclusion list, and what has the FDA pulled lately for a given manufacturer? carefeed is a local forwarding client for the hosted health-intel MCP service: it answers tools/list locally from the captured tool definitions and forwards every call to the service, returning the answers exactly as the service sends them back.
The three tools all read published material. provider_lookup searches the public CMS NPPES registry and returns the registry records as published — NPI, name, specialty, license, location, and each record's own published OIG-LEIE exclusion flag field. new_exclusions is the feed of providers newly added to the OIG-LEIE exclusion list, scopable by state and specialty. fda_enforcement returns recent FDA enforcement and recall actions tied to a device or drug firm from openFDA. The upstream capture states "Public data only — no PHI", and there is no patient data anywhere in this surface.
Labelled subset — 3 of the 4 captured tools are built. The captured screen_exclusion tool is omitted on safety grounds: it screens a caller-named provider or organization against the HHS-OIG LEIE and SAM.gov exclusion lists and returns findings about that named subject. Caller-named exclusion screening is not built here, so screen_exclusion is not registered, does not appear in tools/list, and is not a CLI command. The kept tools are register and feed reads: they return published records, not a screening verdict computed about a named subject.
The tools
provider_lookup— Look up US healthcare providers in the public CMS NPPES registry by exactnpi, or search byspecialtyplusstatewith optionalnameandcitysubstrings;limitcaps the rows (default 50). No required parameters.new_exclusions— Providers newly added to the OIG-LEIE exclusion list, optionally scoped bystateand/orspecialty;limitcaps the rows (default 60). No required parameters.fda_enforcement— Recent FDA enforcement/recall actions tied to a device/drug firm (openFDA).firm, the recalling firm or manufacturer name, is required.
Install and run
As an MCP server via npm:
npx -y @reneturcios/carefeed mcp
MCP client configuration:
{
"mcpServers": {
"carefeed": {
"command": "npx",
"args": ["-y", "@reneturcios/carefeed", "mcp"]
}
}
}
As a container:
docker run -i ghcr.io/cloudcorprecords/carefeed
docker run --rm ghcr.io/cloudcorprecords/carefeed new_exclusions '{}'
CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
carefeed provider_lookup '{"specialty":"Cardiology","state":"TX"}'
carefeed new_exclusions '{"state":"CA","limit":10}'
carefeed fda_enforcement '{"firm":"Medtronic"}'
carefeed --version
Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand (including the omitted screen_exclusion) or a malformed JSON argument.
Configuration
HEALTHINTEL_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://health.dropwatchhq.com/mcp. (The override variable is a reconstruction added by this rebuild.)
The upstream registry record declares no headers, so no authentication header is ever sent; the tool surface was captured keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with carefeed error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
The test suite checks the served tool list against the captured surface (the 3 kept tools, deep-equal, in order, with no titles invented and no required key added to the two tools that carry none), asserts the omitted screen_exclusion tool is absent at registry, MCP and CLI level, exercises the session handshake and its reuse, verifies that no Authorization header is ever sent under any environment, and verifies that arguments go upstream untouched and results come back untouched.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
@reneturcios/carefeednpm install @reneturcios/carefeedghcr.io/cloudcorprecords/carefeed:0.1.0docker pull ghcr.io/cloudcorprecords/carefeed:0.1.0:undefinedRelated Servers
io.github.CloudCorpRecords/abandoncheck
Judge whether a dependency is maintained, from factual signals: releases, commits, archival.
io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
io.github.CloudCorpRecords/actionpin
GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.