Rekvira: EU regulation pinpoints for compliance AI
REMOTE · MCP.REKVIRA.COM · SCANNED SEP 28
Official EU regulation text with article and recital pinpoints over MCP. Keyless trial.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (rekvira_account). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5424 tokens (~285/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Rekvira: EU regulation pinpoints for compliance AI MCP server?
Rekvira: EU regulation pinpoints for compliance AI is a hosted endpoint at https://mcp.rekvira.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.rekvira.com
claude mcp add --transport http com-rekvira-rekvira 'https://mcp.rekvira.com/mcp'
{
"mcpServers": {
"com-rekvira-rekvira": {
"url": "https://mcp.rekvira.com/mcp"
}
}
} {
"servers": {
"com-rekvira-rekvira": {
"type": "http",
"url": "https://mcp.rekvira.com/mcp"
}
}
} [mcp_servers.com-rekvira-rekvira] url = "https://mcp.rekvira.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-rekvira-rekvira": {
"type": "remote",
"url": "https://mcp.rekvira.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-rekvira-rekvira --url 'https://mcp.rekvira.com/mcp' --transport streamable-http
mcp_servers:
com-rekvira-rekvira:
url: "https://mcp.rekvira.com/mcp" {
"McpServers": {
"com-rekvira-rekvira": {
"Transport": "http",
"Url": "https://mcp.rekvira.com/mcp"
}
}
} assistant mcp add com-rekvira-rekvira -t streamable-http -u 'https://mcp.rekvira.com/mcp'
{
"mcpServers": {
"com-rekvira-rekvira": {
"type": "http",
"url": "https://mcp.rekvira.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
- Tool “submit_feedback” rewrote its description, which is the text the model reads security
- “submit_feedback” added an optional parameter “contact_email” cosmetic
- “submit_feedback” added an optional parameter “expected” cosmetic
- “submit_feedback” added an optional parameter “got” cosmetic
- “submit_feedback” added an optional parameter “query” cosmetic
- “submit_feedback” added an optional parameter “severity” cosmetic
- “submit_feedback” added an optional parameter “tool” cosmetic
- “submit_feedback” added an optional parameter “what” cosmetic
- “submit_feedback” reworded the description of “authored_by” cosmetic
- “submit_feedback” reworded the description of “confirmed” cosmetic
- “submit_feedback” reworded the description of “kind” cosmetic
- “submit_feedback” reworded the description of “message” cosmetic
- Tool “submit_feedback” changed its title: Send feedback to the operator → Send feedback to the team cosmetic
- 25 Sept 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +31
- Authorization: fail → unverified ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Tool coverage: 100 functional
- 23 Sept 26 33
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.rekvira.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rekvira.com | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2e523fafd9e6110e13380d4a5c73e19d |
| SANs: rekvira.com, *.rekvira.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.rekvira.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rekvira.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), geolocation=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rekvira.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rekvira.com/mcp | HTTPS enforced | 301 | https://mcp.rekvira.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
connect Connect, or sign in (step 1 of 2) ~201
Connect. With no arguments: the keyless trial — no email, no key; returns trial_id for record_assessment / list_assessments and the private playbook tools. Call start_here next. With the user's email and the language you speak with them (e.g. 'en', 'de', 'lt'): sign in to a free account that keeps their assessments and playbooks across chats. Rekvira sends ONE email in that language with a Confirm link and a six-digit code, valid 15 minutes, and returns request_id. Tell the user to click Confirm; then IMMEDIATELY call connect_verify(request_id) — it waits for the click. Nothing is charged and no card is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| – | – | Only to sign in: the user's email. Omit for the keyless trial | |
| language | – | – | The language you speak with the user (en, de, lt, fr, es, pl); the email uses it |
No output schema declared.
No examples provided.
connect_verify Sign in (step 2 of 2) ~174
Finish signing in. Call it RIGHT AFTER connect(email) with the request_id and no code: it waits up to 45 s for the user to click Confirm in the email and returns as soon as they do (if it returns waiting, call it again — do not ask the user to report the click). If the user reads you the six-digit code, pass it as code. Pass the trial_id you already have and the keyless work moves into the account. Returns a rek_ key (shown once) and a `session` value to pass on later calls.
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | Only if the user reads you the six-digit code from the email |
| request_id | – | – | request_id returned by connect(email) |
| trial_id | – | – | Optional trial_id from the keyless connect(): its work moves into the account |
No output schema declared.
No examples provided.
delete_workflow Delete a private playbook ~107
Delete one private workflow for this trial_id. It cannot delete a shipped playbook or a draft owned by another trial.
| Name | Type | Req | Description |
|---|---|---|---|
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| trial_id | – | – | trial_id returned by connect() |
| workflow_id | – | – | Id of your private workflow to delete |
No output schema declared.
No examples provided.
get_workflow Open a playbook or job ~154
Full step-by-step playbook for one workflow id from list_workflows. Follow the named tools (search_regulation, read_unit, verify_citation, …) rather than summarising the playbook.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | – | Alias for workflow_id |
| name | – | – | Alias for workflow_id |
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| trial_id | – | – | Optional trial_id from connect to read your private draft |
| workflow_id | – | – | Id from list_workflows, e.g. high-risk-triage |
No output schema declared.
No examples provided.
list_assessments List my assessments ~142
List this trial_id's recorded assessments, newest first. Pass the trial_id from connect(). Use when resuming a multi-week DPIA or applicability review. Never invent rows for another trial.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Max rows (1–100, default 50) |
| max_chars | – | – | Cap on the response size in characters (default 8000) |
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| trial_id | – | – | trial_id returned by connect() |
No output schema declared.
No examples provided.
list_regulations List regulations ~76
List regulations in the registry and whether corpus JSON is loaded. Then search_regulation, search_regulations, or list_workflows for a named process.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Most rows to return (default 10 on searches, max 50) |
| max_chars | – | – | Cap on the response size in characters (default 8000) |
No output schema declared.
No examples provided.
list_workflows List playbooks and jobs ~176
Playbook library for compliance-officer workflows — high-risk triage, DORA ICT review, cross-reg scans, vendor questionnaires. Read a playbook before improvising a process. Pass trial_id from connect to list your own private drafts beside the shipped library. Then call get_workflow with workflow_id from this list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Most rows to return (default 10 on searches, max 50) |
| max_chars | – | – | Cap on the response size in characters (default 8000) |
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| trial_id | – | – | Optional trial_id from connect for this client private drafts |
No output schema declared.
No examples provided.
lookup_obligations Look up obligations by role ~552
Articles whose official title names a role as an obligation addressee (e.g. role='deployer', optional system_class='high-risk'). Heading index, not annotated metadata — then read_unit the article. role accepts the word a title uses (deployer, provider, importer, operator, authorised representative, controller, processor, joint controller, data subject, or supervisory authority on gdpr). notified body on eu-ai-act returns Arts 34/45. Read also_named (Arts 31 through 38) for related titles without 'obligation'. When result_count is 0, read also_named before concluding none match (e.g. Arts 22/54 on eu-ai-act authorised representative; Arts 63/94 on eu-ai-act operator; Arts 29/39 on eu-ai-act conformity assessment body; Arts 76/77/85 on eu-ai-act market surveillance authority; Art 100 on eu-ai-act union institution; Arts 53/55/88 on eu-ai-act GPAI provider / general-purpose AI provider / provider of general-purpose AI models; Arts 13/14/21/22 on cra manufacturer / manufacturer of products with digital elements; when also_named is empty read heading_note and use search_regulation; Arts 24/26/27/29/79 on gdpr controller; Arts 27/28/29/79 on gdpr processor; Art 26 on gdpr joint controller; Arts 12/13/14/15/34/80 on gdpr data subject; Arts 31/33/51/53/54/56/60/62/77/78 on gdpr supervisory authority; Art 32 on nis2 essential entity; Arts 3/33/34 on nis2 important entity; Arts 23/31 on dora provider; Art 31 on dora ict third-party service provider; on dora financial entity or operator also_named is empty — read heading_note and use search_regulation for body mentions (Arts 28/30 for ICT third-party context); Art 18 on cra authorised representative). Then read_unit each article — the index is not a complete duty set.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Most rows to return (default 10 on searches, max 50) |
| max_chars | – | – | Cap on the response size in characters (default 8000) |
| query | – | – | Alias for role when agents pass search-style query= instead of role= |
| regulation | – | – | Regulation id from list_regulations (required) |
| role | – | – | Addressee in the article title, e.g. deployer |
| system_class | – | – | Optional class in the same title, e.g. high-risk |
No output schema declared.
No examples provided.
publish_workflow Publish a private playbook ~132
Mark one of this trial_id private playbooks ready or draft. Publishing is private state only; it never adds content to the shipped library or another trial.
| Name | Type | Req | Description |
|---|---|---|---|
| published | boolean | – | true marks it ready in this trial; false returns it to draft |
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| trial_id | – | – | trial_id returned by connect() |
| workflow_id | – | – | Id of your private workflow |
No output schema declared.
No examples provided.
read_unit Read a provision ~259
Read one citable unit by kind and number or label. Articles return aggregated paragraph text. Paragraphs repeat across articles — pass article= (e.g. 6 or '6') to disambiguate. number, label and article accept JSON numbers or strings. read_unit also takes a result row's pinpoint verbatim: pinpoint='Article 6(1)' resolves kind and number for you. Then verify_citation if checking someone else's pinpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| article | – | – | Required for paragraphs: parent article number (e.g. 6 or '6') |
| as_of | – | – | Optional date YYYY-MM-DD: answer with the wording in force on that date (default today). Amended provisions say which act gave them their wording |
| citation | – | – | Alias for pinpoint |
| cite | – | – | Alias for pinpoint |
| kind | – | – | recital | article | paragraph | annex | section |
| label | – | – | Exact label e.g. (47) or 1. (string or JSON number) |
| number | – | – | Unit number within kind (string or JSON number) |
| pinpoint | – | – | A pinpoint string from a result row, e.g. 'Article 6(1)' — read instead of kind/number |
| regulation | – | – | Regulation id (required) |
No output schema declared.
No examples provided.
record_assessment Record an assessment ~224
Record one structured applicability verdict on a regulation pinpoint for this keyless trial_id (from connect). Verdicts: applicable | not_applicable | needs_review | deferred. Optional reason codes only — never free-text notes. Re-recording the same regulation+pinpoint overwrites. Assessments annotate; they never hide search or read results. Call after the officer states applicability.
| Name | Type | Req | Description |
|---|---|---|---|
| pinpoint | – | – | Pinpoint string, e.g. Article 6(1) |
| reason | – | – | Optional structured reason: wrong_entity_type | below_threshold | already_covered_elsewhere | awaiting_vendor_answer | confirmed_obligation | revisit_after_guidance |
| regulation | – | – | Regulation id, e.g. eu-ai-act |
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| trial_id | – | – | trial_id returned by connect() |
| verdict | – | – | applicable | not_applicable | needs_review | deferred |
No output schema declared.
No examples provided.
rekvira_account Your account and plan ~273
The signed-in account: action='status' (default: email, what is kept, keys), 'plan' (what the free beta includes: the keyless trial and the free account; nothing is charged), 'usage', 'keys' (list; never the key itself), 'revoke_key' with key_prefix, 'export' (everything held), 'delete' with confirm_email=<the account email> (mails a confirmation link; deletion happens on the click). Not signed in: says how to sign in, and 'plan' still shows what the free beta includes.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | – | status | plan | usage | keys | revoke_key | export | delete |
| confirm_email | – | – | With action='delete': the account's email, typed back by the user |
| key_prefix | – | – | With action='revoke_key': the key's prefix as action='keys' lists it (rek_xxxxxx) |
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| tier | – | – | With action='plan': not needed during the beta — everything is free and there is no paid plan to choose |
No output schema declared.
No examples provided.
save_workflow Save a private playbook ~172
Save or update one private compliance playbook for this keyless trial. It stays inside this trial_id; call publish_workflow only to mark it ready here, never to share it with another user.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The steps and tool calls for this private playbook |
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| summary | – | – | One sentence saying when this private playbook is useful |
| title | – | – | Plain title for this private playbook |
| trial_id | – | – | trial_id returned by connect() |
| workflow_id | – | – | Lowercase id for this private workflow, e.g. vendor-ai-review |
No output schema declared.
No examples provided.
search_regulation Search one regulation ~207
Search held regulation text. Returns pinpoints and excerpts, not summaries. Requires regulation id (e.g. eu-ai-act) and query string. limit, detail (compact|full) and max_chars bound the response. Then read_unit on the best pinpoints; verify_citation if checking someone else's cite.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Optional date YYYY-MM-DD: answer with the wording in force on that date (default today). Amended provisions say which act gave them their wording |
| detail | – | – | compact (default: ~400-char excerpt around the match) | full (whole unit text) |
| kinds | – | – | Optional filter: recital, article, paragraph, annex, section |
| limit | – | – | Most rows to return (default 10 on searches, max 50) |
| max_chars | – | – | Cap on the response size in characters (default 8000) |
| query | – | – | Search terms in English (required) |
| regulation | – | – | Regulation id from list_regulations (required) |
No output schema declared.
No examples provided.
search_regulations Search all regulations ~244
Search all loaded regulation modules in one call, ranked by relevance across them. Use when the question names more than one act or you do not know which act holds the answer. limit, detail (compact|full) and max_chars bound the response; per_regulation_min gives each act a share of the page. Each hit carries its regulation id — then read_unit per regulation.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Optional date YYYY-MM-DD: answer with the wording in force on that date (default today). Amended provisions say which act gave them their wording |
| detail | – | – | compact (default: ~400-char excerpt around the match) | full (whole unit text) |
| kinds | – | – | Optional filter: recital, article, paragraph, annex, section |
| limit | – | – | Most rows to return (default 10 on searches, max 50) |
| max_chars | – | – | Cap on the response size in characters (default 8000) |
| per_regulation_min | – | – | Optional: at least this many rows from each act with matches |
| query | – | – | Search terms in English (required) |
| regulations | – | – | Optional subset of regulation ids; default = all loaded corpus |
No output schema declared.
No examples provided.
start_here Start here ~70
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. Built from the loaded corpus at call time. Cheap: one call, no quota. Then list_regulations, search_regulation, or list_workflows.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_feedback Send feedback to the team ~586
Send feedback about Rekvira to the team that builds it: a bug, a wrong answer, missing data, a missing feature, a workflow idea, or praise. Every item is read by a person. When to offer it: an answer came back empty or wrong; the user corrected you or the result; a workflow was missing a step the user needed; the user repeats a manual step the service could do for them; the user says they need something the service does not do. Offer once, in one sentence; the user's task comes first. Ask first. Show the user what you will send and send it only after they agree. Their own words, and any client, case, company or personal detail, go only with their explicit OK; then set confirmed=true. With authored_by='agent' you may report your own observation of the service (the tool, what you expected, what came back) without asking, as long as it holds none of the user's words or confidential content. Fill kind and what (the task, and what went wrong or what is needed). For a wrong answer add expected and got. Add tool and query for context (the query only with the user's OK), severity, and contact_email only when the user wants a reply. The reply carries a reference id. Tell the user it reached the team; do not promise a reply or a date.
| Name | Type | Req | Description |
|---|---|---|---|
| authored_by | – | – | user (their words) | agent_drafted (you wrote it, they approved) | agent (your own observation) |
| confirmed | boolean | – | true once the user approved sending this; required for authored_by user or agent_drafted |
| contact_email | – | – | Only if the user wants a reply: the address to reply to |
| expected | – | – | For a wrong answer: what the right answer or result would have been |
| got | – | – | For a wrong answer: what came back instead |
| kind | – | – | One of: bug (something failed or errored), wrong_answer (an answer was returned but it was wrong or misleading), missing_data (a document, record or source the user expected is not covered), missing_… |
| message | – | – | Older name for `what`, kept so earlier callers still work; prefer `what` |
| query | – | – | The query or arguments that produced it; only with the user's OK |
| severity | – | – | low | normal | high | blocking (blocking: the user cannot do their work) |
| tool | – | – | The tool the feedback is about, if one (e.g. the tool that answered wrongly) |
| what | – | – | The task and what went wrong or what is needed (3-2000 characters) |
No output schema declared.
No examples provided.
verify_citation Verify a citation ~191
Verify a citation someone else produced — does the pinpoint exist in held text, and optionally does the quote appear. Pass the cite as written (e.g. 'Article 6(1) EU AI Act') plus optional quote=. Then read_unit for full text. regulation= disambiguates when the cite omits the act name; returns regulation_mismatch when the cite embeds YYYY/NNNN for a different act.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Optional date YYYY-MM-DD: answer with the wording in force on that date (default today). Amended provisions say which act gave them their wording |
| citation | – | – | Citation as written, e.g. Article 6(1) EU AI Act |
| cite | – | – | Alias for citation when agents pass cite= instead of citation= |
| quote | – | – | Optional sentence to check against held text |
| regulation | – | – | Regulation id when the cite string alone is ambiguous |
No output schema declared.
No examples provided.
whoami Who am I ~115
Who is calling: tier, trial state, corpus load count. Pass trial_id from connect() to confirm the handle used for assessments and private workflows. After connect, call start_here or list_regulations.
| Name | Type | Req | Description |
|---|---|---|---|
| session | – | – | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OA… |
| trial_id | – | – | Optional trial_id from connect() — echoed when present |
No output schema declared.
No examples provided.
What is the Rekvira: EU regulation pinpoints for compliance AI MCP server?
Rekvira: EU regulation pinpoints for compliance AI is an MCP server listed in the public MCP registry as com.rekvira/rekvira. Official EU regulation text with article and recital pinpoints over MCP. Keyless trial. This page covers its hosted endpoint (https://mcp.rekvira.com/mcp).
Is the Rekvira: EU regulation pinpoints for compliance AI MCP server safe to use?
Rekvira: EU regulation pinpoints for compliance AI scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Rekvira: EU regulation pinpoints for compliance AI MCP server expose?
Rekvira: EU regulation pinpoints for compliance AI exposes 19 tools: connect, connect_verify, rekvira_account, start_here, whoami, and 14 more. Their descriptions and schemas cost roughly 4,055 tokens of context every time the server is loaded.
Does the Rekvira: EU regulation pinpoints for compliance AI MCP server require authentication?
No. We connected to Rekvira: EU regulation pinpoints for compliance AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rekvira: EU regulation pinpoints for compliance AI MCP server still maintained?
Rekvira: EU regulation pinpoints for compliance AI is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.