MCP.Market

regulatory-deadline MCP server

by weiseer·io.github.weiseer/regulatory-deadline·v0.1.1
No reviews yet

FinCEN/SEC/EU AI Act/GDPR deadline tracker for AI agents.

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed regulatory-deadline yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

regulatory-deadline tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_deadline

    Full record for one deadline — cited statute/rule URL, scope, who-applies.

  • list_by_jurisdiction

    All tracked deadlines for a jurisdiction (us-federal, eu, uk, etc.).

  • search_by_keyword

    Full-text search across title/summary/regime. Useful for ad-hoc compliance queries.

  • upcoming_deadlines

    Upcoming regulatory deadlines within N days. Filter by jurisdiction/regime.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 118 days ago8/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How regulatory-deadline compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 4 read

Install regulatory-deadline in Claude Code, Cursor or VS Code

Runs npx -y @weiseer/regulatory-deadline-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add regulatory-deadline -- npx -y @weiseer/regulatory-deadline-mcp
Add to Cursor

What the publisher says

From the regulatory-deadline repository's README, as published. We do not edit it. Read it on GitHub

@weiseer/regulatory-deadline-mcp

FinCEN/SEC/EU AI Act/GDPR deadline tracker for AI agents. stdio MCP server.

Part of weiseer — AI-agent-native cached oracles.

Install

npm install -g @weiseer/regulatory-deadline-mcp

Use with Claude Desktop / Cursor / Cline / Continue / Windsurf

{
  "mcpServers": {
    "regulatory-deadline": {
      "command": "npx",
      "args": ["-y", "@weiseer/regulatory-deadline-mcp"]
    }
  }
}

Why use this instead of your agent doing it itself

The DIY cost in token-spend, latency, and rate-limit risk is 100-1500x our cost. See the weiseer organization README for the economic argument.

Environment

  • REG_URL — override remote snapshot URL
  • REGLOCALONLY=1 — skip remote fetch

License

Apache-2.0

Nothing above is checked by us. What we check is on the safety report.

regulatory-deadline: common questions

Is regulatory-deadline MCP server safe?
Mostly: it is graded B (78/100). Read the regulatory-deadline safety report
How do I install regulatory-deadline?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does regulatory-deadline need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is regulatory-deadline maintained?
The last commit was 156 days ago (2026-06-01). The latest release is v0.1.1.
How does regulatory-deadline compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from weiseer →