Meridian Trace MCP MCP server

An official MCP server providing access to medical device registration data from 36 national registries. It enables agents to resolve company names across markets, check regulatory coverage gaps, find local distributors, and analyze risk classifications for global expansion planning.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Meridian Trace

MCP endpoint (Streamable HTTP)

https://meridiantrace.com/v1/mcp

Vendor documentation

What you can do with it

Resolve manufacturer names across different national registries
Check market coverage gaps for specific medical devices
Find local distributors and importers in target markets
Analyze risk classification differences across jurisdictions

Tools advertised by the last live check:

search_manufacturer
get_registrations
get_registration
get_license_holders
find_distributors
get_market_coverage
get_registration_timeline
find_predicates
classify_device
find_similar_devices
get_recent_registrations
get_coverage

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http meridian-trace-mcp https://meridiantrace.com/v1/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add meridian-trace-mcp --url https://meridiantrace.com/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable meridian-trace-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "meridian-trace-mcp": {
      "url": "https://meridiantrace.com/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "meridian-trace-mcp": {
      "type": "streamableHttp",
      "url": "https://meridiantrace.com/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start meridian-trace-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "meridian-trace-mcp": {
      "type": "http",
      "url": "https://meridiantrace.com/v1/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http meridian-trace-mcp https://meridiantrace.com/v1/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "meridian-trace-mcp": {
      "url": "https://meridiantrace.com/v1/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "meridian-trace-mcp": {
      "serverUrl": "https://meridiantrace.com/v1/mcp"
    }
  }
}

See all 1,583

Do you run Meridian Trace MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing