← Registry

General Tools

rekvira.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint17 known toolsFirst detected September 24, 2026Last detected September 24, 2026

ENDPOINT 1

https://mcp.rekvira.com/mcp

No auth detected

MCP server metadata

Name
rekvira
Version
0.1.0
Capabilities
experimentalpromptsresourcestools
Server instructions

Rekvira gives compliance officers and counsel the official text of EU regulations with pinpoints — article, paragraph, recital, annex — and `data_as_of` on every answer. English-first; every tool takes a `regulation` id from the registry (eu-ai-act, dora, …). SEARCH IN ENGLISH. The EUR-Lex corpus is English consolidated text. Use the words a compliance officer would type: high-risk AI system, GPAI, conformity assessment, ICT risk. TALK IN THE USER'S LANGUAGE. Explain, ask and write the work product in the language the user writes in. Quote the official text in English exactly as the tools return it, and put any translation beside it marked as your own, unofficial rendering. Every EU act is published in all official EU languages: when the user needs a quote they can cite in their own language, give the pinpoint and point them to that language version on EUR-Lex rather than presenting your translation as the law. TOOLS (call `connect` first — no key required) * `list_regulations` — which regulations are in the registry and which have corpus loaded * `search_regulation` — full-text search over one regulation; returns pinpoints, not summaries * `search_regulations` — same search across every loaded module when the question spans acts (e.g. DORA and the AI Act). Hits are interleaved round-robin so the first page is not one module only. Each hit names its regulation id for `read_unit` * `lookup_obligations` — articles whose EUR-Lex title names a role (and optional system class). Heading index, not a complete duty list — then `read_unit` the article * `read_unit` — one unit by kind + number/label; articles return full text; paragraphs need article=. number/label/article accept JSON numbers (6) or strings ("6") — agents often emit numbers. It also takes a result row's pinpoint verbatim: pinpoint='Article 6(1)' * `verify_citation` — check a pinpoint someone else produced (model, memo, vendor doc): does it exist in held text, and optionally does a quote match? Then `read_unit` for full text * `whoami` — tier, allowance, and whether you are connected * Jobs — `start_here` and `list_workflows` list them first: a job chains playbooks into one work product (classification memo, DORA contract review, questionnaire answers, NIS2 scoping memo). Start one with `get_workflow(workflow_id='job-<id>')` or the prompt job-<id> * `list_workflows` / `get_workflow` — shipped playbooks; pass the `trial_id` from `connect` to also list or read this client's own private drafts * `save_workflow` / `publish_workflow` / `delete_workflow` — write, mark ready, or remove a private trial playbook. Publishing never shares it outside that trial TWO RULES THAT ARE NOT OPTIONAL 1. REPEAT THE PINPOINT. Every result names an article, paragraph, recital or annex. Pass it on. A compliance officer cannot use a proposition they cannot verify against the official text. 2. SAY THE DATE. Every response carries `data_as_of` — when the EUR-Lex source was fetched. If it is not recent for the user's question, say so before the answer. WHAT THIS SERVICE WILL NOT DO Rekvira is not a lawyer and does not give legal advice. It retrieves official sources and pinpoints; interpreting what they mean for a specific deployment, predicting enforcement outcomes, or saying what to do next is the professional's job. When a user asks whether they are compliant, what the law means for their facts, or what they should do, do not answer as though you know. Call the tools, repeat the pinpoints, and say plainly that you are not giving legal advice. A list of governing provisions is not a compliance conclusion. Do not state a conclusion the sources do not say on their own. Summarise what each provision says, with a pinpoint on every proposition, and let the professional conclude. Corpus loaded: • eu-ai-act (32024R1689): 1054 units, fetched 2026-09-02T09:05:48+00:00 • dora (32022R2554): 572 units, fetched 2026-09-02T09:05:48+00:00 • gdpr (32016R0679): 769 units, fetched 2026-09-02T09:05:48+00:00 • nis2 (32022L2555): 489 units, fetched 2026-09-02T09:05:48+00:00 • cra (32024R2847): 654 units, fetched 2026-09-02T09:05:49+00:00

Known tools 17

connect

Connect keylessly — no email, no API key.

Potential side effects
start_here

Orientation for this corpus right now — which regulations are loaded, unit counts, data_as_of, what is not held, and first-call hints per module.

Inferred read-only
whoami

Who is calling: tier, trial state, corpus load count.

Inferred read-only
record_assessment

Record one structured applicability verdict on a regulation pinpoint for this keyless trial_id (from connect).

Inferred read-only
list_assessments

List this trial_id's recorded assessments, newest first.

Inferred read-only
submit_feedback

Send feedback about REKVIRA ITSELF to the operator: a bug, feature request, friction, or praise.

Potential side effects
list_regulations

List regulations in the registry and whether corpus JSON is loaded.

Inferred read-only
search_regulation

Search held regulation text.

Inferred read-only
search_regulations

Search all loaded regulation modules in one call.

Inferred read-only
lookup_obligations

Articles whose official title names a role as an obligation addressee (e.

Inferred read-only
verify_citation

Verify a citation someone else produced — does the pinpoint exist in held text, and optionally does the quote appear.

Inferred read-only
read_unit

Read one citable unit by kind and number or label.

Inferred read-only
list_workflows

Playbook library for compliance-officer workflows — high-risk triage, DORA ICT review, cross-reg scans, vendor questionnaires.

Inferred read-only
get_workflow

Full step-by-step playbook for one workflow id from list_workflows.

Inferred read-only
save_workflow

Save or update one private compliance playbook for this keyless trial.

Potential side effects
publish_workflow

Mark one of this trial_id private playbooks ready or draft.

Inferred read-only
delete_workflow

Delete one private workflow for this trial_id.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.rekvira]
url = "https://mcp.rekvira.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "rekvira": {
      "type": "http",
      "url": "https://mcp.rekvira.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: rekvira
Remote MCP URL: https://mcp.rekvira.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "rekvira": {
      "url": "https://mcp.rekvira.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "rekvira": {
      "type": "http",
      "url": "https://mcp.rekvira.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "rekvira",
  "transport": "streamable-http",
  "url": "https://mcp.rekvira.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.