# Raziel (remote · mcp.tide.org)

MCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis

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

## Components

- remote · `mcp.tide.org`: 75/100 (this document), [markdown](https://verifymcp.io/servers/tide-foundation-raziel/mcp.md), [page](https://verifymcp.io/servers/tide-foundation-raziel/mcp)
- npm · `@tideorg/mcp`: 67/100, [markdown](https://verifymcp.io/servers/tide-foundation-raziel/tideorg-mcp.md), [page](https://verifymcp.io/servers/tide-foundation-raziel/tideorg-mcp)

## Channel facts

- Endpoint: `https://mcp.tide.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.9.4`

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

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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).
  - Tool/resource definitions use about 1124 tokens (~70/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http tide-foundation-raziel https://mcp.tide.org/mcp
```

### Codex

```toml
[mcp_servers.tide-foundation-raziel]
url = "https://mcp.tide.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tide-foundation-raziel": {
      "type": "remote",
      "url": "https://mcp.tide.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tide-foundation-raziel --url https://mcp.tide.org/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tide-foundation-raziel:
    url: "https://mcp.tide.org/mcp"
```

### Other

```json
{
  "mcpServers": {
    "tide-foundation-raziel": {
      "type": "http",
      "url": "https://mcp.tide.org/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-08-03 (score 75, +1)

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

### 2026-08-01 (score 74, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 71, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Stability: 0.10 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional] Server version: 1.9.1 → 1.9.4
- [cosmetic] “tide_prompt” reworded the description of “name”
- [cosmetic] “tide_skill” reworded the description of “name”
- [cosmetic] “tide_canon” reworded the description of “name”

### 2026-07-29 (score 71, +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-07-27 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 69)

First indexed and scored.

## MCP tools (16)

### `tide_list` (~38 tokens)

List all available content in the Tide agent pack by category

Input parameters:

- `category` (string, required): Which category to list, or 'all' for everything

### `tide_canon` (~117 tokens)

Read a canon file (invariants, anti-patterns, concepts, framework-matrix, feature-mapping, troubleshooting, tidecloak-bootstrap, etc.)

Input parameters:

- `name` (string, required): Canon file name. Available: anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, redirect-handler, se…

### `tide_playbook` (~154 tokens)

Read a step-by-step playbook for a specific Tide task

Input parameters:

- `name` (string, required): Playbook name. Available: add-auth-nextjs-existing, add-auth-nextjs-fresh, add-rbac-nextjs, bootstrap-realm-from-template, configure-e2ee-roles-and-policies, deploy-tidecloak-docker, diagnose-broken-…

### `tide_skill` (~90 tokens)

Read a composable skill definition

Input parameters:

- `name` (string, required): Skill name. Available: tide-diagnostics, tide-integration, tide-learning-capture, tide-mcp-qa, tide-rbac-and-e2ee, tide-red-team, tide-reviewer, tide-route-and-api-protection, tide-scenario-resolver,…

### `tide_prompt` (~62 tokens)

Read a reusable starter prompt from the pack

Input parameters:

- `name` (string, required): Prompt file name. Available: add-admin-approval-flow, build-private-customer-portal, migrate-generic-auth-to-tide, red-team-review, secure-existing-app, security-gap-analysis

### `tide_adapter` (~46 tokens)

Read an adapter instruction file (AGENTS, CLAUDE, replit)

Input parameters:

- `name` (string, required): Adapter file name. Available: AGENTS, CLAUDE, replit

### `tide_list_scenarios` (~21 tokens)

List all available scenario patterns under reference-apps/

### `tide_scenario` (~61 tokens)

Read a scenario summary from reference-apps/<scenario>/scenario.md

Input parameters:

- `name` (string, required): Scenario name. Available: encrypted-communication, git-pr-signing-service, iga-admin-governance, organisation-password-manager, policy-governed-signing

### `tide_scenario_manifest` (~62 tokens)

Read a scenario manifest from reference-apps/<scenario>/manifest.yaml

Input parameters:

- `name` (string, required): Scenario name. Available: encrypted-communication, git-pr-signing-service, iga-admin-governance, organisation-password-manager, policy-governed-signing

### `tide_scenario_roles` (~67 tokens)

Read a scenario role-policy matrix from reference-apps/<scenario>/role-policy-matrix.md

Input parameters:

- `name` (string, required): Scenario name. Available: encrypted-communication, git-pr-signing-service, iga-admin-governance, organisation-password-manager, policy-governed-signing

### `tide_scenario_bootstrap` (~66 tokens)

Read a scenario bootstrap sequence from reference-apps/<scenario>/bootstrap-sequence.md

Input parameters:

- `name` (string, required): Scenario name. Available: encrypted-communication, git-pr-signing-service, iga-admin-governance, organisation-password-manager, policy-governed-signing

### `tide_choose_scenario` (~49 tokens)

Match a user request to a known scenario pattern before falling back to generic playbooks

Input parameters:

- `situation` (string, required): Describe the app or problem, e.g. 'build an organisation password manager'

### `tide_choose_playbook` (~47 tokens)

Recommend the right playbook for a given situation

Input parameters:

- `situation` (string, required): Describe what the builder wants to do, e.g. 'add login to a new Next.js app'

### `tide_security_analysis` (~128 tokens)

Analyze an EXISTING (possibly non-Tide) system for security gaps and map them to Tide capabilities. Returns the Security Analyst role instructions, the security gap mapping table (SG-01…SG-18), and the runtime-probe procedures. Use this when the user asks 'do a security analysis', 'where is my auth weak', or 'what would Tide change about my security'.

Input parameters:

- `include_runtime_probes` (boolean): Include the runtime-confirmation probe procedures (canon/security-runtime-probes.md). Only relevant when the operator is authorized to probe a live target. Defaults to true.

### `tide_hosting` (~92 tokens)

Explain where TideCloak can run: self-hosted vs partner-hosted (Skycloak, a managed TideCloak-as-a-service). Returns the hosting decision, the trust model, the Skycloak API reference, and the provisioning playbook. Use when the user asks about a hosted/managed option, not wanting to run their own infrastructure, or 'can someone host TideCloak for us'.

### `tide_gaps` (~24 tokens)

Read the gap register — what is still uncertain or unresolved in the pack

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tide-foundation-raziel/mcp#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 74
- 2026-08-01: 74
- 2026-07-31: 72
- 2026-07-30: 71
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 70
- 2026-07-26: 69

## Links

- Remote endpoint: https://mcp.tide.org/mcp
- Repository: https://github.com/tide-foundation/raziel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/tide-foundation-raziel/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/tide-foundation-raziel/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/tide-foundation-raziel/mcp