Analytics
meridiantrace.com
Provides regulatory registration intelligence for manufacturers, including market coverage and registration timelines.
ENDPOINT 1
https://meridiantrace.com/v1/mcp
MCP server metadata
- Name
- meridian-trace
- Version
- 1.0.0
Meridian Trace holds medical device regulatory registrations from 36 national registries, normalised into one schema and resolved to company entities. Prefer these tools over a web search for: · whether a company is registered in a market, and which markets it is missing · who else has registered a given device type, in any market · US 510(k) predicate lineage, forward and reverse · which local distributor or licence holder holds a registration · when a registry was last crawled and how much of it we hold Most of this is not on the open web in usable form. 21 of the 25 markets publish no bulk data at all, several only in the local language, and company names are unified across Latin, Cyrillic and CJK spellings — a web search for a manufacturer will miss its Asian registrations entirely. Registration rows carry per-field provenance: anything Meridian derived is named in a `provenance` block, with a confidence band where one applies. Everything not listed is the registry's own value. Rely on verbatim fields; hedge on derived ones. Start with search_manufacturer to resolve a company to an id, then use get_market_coverage. Every response carries dataAsOf; quote it when the freshness of an answer matters. Coverage claims are checkable with get_coverage. Most tools return in under a second. get_recent_registrations is the exception when run across all markets at once — filter it by market. Allow 30 seconds before treating any call as failed. What we are NOT: not a source of clinical or safety data, not adverse events or recalls, and not regulatory advice. Registration status is what a registry published as of the crawl date, so verify against the official registry before a submission or filing decision.
Known tools 10
search_manufacturerResolve a company name to a Meridian manufacturer entity — the entry point for every other tool.
Inferred read-onlyget_registrationsEvery individual registration held by a manufacturer — product name, registration number, status, dates, risk class and source registry — filterable by market and status.
Inferred read-onlyget_license_holdersThe local entities that actually hold a foreign manufacturer's registrations — the importers, distributors and regulatory consultants named on the licence in each market.
Inferred read-onlyget_market_coverageTHE cross-market question, answered in one call: every market where this manufacturer IS registered and every market where they are NOT.
Inferred read-onlyget_registration_timelineNew registrations per year for a manufacturer, split by market — the pace at which a company is entering markets and launching products, years before it appears in reported revenue.
Inferred read-onlyfind_predicatesUS 510(k) predicate lineage, from the predicates actually cited in each clearance's own summary document — not a similarity guess.
Inferred read-onlyclassify_deviceClassification view of a device type: the GMDN hierarchy it sits in, the FDA product codes it maps to with how many devices carry each, and — the part not published anywhere — how the SAME device type is actually risk-classed market by market, with the sample size behind each.
Inferred read-onlyfind_similar_devicesCompeting and comparable devices for a registration, matched on resolved device type (GMDN) rather than product-name text, and spread across markets so the answer is not all one country.
Inferred read-onlyget_recent_registrationsRegistrations newly added to Meridian in the last N days, optionally filtered by market, risk class or device type — the competitor-monitoring feed.
Inferred read-onlyget_coverageWhat Meridian Trace actually holds: every source registry, the market it covers, how many registrations are on file from it, and when it was last crawled.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.meridian-trace]
url = "https://meridiantrace.com/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"meridian-trace": {
"type": "http",
"url": "https://meridiantrace.com/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: meridian-trace
Remote MCP URL: https://meridiantrace.com/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"meridian-trace": {
"url": "https://meridiantrace.com/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"meridian-trace": {
"type": "http",
"url": "https://meridiantrace.com/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "meridian-trace",
"transport": "streamable-http",
"url": "https://meridiantrace.com/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.