Home Products & Services — Web Application — API — IDFinder — iOS Application — Managed Service — KYX Advisory — AI Connectors Use Cases Coverage About Us Contact Get in Touch for a Demo

Products & Services · AI Connectors

Corporate Intelligence,
Inside Your AI Assistant

MCP connectors for Claude and Grok. Run KYC and KYB searches and recall case history conversationally, against official registries, on your existing Revolutio credits.

2
Assistants supported
148
National registries
Zero
API keys to manage
mcp session
Analyst Who ultimately controls ABC Limited?
Tool revolutio.idfinder.resolve running
Tool revolutio.company.ownership running
Claude Found two shareholders in live registry search. Control resolves to one individual holding 74% effective, above your 25% threshold. Source: ACRA · retrieved 14:02 UTC
Connected as Claude · IDLE

In conversation

What your team can ask for without leaving the chat

The connector gives the assistant a set of tools against live registries. The analyst asks in plain language; the assistant calls the tool and answers from the record.

01

Search official registries

Ask for a company by name or number and the assistant runs the search against the official register, not against what it remembers.

02

Resolve identifiers with IDFinder

A legal name and a country resolve to the correct registry identifier, so a conversation can start from what the analyst actually knows.

03

Recall your case history

Past searches and retrievals from your Revolutio account are available in the conversation, so work already done is not repeated.

04

Read ownership out loud

Shareholders, officers and effective percentages are returned in the thread, with the structure explained rather than dumped as a table.

05

Connect over OAuth

Authorisation happens through your Revolutio account. No API keys are pasted into a chat client or stored on a laptop.

06

Spend your existing credits

Calls are metered against the credits you already hold, on the same terms as every other route into the platform.

Governance

An assistant that cites the register, not itself

The reason to connect an assistant to a registry tool is that the answer stops being a recollection. Every figure it states was retrieved, sourced and timestamped by the same platform your analysts already use.

Answers carry their source

Every retrieved figure returns with the register it came from and the moment it was read, so an assistant answer is quotable in a file.

The register is the authority

Company data is fetched at request time. The assistant is the interface, not the source, which is what keeps it out of guesswork.

Access follows your account

The connector authorises through OAuth against your Revolutio account, so permissions and revocation stay where your administrators already manage them.

Usage stays metered and visible

Every call is counted against your credits and appears in your account activity, so AI-driven retrieval is as auditable as any other search.

Available connectors

Two assistants, one connector

Both run on the Model Context Protocol against the same Revolutio tools, so the answer does not change with the assistant.

Revolutio for Claude

Available

Run KYC and KYB searches, resolve identifiers and recall case history from inside a Claude conversation.

ProtocolMCP
AuthOAuth
BillingYour credits

Revolutio for Grok

Available

The same tool set inside Grok, for teams standardised on xAI rather than Anthropic.

ProtocolMCP
AuthOAuth
BillingYour credits

Connecting takes three steps

01

Add the connector

Point your assistant at the Revolutio MCP server. Nothing is installed and no keys are issued.

02

Authorise with OAuth

Sign in to your Revolutio account and grant access. Permissions and revocation stay with your administrators.

03

Start asking

The tools appear in the assistant. The first question can be a company name.

More connectors are coming

We are expanding the catalogue of AI assistants supported by Revolutio. Talk to our team about your preferred platform.