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/fdarecords

NPM · @RENETURCIOS/FDARECORDS · 2 COMPONENTS

openFDA identifier resolution: drug labels and applications, device submissions, classification.

69 Trust /100

Last scanned (3 hours ago)

Scores higher than 36% 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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 315 tokens (~45/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 54

    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 5 Nov 2026 · Analysed npm/@reneturcios/fdarecords@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 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~315 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
classify_device_product_code ~34

Device product code to device class and medical specialty.

NameTypeReqDescription
product_codestringyesThe product code for this call.

No output schema declared.

No examples provided.

lookup_device_submission ~54

510(k)/De Novo/PMA submission number to device record (K or DEN number, P number; HDE numbers are not in openFDA).

NameTypeReqDescription
submission_numberstringyesThe submission number for this call.

No output schema declared.

No examples provided.

lookup_drugsfda_application ~39

Drugs@FDA record for an NDA/BLA/ANDA number.

NameTypeReqDescription
application_numberstringyesThe application number for this call.

No output schema declared.

No examples provided.

resolve_drug_to_application ~31

Brand or generic name to application number(s).

NameTypeReqDescription
namestringyesName for this call.

No output schema declared.

No examples provided.

screen_for_rwe_signals ~62

Experimental, unvalidated sweep of drug labels for real-world-evidence signals; hits are candidates for human review, not findings.

NameTypeReqDescription
limitinteger–Maximum number of results to return (optional).
querystring–Search query text.

No output schema declared.

No examples provided.

search_drug_label ~58

Search SPL label text, optionally scoped to a section.

NameTypeReqDescription
limitinteger–Maximum number of results to return (optional).
querystringyesSearch query text.
sectionstring–The section for this call.

No output schema declared.

No examples provided.

validate_device_application ~37

Full chain: submission number to device class, medical specialty and category.

NameTypeReqDescription
submission_numberstringyesThe submission number for this call.

No output schema declared.

No examples provided.

Install

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

io.github.CloudCorpRecords/fdarecords runs locally as an npm package, launched with npx -y @reneturcios/fdarecords. 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/fdarecords

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

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

io.github.CloudCorpRecords/fdarecords is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/fdarecords. openFDA identifier resolution: drug labels and applications, device submissions, classification. This page covers its npm package (@reneturcios/fdarecords).

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

io.github.CloudCorpRecords/fdarecords scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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/fdarecords MCP server expose?

io.github.CloudCorpRecords/fdarecords exposes 7 tools: search_drug_label, lookup_drugsfda_application, resolve_drug_to_application, screen_for_rwe_signals, lookup_device_submission, and 2 more. Their descriptions and schemas cost roughly 315 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/fdarecords is still listed as active in the MCP registry. We last reached this channel on 5 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/fdarecords MCP server under?

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