mcp-registry/com.meridiantrace/medical-device-registrations · v1.0.0
As of 2026-10-26 10:52 UTC, the Meridiantrace Medical Device Registrations MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 95.1% of Glimind's liveness checks. It had 33 outages in 90 days, with a median recovery of 25.8 hours.
Medical device registrations across 25 markets: coverage gaps, 510(k) predicates, classification
Point your MCP client at this streamable-http endpoint: https://meridiantrace.com/v1/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
14 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Reachable 95.1% of the time over the last 30 days; median recovery 1550 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.meridiantrace%2Fmedical-device-registrations/fixes
{
"name": "check_issue",
"description": "Where a report you filed with report_data_issue stands — Received, Looking into it, Fixed, Not changing or Already reported (with the reference it repeats) — and Meridian's reply, if any. Only the API key that filed a report (or another key on the same account) can read it. Needs an API key.",
"inputSchema": {
"type": "object",
"required": [
"ref"
],
"properties": {
"ref": {
"type": "string",
"description": "The reference report_data_issue returned, e.g. MT-1042"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_distributors",
"description": "RUNS WITHOUT AN API KEY (anonymous callers see the top 3 per market and are told how many more matched). WHO COULD SELL A DEVICE IN A MARKET — the question a company entering a market actually has. Give it a market and, optionally, a device type or clinical area; it returns the local distributors and importers who hold registrations there, what clinical areas they cover, how many markets they operate in, and a sample of the lines they already carry. Strongest across Asia, where the registry name",
"inputSchema": {
"type": "object",
"required": [
"market"
],
"properties": {
"limit": {
"type": "number",
"description": "1-25 (default 10). Capped to 3 without a paid key."
},
"market": {
"type": "string",
"description": "ISO2 code or market name, e.g. \"TH\" or \"Thailand\". One market per call."
},
"device_type": {
"type": "string",
"description": "Optional clinical area or device category in plain words, e.g. \"orthopaedic implants\", \"in vitro diagnostics\", \"cardiology\". Partial matches count. Omit it to see the whole channel in that market."
},
"holder_basis": {
"enum": [
"all",
"registrations",
"licence_or_tender_only"
],
"type": "string",
"description": "Which distributors to LIST (counts always report both): \"all\" (default; registered holders rank first), \"registrations\" (hold registrations here), or \"licence_or_tender_only\" (known from a licence list or tender award, no registrations of their own in our data)."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_predicates",
"description": "US 510(k) predicate lineage, from the predicates actually cited in each clearance's own summary document — not a similarity guess. 64,567 clearances, 1992-2026. By k_number: what that device cited, AND which later devices cited IT as a predicate — the reverse direction shows whose clearances rest on your device and how contested a space is. By product_code: the predicates that code leans on most, ranked by how often they are cited, plus recent clearances. Use when choosing a predicate, assessing",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "number",
"description": "Max rows per list (default 20, max 50)"
},
"k_number": {
"type": "string",
"description": "A 510(k) number, e.g. \"K191275\""
},
"product_code": {
"type": "string",
"description": "An FDA product code, e.g. \"LIT\""
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.meridiantrace/medical-device-registrations"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.meridiantrace/medical-device-registrations"}) over MCP.
report_data_issue ~443 tokensfind_distributors ~404 tokensget_registrations ~380 tokensget_registration_timeline ~314 tokensget_market_coverage ~312 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.meridiantrace%2Fmedical-device-registrations?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.meridiantrace%2Fmedical-device-registrations?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.meridiantrace%2Fmedical-device-registrations.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.meridiantrace%2Fmedical-device-registrations.svg :target: https://glimind.com/server/mcp-registry%2Fcom.meridiantrace%2Fmedical-device-registrations?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a939ea64c4ba9963…, first seen 2026-10-17, included at leaf 10435 of 75,557. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable search servers · most reliable database servers · most reliable data servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 10:52 UTC, the Meridiantrace Medical Device Registrations MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 95.1% of Glimind's liveness checks. It had 33 outages in 90 days, with a median recovery of 25.8 hours.
Meridiantrace Medical Device Registrations MCP server advertises 14 tools, including check_issue, classify_device, find_distributors, find_predicates, find_similar_devices.
Point your MCP client at this streamable-http endpoint: https://meridiantrace.com/v1/mcp
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.