deawatch MCP server
us.artificl/deawatchartificl.usstreamable-httpv1.0.0Scanned
DEA registration & controlled-substance authority tracking for prescribers — read-only demo.
5 tools: 1 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- 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 deawatch MCP server can do
The deawatch MCP server is published by artificl.us, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: export_registration_report), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (get_authority_summary).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 5, 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.
5 tools
Changes things 1Claude Code: ask
export_registration_reportExport the full controlled substance registration report as CSV text (prescriber, registration, expiry, status, reminder history).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 Export the full controlled substance registration report as CSV text (prescriber, registration, expiry, status, reminder history).
Only reads 4Show 4 read-only tools
get_authority_summaryGet the controlled substance authority summary: totals for tracked registrations, renewals not started, expired, due in 30 days, and awaiting issue.Reads text others writeNo findings
Why it is in this group
- The name "get_authority_summary" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "issue": it reads issues, which other people can write.
Description, as the server wrote it Get the controlled substance authority summary: totals for tracked registrations, renewals not started, expired, due in 30 days, and awaiting issue.
get_registrations_expiringList controlled substance registrations expiring within the next N days (default 90), including state CSRs and mid-level registrations.No findings
Why it is in this group
- The name "get_registrations_expiring" says "get": a word for reading.
Description, as the server wrote it List controlled substance registrations expiring within the next N days (default 90), including state CSRs and mid-level registrations.
list_cannot_prescribeList prescribers whose DEA registration or state controlled substance license has expired — the practitioners who cannot legally write controlled prescriptions right now.No findings
Why it is in this group
- The name "list_cannot_prescribe" says "list": a word for reading.
Description, as the server wrote it List prescribers whose DEA registration or state controlled substance license has expired — the practitioners who cannot legally write controlled prescriptions right now.
search_registrationsSearch controlled substance registrations by prescriber name, registration type, or location.No findings
Why it is in this group
- The name "search_registrations" says "search": a word for reading.
Description, as the server wrote it Search controlled substance registrations by prescriber name, registration type, or location. Returns matching records with expiry date and status.
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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:20 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
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://deawatch.artificl.us/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata
- https://deawatch.artificl.us/.well-known/oauth-protected-resource
- Authorization servers
- https://deawatch.artificl.us
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Posture changes
- Nov 20, 2026
- Authorization servers: none to https://deawatch.artificl.us
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://deawatch.artificl.us/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: none to https://deawatch.artificl.us/.well-known/oauth-protected-resource
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. Authorization servers: none -> https://deawatch.artificl.us; Dynamic client registration: not observed -> yes; Client ID metadata documents: not observed -> no.View diff
- Authorization servers: none to https://deawatch.artificl.us
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 4 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://deawatch.artificl.us/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: none to https://deawatch.artificl.us/.well-known/oauth-protected-resource
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http deawatch https://deawatch.artificl.us/mcpclaude mcp add --transport http deawatch https://deawatch.artificl.us/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__deawatch__search_registrations",
"mcp__deawatch__list_cannot_prescribe",
"mcp__deawatch__get_registrations_expiring",
"mcp__deawatch__get_authority_summary"
],
"ask": [
"mcp__deawatch__export_registration_report"
],
"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 deawatch. Review it before you use it.
Capability tags behind 1 rule
- mcp__deawatch__get_authority_summary untrusted-input
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/us.artificl/deawatch/verify?hash=97269e1e22f1759f2b09f00390bfe474a861ba1b4c4df1f8accfcab804b2afef" | jq -e '.changed == false'Pinned hash 97269e1e22f1, from Nov 5, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/us.artificl/deawatch/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/us.artificl/deawatch)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
deawatch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the deawatch MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 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 deawatch MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the deawatch 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 deawatch MCP server have?
- 5 tools: 1 write, 4 read. export_registration_report, search_registrations, list_cannot_prescribe, get_registrations_expiring and get_authority_summary.
Does the deawatch MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the deawatch MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the deawatch MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 5, 2026.