regintel-mcp@0.6.1
VERIFIED· not startedPublisher claims: "Drop-in regulatory data for your Claude / LLM agent. Query GDPR, MiCA, DORA, AASB-S2 climate disclosure, Australian Migration Act / OMARA Code / Skilled Occupation List, NDIS Pricing Arrangements + Practice Standards, KYC/AML across 41 jurisdictions — cited to regulator sources. First 5 calls per IP work without an API key (real data, not demo); free key (100 credits, no card) at regintelapi.com/k." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
REGINTEL_API_KEYConfiguration, not credentials: REGINTEL_API_BASE- Where it talks to
- regintelapi.com (its own)Also europa.eu, asic.gov.au, aasb.gov.au — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names europa.eu, asic.gov.au, aasb.gov.au as well as its own vendor. The guard injects REGINTEL_API_KEY only into requests to regintelapi.com (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 820 lines in 7 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.