All servers · Security
Regulane compliance check
com.regulane/compliance · v1.0.0
New (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | prompts, tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Check code against secure-coding rules mapped to ISO 27001 and the DPDP Act. Free, no account.
Connect
streamable-http · https://regulane.com/api/mcp
claude mcp add --transport http compliance https://regulane.com/api/mcp{
"mcpServers": {
"compliance": {
"url": "https://regulane.com/api/mcp"
}
}
}Tools as reported by the server
get_compliance_rulesReturns the workspace's secure-coding rules: what to look for, how to fix it, and the ISO 27001 Annex A controls and DPDP Act sections each rule evidences. Call this before reviewing a change, then report with report_compliance_check.report_compliance_checkTurns the check you ran against the rules from get_compliance_rules into a scorecard: findings by severity, the ISO 27001 controls and DPDP Act sections affected, and the fix for each. Report a clean check too. Regulane does not store it. Send no source code, secrets or personal data.
Repository · Website · JSON · Text for agents · Registry updated 2026-10-26