iResolve Private Alignment Rooms
REMOTE · APP.IRESOLVE.IO
Private pre-work and calm double-blind summaries in 100+ languages (zero PII exposed).
Available components
Last scanned (16 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Communication
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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 761 tokens (~152/item across 5 items; 3 tools + 2 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 +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.
- 19 Nov 26 +4
- Tool “create_alignment_room_link” rewrote its description, which is the text the model reads security
- Tool “get_prework_methodology” rewrote its description, which is the text the model reads security
- Tool “list_alignment_scenarios” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: fair → good functional
- “create_alignment_room_link” reworded the description of “locale” cosmetic
- “create_alignment_room_link” reworded the description of “scenarioSlug” cosmetic
- “create_alignment_room_link” reworded the description of “topology” cosmetic
- “get_prework_methodology” reworded the description of “locale” cosmetic
- “list_alignment_scenarios” reworded the description of “locale” cosmetic
- Tool “create_alignment_room_link” changed its title: Create Self-Serve Private Pre-Work Room Link cosmetic
- Tool “get_prework_methodology” changed its title: Get Peer-Reviewed Pre-Work Methodology & Pricing cosmetic
- Tool “list_alignment_scenarios” changed its title: List Bilingual Alignment Scenarios cosmetic
- 18 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.
- 17 Nov 26 +3
- Tool “create_alignment_room_link” rewrote its description, which is the text the model reads security
- Tool “list_alignment_scenarios” rewrote its description, which is the text the model reads security
- Schema quality: 116 → 268 ▼ functional
- Tool “create_alignment_room_link” now declares an output schema ▲ functional
- Tool “list_alignment_scenarios” now declares an output schema ▲ functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- First check of Tool coverage: 100 functional
- New resource “Thomson Reuters Peer-Reviewed Study — (2025) 34 ADRJ 75, pp. 75-78” functional
- New resource “iResolve Bilingual Alignment Scenarios (EN/FR)” functional
- Server version: 1.0.0 → 1.0.2 functional
- New tool “get_prework_methodology” functional
- 16 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 68
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://app.iresolve.io/api/integrations/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.iresolve.io | CN=YR2,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 60d365916874b455c650cdf5da5ab4e7314 |
| SANs: app.iresolve.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.iresolve.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| iresolve.io. | 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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self' https://accounts.google.com; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://pagead2.googlesyndication.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://pagead2.googlesyndication.com https://www.google.com https://www.google.ca; font-src 'self' data:; connect-src 'self' https://www.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://pagead2.googlesyndication.com https://www.google-analytics.com https://analytics.google.com; frame-src 'self' https://td.doubleclick.net https://www.googletagmanager.com; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.iresolve.io/api/integrations/mcp | Verified | 200 | |
| http (plaintext) | http://app.iresolve.io/api/integrations/mcp | HTTPS enforced | 308 | https://app.iresolve.io/api/integrations/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 →
create_alignment_room_link Create Self-Serve Private Pre-Work Room Link ~291
Purpose: Builds a deterministic self-serve HTTPS room-launcher URL (?utm_source=mcp) to start confidential solo talk-prep or double-blind written alignment in 100+ languages. Use when: Providing a user or team with a clickable link to start solo pre-work (solo), a 1-on-1 summary room (1:1), or an untraceable k>=3 group sounding board (3+). Do not use when: Enumerating valid scenario slugs (use list_alignment_scenarios) or fetching ADRJ citations and pricing (use get_prework_methodology); never pass private dispute details in arguments. Returns & Zero-PII Guarantee: Purely deterministic URL formatter with zero server state mutation, safe fallback to root hub on unknown slugs, and 100% zero-PII MCP Gateway call logs.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Interface and guide locale ('en' default or 'fr' for French). |
| scenarioSlug | string | – | Optional kebab-case scenario slug from list_alignment_scenarios (for example workplace-conversation-alignment). Omitted or unrecognized values safely fall back to the public root hub. |
| topology | string | – | Intended alignment mode: 'solo' for 100% private in-person talk prep, '1:1' (default) for bilateral calm summary exchange, or '3+' for anonymous group sounding boards. |
| Name | Type | Req | Description |
|---|---|---|---|
| canonicalWebsiteUrl | string | yes | Canonical public guide URL on https://www.iresolve.io. |
| entryUrl | string | yes | Self-serve HTTPS entry URL tagged with ?utm_source=mcp. |
| locale | string | yes | Resolved two-letter locale code. |
| topology | string | yes | Resolved room topology metadata. |
No examples provided.
get_prework_methodology Get Peer-Reviewed Pre-Work Methodology & Pricing ~191
Purpose: Returns iResolve concentric alignment architecture (Self -> Another -> Group/System), Level-1 dual-path exit options, USD self-serve pricing ($0/$15/$29), and peer-reviewed (2025) 34 ADRJ 75, pp. 75-78 citation metadata. Use when: Explaining double-blind room isolation, practitioner non-displacement, pricing tiers, or academic provenance. Do not use when: Listing scenario templates (use list_alignment_scenarios) or generating a room launch link (use create_alignment_room_link). Returns & Zero-PII Guarantee: Stateless, read-only, idempotent reference payload defaulting to English when locale is omitted, with zero external network calls and 100% zero-PII MCP Gateway call logs.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Output language for methodology summary and dual-path options ('en' default or 'fr'). |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | Peer-reviewed Thomson Reuters ADRJ bibliographic citation and Informit DOI. |
| concentricModel | string | yes | Summary of the Self -> Another -> Group/System private pre-work model. |
| deliverabilityPostureUrl | string | – | Machine-readable BIMI/DMARC/MTA-STS deliverability posture URL. |
| dualPathExit | array | yes | Two voluntary Level-1 completion paths (in-person talking points vs. calm written line). |
| pricingUsd | object | – | Transparent self-serve USD pricing summary. |
| provider | string | – | Operating legal entity (7993064 Canada Inc.). |
| scholarlyCitationUrl | string | – | Canonical Informit DOI record URL for (2025) 34 ADRJ 75, pp. 75-78. |
| trustPostureUrl | string | – | Machine-readable trust and PIPEDA/SOC 2 posture manifest URL. |
| websiteUrl | string | yes | Canonical public homepage URL (https://www.iresolve.io). |
No examples provided.
list_alignment_scenarios List Bilingual Alignment Scenarios ~185
Purpose: Lists all 14 public iResolve private pre-work and calm written alignment scenario templates across English and French. Use when: Selecting a workplace, co-founder, board, commercial, condo, or family scenario slug before creating a room link. Do not use when: Constructing a launch URL directly (use create_alignment_room_link) or retrieving pricing and peer-reviewed methodology (use get_prework_methodology). Returns & Zero-PII Guarantee: Stateless, read-only, idempotent catalog lookup with zero authentication and zero database writes; confidential party narratives never enter MCP tool inputs or outputs, keeping MCP Gateway JSON-RPC call logs 100% zero-PII.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Optional ISO language filter ('en' for 7 English entries or 'fr' for 7 French entries). Omit to return all 14 bilingual scenario entries. |
| Name | Type | Req | Description |
|---|---|---|---|
| scenarios | array | yes | Matched public scenario catalog entries with canonical and app launch URLs. |
No examples provided.
How do I install the iResolve Private Alignment Rooms MCP server?
iResolve Private Alignment Rooms is a hosted endpoint at https://app.iresolve.io/api/integrations/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 · app.iresolve.io
claude mcp add --transport http io-iresolve-app-mcp-server 'https://app.iresolve.io/api/integrations/mcp'
What is the iResolve Private Alignment Rooms MCP server?
iResolve Private Alignment Rooms is an MCP server listed in the public MCP registry as io.iresolve.app/mcp-server. Private pre-work and calm double-blind summaries in 100+ languages (zero PII exposed). This page covers its hosted endpoint (https://app.iresolve.io/api/integrations/mcp).
Is the iResolve Private Alignment Rooms MCP server safe to use?
iResolve Private Alignment Rooms scores 77 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 iResolve Private Alignment Rooms MCP server expose?
iResolve Private Alignment Rooms exposes 3 tools: list_alignment_scenarios, create_alignment_room_link, get_prework_methodology. Their descriptions and schemas cost roughly 667 tokens of context every time the server is loaded.
Does the iResolve Private Alignment Rooms MCP server require authentication?
No. We connected to iResolve Private Alignment Rooms without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the iResolve Private Alignment Rooms MCP server still maintained?
iResolve Private Alignment Rooms 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 iResolve Private Alignment Rooms MCP server?
VerifyMCP ran 13 checks on iResolve Private Alignment Rooms, 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.