IVERIOS Trust Center
REMOTE · TRUST.IVERIOS.EU
Vendor security & compliance (certifications, controls, subprocessors) from IVERIOS Trust Centers
Available components
Last scanned (17 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
- Structured output schemas are declared (13% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1660 → 1979 ▼ functional
- New tool “get_answers” functional
- New tool “list_services” functional
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 72
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 21 Nov 2026 · Probed https://trust.iverios.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trust.iverios.eu | CN=YE2,O=Let's Encrypt,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 62d24168a10317ef46b7b735d4fb5b6c6e5 |
| SANs: trust.iverios.eu | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trust.iverios.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | DS published | 35926 | 8 | Verified |
| iverios.eu. | No DS | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trust.iverios.eu/mcp | Verified | 200 | |
| http (plaintext) | http://trust.iverios.eu/mcp | HTTPS enforced | 308 | https://trust.iverios.eu/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 →
about_iverios About IVERIOS ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional section; omit for everything |
No output schema declared.
No examples provided.
fetch Fetch ~78
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>".
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Result id from search |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_answers Answers to customer due-diligence questions ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
get_document_text Read document ~84
Plain text of an accessible document, in slices of up to 20000 characters. Use next_offset to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | Document id from list_documents |
| offset | integer | – | Character offset (default 0) |
| trust_center | string | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
get_infrastructure Infrastructure overview ~169
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)").
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
get_overview Trust center overview ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
get_privacy Privacy ~129
Data processing description, data location, DPO contact and international data transfers (GDPR Chapter V: countries, transfer mechanisms, safeguards).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
list_certificates Certificates ~138
Certifications (e.g. ISO/IEC 27001, SOC 2) with status, issuer, accreditation, issue/expiry dates, scope and the certificate document if available.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
list_controls Security controls ~134
Implemented security controls with descriptions. Optional filter by area: governance, infrastructure, data, application, access, incident, continuity.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
list_documents Documents ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| trust_center | string | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
list_services Services ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| trust_center | string | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
list_subprocessors Subprocessors ~112
Subprocessors with purpose, location and transfer mechanism.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Trust center id (from list_trust_centers), its domain or the exact company name. |
No output schema declared.
No examples provided.
list_trust_centers Find trust centers ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Company name or domain to search for (optional) |
No output schema declared.
No examples provided.
search Search ~202
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").
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| trust_center | string | – | Trust center id (from list_trust_centers), its domain or the exact company name. Optional for search. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
sign_in Sign in for restricted information ~62
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · trust.iverios.eu
claude mcp add --transport http eu-iverios-trust-center 'https://trust.iverios.eu/mcp'
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.