Medical device registration data from 36 national registries, callable over the Model Context Protocol. Free developer key, no card.
Meridian Trace speaks the Model Context Protocol over HTTP. Point any MCP-capable client at the endpoint and authenticate with an API key. Get one at meridiantrace.com/api โ the Developer tier is free, needs no card, and includes 100 calls a month.
{ "mcpServers": { "meridian-trace": { "url": "https://meridiantrace.com/v1/mcp", "headers": { "X-API-Key": "mt_your_key_here" } } } }
The transport is JSON-RPC 2.0 over HTTP POST. Call initialize for server instructions, then tools/list. Agents can also read /llms.txt.
initialize
tools/list
Most of this data is not on the open web in usable form, and the parts that are will mislead you.
21 of our 25 markets publish no bulk data at all. India, Brazil, Japan, Korea, Taiwan, China, Indonesia, Russia, Thailand, Vietnam, Saudi Arabia, Malaysia, Colombia, the Philippines and Israel are reachable only by scraping a registry, several of them local-language only. The US, EU, Canada and Australia have open bulk sources; the other 1.25 million records do not.
Company names do not match across markets. The same manufacturer appears as "Medtronic", "ะะตะดััะพะฝะธะบ" and "็พๆฆๅ" depending on the registry. Meridian unifies them, and rolls subsidiaries up to the parent that owns them. A web search for a manufacturer misses its Asian registrations entirely, and โ worse โ returns nothing rather than an error, so the answer looks complete.
In Malaysia, Indonesia and Thailand the registry names the local licence holder, not the manufacturer. Read those registries literally and you will attribute a product to its distributor. Meridian infers the actual OEM on 94,229 records and marks the inference.
An example of what that produces: 62% of device types carry a different risk class depending on the market — a comparison no single registry publishes, because it is not any one registry's fact.
search_manufacturer
get_market_coverage
get_registrations
get_license_holders
find_predicates
find_similar_devices
classify_device
get_registration_timeline
get_recent_registrations
get_coverage
Coverage and freshness are the two things you cannot take on trust from a data provider, so both are queryable. get_coverage returns all 36 registries with a record count and a last-crawled date. Every other response carries a dataAsOf stamp. Registration records refresh on each registry crawl; manufacturer profiles rebuild weekly.
dataAsOf
Where history is concerned, get_registration_timeline labels each market. The US and EU never remove a record, so those series are complete. Taiwan, Thailand, Canada and Japan retain lapsed registrations, so entries and exits are both real. The remaining markets publish only today's position โ a trend built from them slopes upward purely because withdrawn products are missing from the past, and the flag says so rather than letting you find out later.
Not clinical or safety data. No adverse events, recalls or field safety notices. Not regulatory advice. Registration status is what a registry published as of the crawl date โ while we work to keep it complete, source registries occasionally publish incomplete records, and anything informing a submission or filing decision should be verified against the official registry.
Developer access is free and self-serve: 100 calls a month, one key, no card. Paid plans raise call volume and key count. See meridiantrace.com/api for plans and to issue a key, or write to hello@meridiantrace.com.