regulatory-deadline
NPM · @WEISEER/REGULATORY-DEADLINE-MCP · SCANNED SEP 20
FinCEN/SEC/EU AI Act/GDPR deadline tracker for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 113 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 163 tokens (~40/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the regulatory-deadline MCP server?
regulatory-deadline runs locally as an npm package, launched with npx -y @weiseer/regulatory-deadline-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @weiseer/regulatory-deadline-mcp
claude mcp add weiseer-regulatory-deadline -- npx -y @weiseer/regulatory-deadline-mcp
{
"mcpServers": {
"weiseer-regulatory-deadline": {
"command": "npx",
"args": [
"-y",
"@weiseer/regulatory-deadline-mcp"
]
}
}
} {
"servers": {
"weiseer-regulatory-deadline": {
"command": "npx",
"args": [
"-y",
"@weiseer/regulatory-deadline-mcp"
]
}
}
} codex mcp add weiseer-regulatory-deadline -- npx -y @weiseer/regulatory-deadline-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"weiseer-regulatory-deadline": {
"type": "local",
"command": [
"npx",
"-y",
"@weiseer/regulatory-deadline-mcp"
],
"enabled": true
}
}
} openclaw mcp add weiseer-regulatory-deadline --command npx --arg -y --arg @weiseer/regulatory-deadline-mcp
mcp_servers:
weiseer-regulatory-deadline:
command: "npx"
args: ["-y", "@weiseer/regulatory-deadline-mcp"] {
"McpServers": {
"weiseer-regulatory-deadline": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@weiseer/regulatory-deadline-mcp"
]
}
}
} assistant mcp add weiseer-regulatory-deadline -t stdio -c npx -a -y @weiseer/regulatory-deadline-mcp
{
"mcpServers": {
"weiseer-regulatory-deadline": {
"command": "npx",
"args": [
"-y",
"@weiseer/regulatory-deadline-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@weiseer/regulatory-deadline-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_deadline ~35
Full record for one deadline — cited statute/rule URL, scope, who-applies.
| Name | Type | Req | Description |
|---|---|---|---|
| deadline_id | string | yes | – |
No output schema declared.
No examples provided.
list_by_jurisdiction ~35
All tracked deadlines for a jurisdiction (us-federal, eu, uk, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | – |
No output schema declared.
No examples provided.
search_by_keyword ~34
Full-text search across title/summary/regime. Useful for ad-hoc compliance queries.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
No output schema declared.
No examples provided.
upcoming_deadlines ~59
Upcoming regulatory deadlines within N days. Filter by jurisdiction/regime.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | – |
| regime | string | – | e.g. ai-act, gdpr, sec, fincen-boi |
| within_days | number | – | – |
No output schema declared.
No examples provided.
What is the regulatory-deadline MCP server?
regulatory-deadline is an MCP server listed in the public MCP registry as io.github.weiseer/regulatory-deadline. FinCEN/SEC/EU AI Act/GDPR deadline tracker for AI agents. This page covers its npm package (@weiseer/regulatory-deadline-mcp).
Is the regulatory-deadline MCP server safe to use?
regulatory-deadline scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the regulatory-deadline MCP server expose?
regulatory-deadline exposes 4 tools: upcoming_deadlines, get_deadline, list_by_jurisdiction, search_by_keyword. Their descriptions and schemas cost roughly 163 tokens of context every time the server is loaded.
Is the regulatory-deadline MCP server still maintained?
regulatory-deadline is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the regulatory-deadline MCP server under?
regulatory-deadline declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.