Skip to content
Medrecpro logo

Medrecpro

Imports DailyMed SPL zip files into a database, then serves them through a REST API, MCP server and label renderer.

DataAPIOpen sourceFor developers
medrecpro.com ↗
At a glanceswept 2026-10-12

≈ 2visits/mo

Little sign of use · estimate, read 2026-10-12

For
Pharmaceutical professionals managing FDA structured product label (SPL) data for drug labels
Price
Price not read
Activity
Activity not read yet
Company
Domain since 2013domain registered
Runs as
API
AlternativesSet it up for my teamIs Medrecpro yours? Claim the card →
What people do with it
  • import DailyMed SPL zip files and normalize their data
  • search drug products by NDC code or ingredient
  • generate valid SPL XML from database records
The companyeach fact with its source · read 2026-10-13
  • Domain since2013domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP servercom.medrecpro/drug-label-serververified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-13
  • Address to connectwww.medrecpro.com/mcp
  • API docsmedrecpro.com/api/swagger/index.htmlthe vendor's page ↗

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Databy use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Data tools →

Questions this page answers
  • What is Medrecpro?

    Imports DailyMed SPL zip files into a database, then serves them through a REST API, MCP server and label renderer. It is listed in the Atlas under Data.

  • Who is Medrecpro for?

    Pharmaceutical professionals managing FDA structured product label (SPL) data for drug labels

  • Do people use Medrecpro?

    Little sign of use: ≈ 2 visits/mo · estimate, 2026-10.

  • What are alternatives to Medrecpro?

    In Data, by use: MCP-Builder.ai, Hugging Face, Ultimaps, Agenty, Apify, xMap POI Data.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.