Rulewise
Server Details
Warns developers which Sri Lankan laws apply to what they build. Legal information, not advice.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- malithJayasinghe2000/legal-mcp
- GitHub Stars
- 0
- Server Listing
- Rulewise
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
Each tool has a distinct role: gather inputs (get_fact_questions), run the assessment (check_legal_risks), and fetch a single rule's proof text (get_rule). The main risk is that get_rule could be mistaken for a general legal-question tool, but its description scopes it to displaying quoted rule text.
All three names follow a clean snake_case verb_noun pattern (check_legal_risks, get_fact_questions, get_rule) with the verb accurately signaling the action.
Three tools are enough for a narrow, single-jurisdiction legal risk checker, and each earns its place with no filler. It is on the thin side, but that matches the tightly scoped purpose.
The workflow (discover facts → check risks → show rule proof) is covered, but there is no way to enumerate or search rules/coverage areas, and no tool to browse which laws or jurisdictions are supported beyond the fact list. Agents hitting a vague warning have limited paths to drill down.
Available Tools
3 toolscheck_legal_risksARead-onlyIdempotentInspect
Check a planned or new feature for legal risks. Call this whenever the user plans or builds a feature for a product used in Sri Lanka, or made by a Sri Lankan company or person, even if they didn't ask about law. If the user hasn't said where the users or company are, ask them first; never guess the country. Send country codes and facts from get_fact_questions only (no idea text, no code). Returns warnings with severity (Must / Should / Check with a lawyer), the law and section, what to do, and the areas NOT covered.
Inputs: facts (required), users_in (required), done, company_in, +1 more. Returns: object
get_fact_questionsARead-onlyIdempotentInspect
List the facts check_legal_risks understands, grouped, each with the question it answers. Call once before check_legal_risks.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Declare what your app does and where it operates; get cited, jurisdiction-specific findings.
One-step legal compliance for vibe-coded apps: privacy, terms, cookie banner and EU AI Act check.
Deterministic, cited regulatory research for product launches; legal information, not legal advice.
Cited EU & global law, regulations & security frameworks via Ansvar Gateway. OAuth, free + paid.
Related MCP Servers
- AlicenseAqualityBmaintenanceOne-step legal compliance for vibe-coded apps: scans project, generates privacy policies/TOS, installs cookie consent banner, and checks EU AI Act risk.10175 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding assistants to audit websites and local projects against a Sri Lanka PDPA technical checklist via nine MCP tools covering privacy policies, cookie consent, data-collection forms, code schemas, breach readiness, and cross-border transfers. Produces prioritized Markdown and JSON gap reports with readiness scores and remediation notes.9MIT
- AlicenseDqualityDmaintenanceProvides comprehensive HIPAA compliance guidance for developers building healthcare applications. Offers tools to identify PHI, understand encryption requirements, navigate business associate rules, and ensure compliance with HIPAA Security and Privacy Rules.152MIT
- AlicenseNot gradedqualityCmaintenanceScans public URLs for compliance and security issues such as leaked API keys, exposed files, missing privacy pages, and security headers, helping developers identify gaps before launch.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.