Canada Medical Device Licences MCP server
io.github.donniertf-hub/ca-medical-devices-mcpdonniertf-hubstreamable-httpv1.0.0Scanned
Is this medical device licensed in Canada? Search Health Canada MDALL and verify licences.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Canada Medical Device Licences MCP server can do
The Canada Medical Device Licences MCP server is published by the GitHub account donniertf-hub. It has 4 tools. It can create or change data (2 tools: licence_detail and batch_licence_check), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 11, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
batch_licence_checkPRO.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it PRO. Check up to 50 licence numbers for current validity.
licence_detailPRO.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it PRO. Licence details for an original licence number: name, device class, licence type and company.
Only reads 2Show 2 read-only tools
device_searchFREE.No findings
Why it is in this group
- The name "device_search" says "search": a word for reading.
Description, as the server wrote it FREE. Find Health Canada-licensed medical devices by trade name — licence number, first licensed, end date. Top 5.
device_search_fullPRO.No findings
Why it is in this group
- The name "device_search_full" says "search": a word for reading.
Description, as the server wrote it PRO. All licensed devices matching a trade name (up to 200), with active/expired flag.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:29 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 429
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 429.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ca-medical-devices https://ca-medical-devices-mcp.donniertf.workers.dev/mcpclaude mcp add --transport http ca-medical-devices https://ca-medical-devices-mcp.donniertf.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ca-medical-devices__device_search",
"mcp__ca-medical-devices__device_search_full"
],
"ask": [
"mcp__ca-medical-devices__licence_detail",
"mcp__ca-medical-devices__batch_licence_check"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ca-medical-devices. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.donniertf-hub/ca-medical-devices-mcp/verify?hash=6388ffc0d6d18e92c1716510ea304335dd6c8ca3bacd138381f5ad9e71fc4585" | jq -e '.changed == false'Pinned hash 6388ffc0d6d1, from Nov 11, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.donniertf-hub/ca-medical-devices-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.donniertf-hub/ca-medical-devices-mcp)Source: MCP Registry · repository. Synced Oct 29, 2026, 22:17 UTC.
Canada Medical Device Licences MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Canada Medical Device Licences MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Canada Medical Device Licences MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Canada Medical Device Licences MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Canada Medical Device Licences MCP server have?
- 4 tools: 2 write, 2 read. licence_detail, batch_licence_check, device_search and device_search_full.
Does the Canada Medical Device Licences MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Canada Medical Device Licences MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Canada Medical Device Licences MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.