# iResolve Private Alignment Rooms (remote · app.iresolve.io)

Private pre-work and calm double-blind summaries in 100+ languages (zero PII exposed).

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `app.iresolve.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-iresolve-app-mcp-server/api-integrations-mcp.md), [page](https://verifymcp.io/servers/io-iresolve-app-mcp-server/api-integrations-mcp)

## Channel facts

- Endpoint: `https://app.iresolve.io/api/integrations/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## 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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 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.

### Claude

```bash
claude mcp add --transport http io-iresolve-app-mcp-server 'https://app.iresolve.io/api/integrations/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-iresolve-app-mcp-server": {
      "url": "https://app.iresolve.io/api/integrations/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-iresolve-app-mcp-server": {
      "type": "http",
      "url": "https://app.iresolve.io/api/integrations/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-iresolve-app-mcp-server]
url = "https://app.iresolve.io/api/integrations/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-iresolve-app-mcp-server": {
      "type": "remote",
      "url": "https://app.iresolve.io/api/integrations/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-iresolve-app-mcp-server --url 'https://app.iresolve.io/api/integrations/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-iresolve-app-mcp-server:
    url: "https://app.iresolve.io/api/integrations/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-iresolve-app-mcp-server": {
      "Transport": "http",
      "Url": "https://app.iresolve.io/api/integrations/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-iresolve-app-mcp-server -t streamable-http -u 'https://app.iresolve.io/api/integrations/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-iresolve-app-mcp-server": {
      "type": "http",
      "url": "https://app.iresolve.io/api/integrations/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 77, +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-19 (score 76, +4)

- [security] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional] Schema quality: fair → good
- [cosmetic] “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

### 2026-11-18 (score 72, +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-17 (score 71, +3)

- [security] 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
- [functional regression] Schema quality: 116 → 268
- [functional improvement] Tool “create_alignment_room_link” now declares an output schema
- [functional improvement] 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”

### 2026-11-16 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 68)

First indexed and scored.

## MCP tools (3)

### `list_alignment_scenarios` (~185 tokens)

List Bilingual Alignment Scenarios

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.

Input parameters:

- `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.

Output parameters:

- `scenarios` (array): Matched public scenario catalog entries with canonical and app launch URLs.

### `create_alignment_room_link` (~291 tokens)

Create Self-Serve Private Pre-Work Room Link

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.

Input parameters:

- `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.

Output parameters:

- `canonicalWebsiteUrl` (string): Canonical public guide URL on https://www.iresolve.io.
- `entryUrl` (string): Self-serve HTTPS entry URL tagged with ?utm_source=mcp.
- `locale` (string): Resolved two-letter locale code.
- `topology` (string): Resolved room topology metadata.

### `get_prework_methodology` (~191 tokens)

Get Peer-Reviewed Pre-Work Methodology & Pricing

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.

Input parameters:

- `locale` (string): Output language for methodology summary and dual-path options ('en' default or 'fr').

Output parameters:

- `citation` (string): Peer-reviewed Thomson Reuters ADRJ bibliographic citation and Informit DOI.
- `concentricModel` (string): Summary of the Self -> Another -> Group/System private pre-work model.
- `deliverabilityPostureUrl` (string): Machine-readable BIMI/DMARC/MTA-STS deliverability posture URL.
- `dualPathExit` (array): 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): Canonical public homepage URL (https://www.iresolve.io).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-iresolve-app-mcp-server/api-integrations-mcp#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 76
- 2026-11-18: 72
- 2026-11-17: 71
- 2026-11-16: 68
- 2026-11-15: 68

## Common questions

### 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.

## Links

- Remote endpoint: https://app.iresolve.io/api/integrations/mcp
- Website: https://www.iresolve.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-iresolve-app-mcp-server/api-integrations-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-iresolve-app-mcp-server/api-integrations-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-iresolve-app-mcp-server/api-integrations-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-iresolve-app-mcp-server/api-integrations-mcp
