Is LexRegPulse: Banking Regulation Brief MCP server safe?
Yes, with the usual care.
Passed every safety check we run. Maintained, authenticated, reachable, clean scan.
What to know before installing
- highWrite-action tools reachable without authentication
How LexRegPulse: Banking Regulation Brief compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 86/100
- higher than 72% of 48,243 servers
- Tools that change things
- 22%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
What its tools let an agent do: 7 read · 2 change
Release history: 2 versions in the registry since 2026-02-25, latest 2026-09-20, typically one every 208 days.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
1 high
- Code scan3 source files scanned25/25
- Live reliabilityremote reachable in 1269ms20/20
- Tool poisoning9 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
- Maintenancelast push 26 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
LexRegPulse: Banking Regulation Brief reviews, tools and install