# IVERIOS Trust Center (remote · trust.iverios.eu)

Vendor security & compliance (certifications, controls, subprocessors) from IVERIOS Trust Centers

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `trust.iverios.eu`: 75/100 (this document), [markdown](https://verifymcp.io/servers/eu-iverios-trust-center/trust.md), [page](https://verifymcp.io/servers/eu-iverios-trust-center/trust)

## Channel facts

- Endpoint: `https://trust.iverios.eu/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1979 tokens (~131/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
  - Structured output schemas are declared (13% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the IVERIOS Trust Center MCP server?

IVERIOS Trust Center is a hosted endpoint at https://trust.iverios.eu/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.

### Claude

```bash
claude mcp add --transport http eu-iverios-trust-center 'https://trust.iverios.eu/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "eu-iverios-trust-center": {
      "url": "https://trust.iverios.eu/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "eu-iverios-trust-center": {
      "type": "http",
      "url": "https://trust.iverios.eu/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.eu-iverios-trust-center]
url = "https://trust.iverios.eu/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-iverios-trust-center": {
      "type": "remote",
      "url": "https://trust.iverios.eu/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add eu-iverios-trust-center --url 'https://trust.iverios.eu/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  eu-iverios-trust-center:
    url: "https://trust.iverios.eu/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "eu-iverios-trust-center": {
      "Transport": "http",
      "Url": "https://trust.iverios.eu/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add eu-iverios-trust-center -t streamable-http -u 'https://trust.iverios.eu/mcp'
```

### Other

```json
{
  "mcpServers": {
    "eu-iverios-trust-center": {
      "type": "http",
      "url": "https://trust.iverios.eu/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1660 → 1979
- [functional] New tool “get_answers”
- [functional] New tool “list_services”

### 2026-11-19 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 72)

First indexed and scored.

## MCP tools (15)

### `about_iverios` (~83 tokens)

About IVERIOS

Information about IVERIOS and IVERIOS Trust Center: what it is, how vendors publish a trust center and how customers (assessors) use it — access requests, NDA, questionnaires, AI assistants — plus pricing, FAQ and the other IVERIOS tools. No sign-in needed.

Input parameters:

- `topic` (string): Optional section; omit for everything

### `sign_in` (~62 tokens)

Sign in for restricted information

Sign in with your e-mail (OAuth) to see restricted information in trust centers where you are an approved visitor. Call this when the user asks for documents or details that are shared only with approved visitors. Returns who you are signed in as and your approved trust centers.

### `list_trust_centers` (~78 tokens)

Find trust centers

Lists IVERIOS trust centers you can query: those where you are an approved visitor (full access) and, with a query, public trust centers matching a company name or domain. Call this first to get the trust_center id for the other tools.

Input parameters:

- `query` (string): Company name or domain to search for (optional)

### `get_overview` (~141 tokens)

Trust center overview

Summary of the company's security and compliance posture: certificates, regulations, number of security controls per area, privacy and data location, subprocessors, available documents, FAQ and security contact. Start here.

Input parameters:

- `language` (string): Optional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `list_services` (~71 tokens)

Services

The services this trust center covers, with the number of answers to customer due-diligence questions per service and whether your access includes each service. Use the service id with get_answers.

Input parameters:

- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `get_answers` (~207 tokens)

Answers to customer due-diligence questions

The company's confirmed answers to the security questions customers ask in supplier risk assessments (yes / partial / no / not applicable, with details), for one service (company-wide answers included). Each answer has a stable question_key (IVERIOS question bank qb-2) and domain. Approved visitors see the services their access includes.

Input parameters:

- `domain` (string): Optional domain filter (e.g. access, data, incident, continuity)
- `language` (string): Optional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
- `service_id` (string): Service id from list_services; optional when the company has one service
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `list_certificates` (~138 tokens)

Certificates

Certifications (e.g. ISO/IEC 27001, SOC 2) with status, issuer, accreditation, issue/expiry dates, scope and the certificate document if available.

Input parameters:

- `language` (string): Optional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `list_controls` (~134 tokens)

Security controls

Implemented security controls with descriptions. Optional filter by area: governance, infrastructure, data, application, access, incident, continuity.

Input parameters:

- `area` (string)
- `language` (string): Optional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `get_infrastructure` (~169 tokens)

Infrastructure overview

High-level infrastructure overview: components by layer (users, edge, application, data, backup, identity, monitoring, external) and type, provider/region, network zone, internet exposure, authentication, the security controls on each component, and the connections between components (e.g. "Web application → Customer database (mTLS)").

Input parameters:

- `language` (string): Optional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `get_privacy` (~129 tokens)

Privacy

Data processing description, data location, DPO contact and international data transfers (GDPR Chapter V: countries, transfer mechanisms, safeguards).

Input parameters:

- `language` (string): Optional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `list_subprocessors` (~112 tokens)

Subprocessors

Subprocessors with purpose, location and transfer mechanism.

Input parameters:

- `language` (string): Optional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `list_documents` (~76 tokens)

Documents

Published documents (policies, audit reports, certificates…) with category, validity and whether the text is accessible with the current access level. Use get_document_text to read one.

Input parameters:

- `category` (string)
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `get_document_text` (~84 tokens)

Read document

Plain text of an accessible document, in slices of up to 20000 characters. Use next_offset to continue.

Input parameters:

- `document_id` (string, required): Document id from list_documents
- `offset` (integer): Character offset (default 0)
- `trust_center` (string, required): Trust center id (from list_trust_centers), its domain or the exact company name.

### `search` (~202 tokens)

Search

Keyword search across the trust center content and accessible documents. Returns matching passages with their source. Use short keywords (e.g. "encryption at rest", "backup", "MFA"), not full sentences. Without trust_center, searches the trust centers where you are an approved visitor and those whose company name or domain appears in the query (e.g. "Acme encryption at rest").

Input parameters:

- `language` (string): Optional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
- `limit` (integer): Max results (default 8)
- `query` (string, required)
- `trust_center` (string): Trust center id (from list_trust_centers), its domain or the exact company name. Optional for search.

Output parameters:

- `results` (array)

### `fetch` (~78 tokens)

Fetch

Full text of a search result by its id (a trust center section such as "sec:privacy" or a document "doc:<id>"), with title and source URL for citation. Ids look like "<trust_center>/sec:privacy" or "<trust_center>/doc:<id>".

Input parameters:

- `id` (string, required): Result id from search

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eu-iverios-trust-center/trust#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72

## Common questions

### What is the IVERIOS Trust Center MCP server?

IVERIOS Trust Center is an MCP server listed in the public MCP registry as eu.iverios/trust-center. Vendor security & compliance (certifications, controls, subprocessors) from IVERIOS Trust Centers. This page covers its hosted endpoint (https://trust.iverios.eu/mcp).

### Is the IVERIOS Trust Center MCP server safe to use?

IVERIOS Trust Center scores 75 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 IVERIOS Trust Center MCP server expose?

IVERIOS Trust Center exposes 15 tools: about_iverios, sign_in, list_trust_centers, get_overview, list_services, and 10 more. Their descriptions and schemas cost roughly 1,764 tokens of context every time the server is loaded.

### Does the IVERIOS Trust Center MCP server require authentication?

No. We connected to IVERIOS Trust Center without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the IVERIOS Trust Center MCP server still maintained?

IVERIOS Trust Center is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the IVERIOS Trust Center MCP server?

VerifyMCP ran 13 checks on IVERIOS Trust Center, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://trust.iverios.eu/mcp
- Website: https://trust.iverios.eu/connect
- Changelog RSS feed: https://verifymcp.io/servers/eu-iverios-trust-center/trust.xml
- Changelog JSON feed: https://verifymcp.io/servers/eu-iverios-trust-center/trust/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/eu-iverios-trust-center/trust.json
- HTML version of this page: https://verifymcp.io/servers/eu-iverios-trust-center/trust
