RapidValue
EN
ENEnglishNLNederlandsFRFrançaisDEDeutsch
Reserve a pilot
Ask RapidValue · MCP server · Early access

Ask RapidValue a question from the AI assistant you already use

Connect Claude, ChatGPT or any MCP client to RapidValue. Your assistant sees what you may see in the product and nothing else. It can also request access and decide your own tasks, through the normal approvals. Every call is recorded.

Join the early access
Illustration · fictional demo data

Which of our AI agents need my attention this week?

Looks up your findingsread-only · as Tom

Three agents need you:

  1. A leaver still owns an agentclaims-triage-bot · owner left on 2 Sep · manager proposed as successor
  2. Credential expires in 12 daysinvoice-agent · Entra agent identity
  3. Credential rotation overduesupport-summariser · AWS access key · 128 days old
Works with

It works with the assistants your people already use

  • ClaudeAdd RapidValue as a connector and sign in.
  • ChatGPTAdd RapidValue as a connector and sign in.
  • Other MCP clientsAny client that speaks MCP with OAuth sign-in.
  • Your own agentsMachine clients use a scoped RapidValue credential, get the read tools only and are governed like any other agent.
What it can do today

It reads and explains, and starts work only through the normal route

Most of it only reads. What starts work goes through the same approvals as in the product, and nothing writes to a connected system.

  • Which findings need my attention?
  • Why does Tom have access to payroll?
  • Why is this person’s risk high?
  • Who had access to payroll on 1 March?

Ask

read-only

Why can invoice-matcher read invoices?

Owner
Marie Peeters, Finance operations
Reason
Rule FIN-AP-07, approved by Tom Claes on 2 Sep
System
Finance ERP

Explained by RapidValueFictional demo data

For your developers: every tool by name is in the documentation

How it stays safe

Your assistant sees what you may see, and nothing else

  1. It uses your permissionsThe assistant acts for you and sees only what RapidValue would show you in the product. It is registered as an AI agent with an owner, so it is reviewed and can be stopped like any other agent.
  2. You sign in and consentConnecting uses OAuth: you sign in to RapidValue and approve exactly what the assistant may read and do. The answers go to your own assistant provider, which may sit outside Europe.
  3. Your admin decidesMCP is off until your RapidValue admin enables it. People and machine clients are enabled separately, and a platform-wide kill switch can turn MCP off altogether. Access requests, task decisions and connector onboarding each have their own switch.
  4. Every call is recordedEach tool call is logged before and after it runs: who asked, which tool, the outcome and how much was returned.
  5. Revoke any timeConnected assistants are listed in RapidValue and can be disconnected at any moment. Their access ends right away.
  6. No direct path to your systemsTools that start work use the product’s own routes and approvals, and machine clients get the read tools only. No tool writes to a connected system.

Every call passes four gates.

Who connects

  • A person’s assistantClaude, ChatGPT or any MCP client, OAuth sign-in and consent on your host
  • Its agent identityregistered with an owner; kill switch, review, lockout stop its next call
  • A machine clienta scoped RapidValue credential, read tools only
  1. 1Admin switchper tool group, read live
  2. 2Consented scopenarrows, never widens
  3. 3The person’s rightsthe screen’s own view
  4. 4Agent statusstopped means refused

Read and explain: 20 tools

Access
people, rights, someone’s access, your tasks, why a right is held, risk, peers, segregation of duties, a move
Findings
the Advisor findings routed to you
Audit
the audit trail, who held what on a date
Connectors
connector types, setup guides, status

Start work through the product: 4 tools

Request access
normal approvals; switch off by default
Decide my task
MFA, no approving past a segregation-of-duties conflict, rate-limited
Add a connector
a person reviews at credentials, activation
RapidValue’s MCP server: who connects, the four gates every call passes, and what always holds.Open full size

What always holds

  • Recorded before and afterwho asked, which tool, the outcome and counts and references, never the answer
  • A refusal says whyRapidValue’s own sentence: a switch off, a missing right; never your values echoed
  • No path to your systemsno tool writes to a connected system; credentials are never model-visible
  • Off until you switch it onper customer, people and machines apart; a platform kill switch turns it all off
Getting connected

You connect in three steps, and your admin does the first one

  1. Your admin enables MCP

    For your organisation, for people, machine clients or both.

  2. Add RapidValue to your assistant

    Point your MCP client at your RapidValue address.

  3. Sign in and consent

    Approve what the assistant may read and do. Revoke it whenever you like.

What comes next

Next, a gateway for your own tools, and drafts for a person to confirm

  • In early access: RapidValue’s gateway in front of your own MCP servers and APIs, deciding every tool call and blocking what is not allowed.
  • Draft tools: prepare a review decision or a role change for a person to confirm.
  • A model never gets a direct path to a connected system.
Early access

Do you want to try this with your own assistant? Join the early access.

Join the early access
Related