IVERIOS Trust Center MCP server
eu.iverios/trust-centeriverios.eustreamable-httpv1.2.0Scanned
Vendor security & compliance (certifications, controls, subprocessors) from IVERIOS Trust Centers
13 tools: 2 change things and 11 only read.
- Reads private data · 6
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the IVERIOS Trust Center MCP server can do
The IVERIOS Trust Center MCP server is published by iverios.eu, a domain the MCP Registry verified. It has 13 tools. It can create or change data (2 tools: about_iverios and sign_in), but cannot delete data. 11 tools only read.
6 tools read private data (get_overview, get_privacy, list_documents and 3 more); 2 tools bring in text other people can write (get_infrastructure and fetch).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Changes things 2Claude Code: ask
about_iveriosInformation 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 a…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
sign_inSign in with your e-mail (OAuth) to see restricted information in trust centers where you are an approved visitor.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 11Show 11 read-only tools
fetchFull 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.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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>".
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_document_textPlain text of an accessible document, in slices of up to 20000 characters.Reads private dataNo findings
Why it is in this group
- The name "get_document_text" says "get": a word for reading.
What it can reach
- private-dataThe name "get_document_text" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it Plain text of an accessible document, in slices of up to 20000 characters. Use next_offset to continue.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_infrastructureHigh-level infrastructure overview: components by layer (users, edge, application, data, backup, identity, monitoring, external) and type, provider/region, network zone, internet e…Reads text others writeNo findings
Why it is in this group
- The name "get_infrastructure" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "internet": it reads web pages, which anyone can write.
Description, as the server wrote it 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)").
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_overviewSummary of the company's security and compliance posture: certificates, regulations, number of security controls per area, privacy and data location, subprocessors, available docum…Reads private dataNo findings
Why it is in this group
- The name "get_overview" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_privacyData processing description, data location, DPO contact and international data transfers (GDPR Chapter V: countries, transfer mechanisms, safeguards).Reads private dataNo findings
Why it is in this group
- The name "get_privacy" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
Description, as the server wrote it Data processing description, data location, DPO contact and international data transfers (GDPR Chapter V: countries, transfer mechanisms, safeguards).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_certificatesCertifications (e.g.No findings
Why it is in this group
- The name "list_certificates" says "list": a word for reading.
Description, as the server wrote it Certifications (e.g. ISO/IEC 27001, SOC 2) with status, issuer, accreditation, issue/expiry dates, scope and the certificate document if available.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_controlsImplemented security controls with descriptions.No findings
Why it is in this group
- The name "list_controls" says "list": a word for reading.
Description, as the server wrote it Implemented security controls with descriptions. Optional filter by area: governance, infrastructure, data, application, access, incident, continuity.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_documentsPublished documents (policies, audit reports, certificates…) with category, validity and whether the text is accessible with the current access level.Reads private dataNo findings
Why it is in this group
- The name "list_documents" says "list": a word for reading.
What it can reach
- private-dataThe name "list_documents" says "list" and "document": it reads documents.
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_subprocessorsSubprocessors with purpose, location and transfer mechanism.No findings
Why it is in this group
- The name "list_subprocessors" says "list": a word for reading.
Description, as the server wrote it Subprocessors with purpose, location and transfer mechanism.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_trust_centersLists 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.No findings
Why it is in this group
- The name "list_trust_centers" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
searchKeyword search across the trust center content and accessible documents.Reads private dataNo findings
Why it is in this group
- The name "search" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it 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").
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data6
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:19 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://trust.iverios.eu/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://trust.iverios.eu
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://trust.iverios.eu/mcp: tools/list returned 13 tools to an anonymous client, including about_iverios (write), sign_in (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http trust-center https://trust.iverios.eu/mcpclaude mcp add --transport http trust-center https://trust.iverios.eu/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__trust-center__list_trust_centers",
"mcp__trust-center__get_overview",
"mcp__trust-center__list_certificates",
"mcp__trust-center__list_controls",
"mcp__trust-center__get_infrastructure",
"mcp__trust-center__get_privacy",
"mcp__trust-center__list_subprocessors",
"mcp__trust-center__list_documents",
"mcp__trust-center__get_document_text",
"mcp__trust-center__search",
"mcp__trust-center__fetch"
],
"ask": [
"mcp__trust-center__about_iverios",
"mcp__trust-center__sign_in"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trust-center. Review it before you use it.
Capability tags behind 7 rules
- mcp__trust-center__get_overview private-data
- mcp__trust-center__get_infrastructure untrusted-input
- mcp__trust-center__get_privacy private-data
- mcp__trust-center__list_documents private-data
- mcp__trust-center__get_document_text private-data
- mcp__trust-center__search private-data
- mcp__trust-center__fetch private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/eu.iverios/trust-center/verify?hash=1dc576d7186750befa7fd729e616cd49c34975070ba0d80026605e8a963ccc6a" | jq -e '.changed == false'Pinned hash 1dc576d71867, from Nov 14, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/eu.iverios/trust-center/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/eu.iverios/trust-center)Source: MCP Registry. Synced Nov 14, 2026, 20:17 UTC.
IVERIOS Trust Center MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the IVERIOS Trust Center MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the IVERIOS Trust Center MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the IVERIOS Trust Center MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the IVERIOS Trust Center MCP server have?
- 13 tools: 2 write, 11 read. about_iverios, sign_in, list_trust_centers, get_overview, list_certificates, list_controls, get_infrastructure, get_privacy and 5 more.
Does the IVERIOS Trust Center MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the IVERIOS Trust Center MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the IVERIOS Trust Center MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.