Compliance

com.rulemeshPublished by rulemesh.comOfficial publisherv1.0.0Updated Oct 24, 2026

Engineered GDPR compliance for engineers and AI agents: pull rules, implement, submit evidence.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Hosted RuleMesh server that gives an assistant source-traced GDPR and EU AI Act rules, scoping questions, implementation checklists and evidence submission.

What you can do
  • Discover regulations and frameworks, look up definitions, and run scoping questions to decide whether a regulation applies
  • Pull the rules and checklists that apply to a system, and scan a repository against them
  • Submit evidence signals, individually or in batches, with descriptions and filenames
  • Track progress, ticket status, scan sessions, and start, end or resume scans
  • Use packaged prompts for planning, implementing, scanning and reviewing compliance bundles
When to use it
Useful when engineers or coding agents need to turn GDPR or EU AI Act obligations into concrete implementation checklists, judge whether a regulation applies to a system, or record evidence for later human review.
Requirements
A remote Streamable HTTP endpoint with OAuth 2.1 browser login (email/password or Google); no API key. A RuleMesh account is required. The free tier covers GDPR; EU AI Act access and control mappings need a paid subscription. Network access to the hosted endpoint.
Before you install
Evidence submissions send evidence descriptions and filenames to RuleMesh, so avoid including source code or secrets; the vendor states it does not receive source-code contents. Submissions do not certify compliance or mark requirements verified, which stays a human action. Some regulations require a paid subscription.

Installation

In SourceWeft

  1. Open Compliance in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.rulemesh%2Fcompliance/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "compliance": {
      "type": "http",
      "url": "https://api.rulemesh.com/mcp"
    }
  }
}

README

RuleMesh MCP

Engineered Compliance Infrastructure for engineers and AI agents.

RuleMesh delivers source-traced rules for GDPR and the EU AI Act: determine applicability, retrieve the requirements and implementation checklists that apply to a system, submit evidence signals, and track human verification. It runs as a hosted remote MCP server at https://api.rulemesh.com/mcp (Streamable HTTP, OAuth login), consumable from any MCP client.

This repo is the canonical home for the server's listing (server.json, published to the MCP Registry as com.rulemesh/compliance) and client setup docs.

Connect

You authenticate once in the browser (email/password or Google); no API key to manage. A RuleMesh account is required. The FREE tier includes GDPR. EU AI Act access and control mappings are available with a paid subscription.

OpenAI Codex

Add to ~/.codex/config.toml:

toml
[features]rmcp_client = true            # enables the remote MCP client (use experimental_use_rmcp_client = true on older Codex)
[mcp_servers.rulemesh]url = "https://api.rulemesh.com/mcp"startup_timeout_sec = 30tool_timeout_sec = 120

Then codex mcp login rulemesh (opens the browser for OAuth), and /mcp in the TUI to confirm the tools loaded.

Claude Code

bash
claude mcp add --transport http rulemesh https://api.rulemesh.com/mcp

Run /mcp and follow the browser login. A packaged plugin is also available at RuleMesh/rulemesh-claude-plugin.

Claude Desktop / Cursor / VS Code / other clients

Add a remote (Streamable HTTP) MCP server pointing at https://api.rulemesh.com/mcp. For example, Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json):

json
{  "mcpServers": {    "rulemesh": {      "type": "streamable-http",      "url": "https://api.rulemesh.com/mcp"    }  }}

What you get

The server groups its 19 tools around one loop: plan, pull, implement, prove. GDPR and the EU AI Act are live today, with access depending on the account's plan.

  • Discovery and scoping: list_regulations, list_frameworks, lookup_definition, get_compliance_plan, scope_next_question, scope_classify, scope_retrieve_source, scope_query_applicable, scope_update_profile
  • Implement: pull_rules, scan_compliance
  • Prove: submit_signals, submit_signals_batch
  • Track: get_progress, get_ticket_status, get_scan_sessions, start_scan, end_scan, resume_session

Four prompts package the common workflows: implement_bundle, scan_and_report_bundle, review_bundle, and plan_compliance. One resource, regulation://{id}, returns regulation metadata.

Your coding agent reads your repository locally using RuleMesh requirements. RuleMesh does not read or receive source-code contents. Evidence submissions contain the evidence description and relevant filenames; they do not certify compliance or mark a requirement verified. Verification remains a human action.

Example prompts

  • "Which regulations can I use on my current RuleMesh plan?"
  • "Does the EU AI Act apply to this system? Ask the necessary scoping questions and cite the source provisions behind the result."
  • "Give me a prioritised GDPR implementation plan for this application."
  • "Pull the GDPR rules for my data-export feature and give me an engineering checklist."
  • "Review this repository against the pulled requirements. Submit only evidence signals and filenames; do not upload source code or mark anything verified."

Authentication

OAuth 2.1 with PKCE and Dynamic Client Registration. Clients register themselves and open a browser login; tokens refresh automatically.

About RuleMesh

RuleMesh is Engineered Compliance Infrastructure — the engineered rule graph that sits between regulation as written and software as built, consumable by engineers, AI agents, and auditors. It defines what each obligation requires, how to execute it with framework-specific controls, and what evidence proves it was done. GDPR and the EU AI Act are released today; more regulations are on the roadmap. → rulemesh.com

Links

Source: README.md at commit ab8fd79

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.