Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/carefeed

NPM · @RENETURCIOS/CAREFEED · 2 COMPONENTS

Healthcare provider registry lookup, new OIG-LEIE exclusions feed, FDA enforcement actions.

71 Trust /100

Last scanned (20 hours ago)

Scores higher than 42% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 272 tokens (~90/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@reneturcios/carefeed@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~272 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fda_enforcement ~53

Return recent FDA enforcement/recall actions tied to a device/drug firm (openFDA). A manufacturer-risk layer for procurement and payor teams.

NameTypeReqDescription
firmstringyesRecalling firm / manufacturer name.

No output schema declared.

No examples provided.

new_exclusions ~65

Return providers newly added to the OIG-LEIE exclusion list, optionally scoped by state and/or specialty. The credentialing / payment-integrity alert feed.

NameTypeReqDescription
limitnumber–Default 60.
specialtystring––
statestring––

No output schema declared.

No examples provided.

provider_lookup ~154

Look up US healthcare providers from the public CMS NPPES registry by NPI, or search by specialty + state (+ optional name/city). Returns NPI, name, specialty, license, location, and an OIG-LEIE exclusion flag on each. Public data only — no PHI.

NameTypeReqDescription
citystring––
limitnumber–Max results (default 50).
namestring–Provider or organization name substring.
npistring–Exact 10-digit NPI for a single provider.
specialtystring–Taxonomy/specialty, e.g. 'Cardiology'.
statestring–Two-letter state, e.g. 'TX'.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/carefeed MCP server?

io.github.CloudCorpRecords/carefeed runs locally as an npm package, launched with npx -y @reneturcios/carefeed mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/carefeed

# add to Claude Code
claude mcp add cloudcorprecords-carefeed -- npx -y @reneturcios/carefeed mcp
Common questions

What is the io.github.CloudCorpRecords/carefeed MCP server?

io.github.CloudCorpRecords/carefeed is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/carefeed. Healthcare provider registry lookup, new OIG-LEIE exclusions feed, FDA enforcement actions. This page covers its npm package (@reneturcios/carefeed).

Is the io.github.CloudCorpRecords/carefeed MCP server safe to use?

io.github.CloudCorpRecords/carefeed scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.CloudCorpRecords/carefeed MCP server expose?

io.github.CloudCorpRecords/carefeed exposes 3 tools: provider_lookup, new_exclusions, fda_enforcement. Their descriptions and schemas cost roughly 272 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/carefeed MCP server still maintained?

io.github.CloudCorpRecords/carefeed is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/carefeed MCP server under?

io.github.CloudCorpRecords/carefeed declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.CloudCorpRecords/carefeed MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/carefeed, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.