IVERIOS Trust Center connector for Claude and other AI assistants

IVERIOS Trust Center connector

Ask your AI assistant about the security and compliance of your suppliers. One address, no account needed: the IVERIOS Trust Center connector gives Claude and other MCP clients read-only access to the information that companies publish in their IVERIOS trust centers:

certifications;
regulations;
security controls;
infrastructure;
privacy and data transfers;
sub-processors;
documents;
FAQ.

It also answers questions about IVERIOS itself — what a trust center is, how to request access to a vendor's restricted documents, pricing and the other IVERIOS tools (about_iverios).

What you can ask

*Demo Cloud d.o.o. (trust_center: "demo") is a fictional example company published by IVERIOS to show what a trust center can contain; its data and documents are illustrative only.*

"What certifications does Demo Cloud have, and when do they expire?"
"Where does Demo Cloud store customer data, and does it transfer data outside the EEA?"
"Summarise Demo Cloud's latest penetration test."
"List Demo Cloud's sub-processors located outside the EU."
"Fill in our vendor assessment for Demo Cloud using its trust center."

Connect

Server URL	`https://trust.iverios.eu/mcp`
Authentication	Optional. Without sign-in: public information. Sign in (OAuth 2.1 — Microsoft, Google or a one-time code by email) for information shared with approved visitors: ask your assistant to sign in, or it signs in when it needs restricted information (`sign_in` tool).
Sign-in address	`https://trust.iverios.eu/mcp/signin` — for clients that should sign in when connecting
Transport	Streamable HTTP

One click

After installing, start the connector — it works right away; sign in when your assistant asks for it.

Chat assistants

Claude — open the connector from the Claude connectors directory, or go to Settings → Connectors → Add custom connector and paste the server URL. It connects without sign-in; for restricted information use the sign-in address instead (or sign in when prompted). Enable the connector in your chat.

ChatGPT — open Plugins (chatgpt.com/plugins), click +, choose Add custom MCP server, paste the server URL and choose No authentication (public information) or OAuth with the sign-in address. Availability depends on your ChatGPT plan; in workspaces an admin may need to allow custom connectors. Deep research and company knowledge use the search and fetch tools.

Mistral Le Chat — Connectors → + Add Connector → Custom MCP Connector, enter a name and the server URL, choose no authentication (or OAuth with the sign-in address) and click Connect. On team plans only an admin can add connectors.

Microsoft Copilot Studio — in your agent open Tools → Add a tool → New tool → Model Context Protocol, enter the name, a short description and the server URL, and choose OAuth 2.0 → Dynamic discovery.

Developer tools

Claude Code

claude mcp add --transport http iverios-trust https://trust.iverios.eu/mcp

It works right away. For restricted information run /mcp and choose Authenticate when asked, or add the sign-in address instead.

Gemini CLI

gemini mcp add --transport http -s user iverios-trust https://trust.iverios.eu/mcp

Then run /mcp auth iverios-trust.

Codex

codex mcp add iverios-trust --url https://trust.iverios.eu/mcp
codex mcp login iverios-trust

VS Code (command line)

code --add-mcp '{"name":"iverios-trust","type":"http","url":"https://trust.iverios.eu/mcp"}'

Other MCP clients — add a remote MCP server (Streamable HTTP) with the server URL. The client must support OAuth with dynamic client registration or client ID metadata documents, and PKCE. For public information only, use the URL without sign-in.

Assistants without MCP — every trust center publishes an AI-readable summary at <trust center address>/llms.txt. Ask your assistant to read it, for example: "Read https://trust.iverios.eu/demo/llms.txt and summarise the security and compliance."

Sign-in and access

Enter your work email. We send you a 6-digit code that is valid for 10 minutes. There is no password.
Review what the assistant will be able to read and click Allow.

Your assistant can then read:

everything that an approved visitor can see, in every trust center where your email is an approved visitor. This can include documents shared only with approved visitors;
public information of all other trust centers whose owners have enabled AI access.

To get restricted information from a company, request access on its trust center with the same email. Access is checked on every request: when a company revokes your approval, its restricted information is no longer available to your assistant.

Tools

All tools are read-only.

Tool	What it returns
`list_trust_centers`	Trust centers where you are an approved visitor, and trust centers matching a company name or domain
`get_overview`	Summary of a company's security and compliance posture (start here)
`list_certificates`	Certifications with status, issuer, accreditation, dates and scope
`list_controls`	Implemented security controls, optionally by area
`get_infrastructure`	Infrastructure components by layer, exposure, authentication and controls
`get_privacy`	Data processing, data location, DPO contact and international transfers
`list_subprocessors`	Sub-processors with purpose, location and transfer mechanism
`list_documents`	Published documents and whether you can read them
`get_document_text`	Text of an accessible document, in slices
`search`	Keyword search across the content and accessible documents. `trust_center` is optional: without it, the search covers trust centers where you are an approved visitor and those whose company name appears in the query
`fetch`	Full text of a search result (a section or a document) by its id, with the source URL

Every tool except list_trust_centers, search and fetch requires trust_center: the id returned by list_trust_centers, the trust center's domain or the exact company name. Most tools also accept an optional language code for translated content.

Limits

Signed in: 60 requests per minute.
Per trust center per day:
- 2,000 tool calls and 100 documents when signed in;
- fewer without sign-in.

When a limit is reached, the tool returns a message saying when to retry.

Disconnect

Remove the connector in your AI assistant. Tokens expire after 30 days without use. To end your sign-in session in the browser, use Not you? Sign out on the connection screen.

Privacy and support

Connector privacy policy
Support: info@iverios.eu
Provider: IVERIOS OÜ, Tallinn, Estonia — iverios.eu

Companies that use IVERIOS Trust Center enable or disable AI access in their admin interface (AI access (MCP)).