Raziel
NPM · @TIDEORG/MCP · 2 COMPONENTS · SCANNED SEP 21
MCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 31 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3636 tokens (~181/item across 20 items; 20 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 Management83
- Stability observed for 25 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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
How do I install the Raziel MCP server?
Raziel runs locally as an npm package, launched with npx -y @tideorg/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @tideorg/mcp
claude mcp add tide-foundation-raziel -- npx -y @tideorg/mcp
{
"mcpServers": {
"tide-foundation-raziel": {
"command": "npx",
"args": [
"-y",
"@tideorg/mcp"
]
}
}
} {
"servers": {
"tide-foundation-raziel": {
"command": "npx",
"args": [
"-y",
"@tideorg/mcp"
]
}
}
} codex mcp add tide-foundation-raziel -- npx -y @tideorg/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tide-foundation-raziel": {
"type": "local",
"command": [
"npx",
"-y",
"@tideorg/mcp"
],
"enabled": true
}
}
} openclaw mcp add tide-foundation-raziel --command npx --arg -y --arg @tideorg/mcp
mcp_servers:
tide-foundation-raziel:
command: "npx"
args: ["-y", "@tideorg/mcp"] {
"McpServers": {
"tide-foundation-raziel": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@tideorg/mcp"
]
}
}
} assistant mcp add tide-foundation-raziel -t stdio -c npx -a -y @tideorg/mcp
{
"mcpServers": {
"tide-foundation-raziel": {
"command": "npx",
"args": [
"-y",
"@tideorg/mcp"
]
}
}
} 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.
- 21 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.83 functional
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 19 Sept 26 −1
- Stability: pass → 0.97 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 13 Sept 26 −2
- Stability: pass → 0.90 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
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 Sept 2026 · Analysed npm/@tideorg/mcp@1.9.23
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
tide_adapter ~46
Read an adapter instruction file (AGENTS, CLAUDE, replit)
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Adapter file name. Available: AGENTS, CLAUDE, replit |
No output schema declared.
No examples provided.
tide_blast_radius ~146
Run a Blast Radius Assessment of an EXISTING app: an adversarial, vendor-neutral map of where authority is concentrated to a single point (whoever obtains that one thing obtains everything it governs), scored by blast radius (Total/Systemic/Contained/Limited) across three cores — Identity, Governance, Access — and delivered as a director-facing PDF. Phase 1 names no vendor; an opt-in Phase 2 companion explains how TideCloak shrinks each blast radius. Use this when the user wants to 'assess', 'red team', 'threat model', 'find the security gaps in', or make a before/after security case for an existing application.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tide_branding ~272
BRAND THE ENCLAVE FOR THE USER — generate a logo + background and upload them so the Tide login/approval screen is branded. Returns a single ready-to-run command that generates the assets (no image model needed), validates them, uploads both, and saves+signs the IdP settings. Also returns the VERIFIED upload contract (multipart parts, the png/jpg/jpeg/gif/webp allowlist with SVG REJECTED, the 5 MB cap, set-branding = save AND re-sign, IGA-exempt) plus image-model prompts for agents that can generate images. Pass realm/accent/appName to get the command pre-filled. CALL THIS whenever branding, a logo, a background, theming or 'skinning' the enclave or login screen comes up — then RUN the command; do not just describe it.
| Name | Type | Req | Description |
|---|---|---|---|
| accent | string | – | Hex accent colour without '#', e.g. '2f6f4e'. Default 1f6feb. |
| appName | string | – | App name. Deterministically varies the mark's geometry so realms look distinct. |
| realm | string | – | Realm to brand, e.g. 'myapp'. Fills in the command. |
| tidecloakUrl | string | – | Base URL. Default http://localhost:8080. |
No output schema declared.
No examples provided.
tide_canon ~136
Read a canon file (invariants, anti-patterns, concepts, framework-matrix, feature-mapping, troubleshooting, tidecloak-bootstrap, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Canon file name. Available: agent-authority, anti-patterns, breach-precedents, concepts, custom-contracts, feature-mapping, framework-matrix, hosting-options, iga-change-requests-api, invariants, red… |
No output schema declared.
No examples provided.
tide_choose_playbook ~47
Recommend the right playbook for a given situation
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | Describe what the builder wants to do, e.g. 'add login to a new Next.js app' |
No output schema declared.
No examples provided.
tide_choose_scenario ~49
Match a user request to a known scenario pattern before falling back to generic playbooks
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | Describe the app or problem, e.g. 'build an organisation password manager' |
No output schema declared.
No examples provided.
tide_dpop_asset ~177
Returns the CONTENTS of `public/tide_dpop_auth.html` — the DPoP relay page the Tide enclave loads during login — plus its sha256, the required next.config.ts rewrite/CSP wiring, and how to verify. The file is NOT shipped in the @tidecloak/* npm packages and is NOT in the TideCloak container, so there is nowhere else to get it: without this tool people search GitHub and find a STALE copy that posts to window.parent, which breaks the popup fallback and fails login with TIDE-SWE-UNHANDLED. CALL THIS whenever DPoP is enabled (it is on by default), whenever a login fails with TIDE-SWE-UNHANDLED or 'Popup DPoP verification failed to load', and before copying this file from anywhere else.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tide_gaps ~24
Read the gap register — what is still uncertain or unresolved in the pack
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tide_hosting ~176
Where TideCloak runs: local Docker vs partner-hosted (Skycloak managed TideCloak-as-a-service). Returns the local-vs-hosted decision with the honest trade-offs, the trust model, the verified Skycloak API reference (correct cluster field names and the required version), and the full provisioning playbook. CALL THIS BEFORE STARTING ANY TIDECLOAK DEPLOYMENT — the choice must be made up front (I-17) because a realm cannot be moved between local and hosted afterwards. Triggers: 'deploy to production', 'deploy TideCloak', 'go live', 'host this somewhere', 'managed option', 'stable URL', 'can someone host TideCloak for us', or any request to stand up an instance where local-vs-hosted has not been settled.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tide_list ~38
List all available content in the Tide agent pack by category
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Which category to list, or 'all' for everything |
No output schema declared.
No examples provided.
tide_list_scenarios ~21
List all available scenario patterns under reference-apps/
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tide_onboarding ~303
STOP KEYCLOAK'S 'UPDATE ACCOUNT INFORMATION' PAGE and collect the details in-app instead. Tide asserts ONLY a username (the vuid) -- no email, no name -- so Keycloak blocks new users on an unstyled form showing a 64-hex username. Returns: a read-only DIAGNOSTIC that identifies which of FOUR mechanisms is causing the page (they need different fixes), the script that fixes it, and a ready-to-drop React modal that collects the details AFTER login via the Account API. CALL THIS whenever signup, onboarding, 'Update Account Information', a profile/details form, or 'what users see after they create an account' comes up -- and ALSO proactively once a realm is bootstrapped, because the default is that every new user hits that page.
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | – | App name, e.g. 'Mood Garden'. Used in the modal's copy. |
| componentPath | string | – | Where to WRITE the component, e.g. 'src/components/ProfileOnboarding.tsx'. |
| fields | array | – | Which fields to collect. ASK THE USER FIRST — do not guess. Default ['firstName','lastName']. |
| framework | string | – | Controls the mounting snippet. Default nextjs-app. |
| realm | string | – | Realm, e.g. 'vialproof'. Fills in the commands. |
| tidecloakUrl | string | – | Base URL. Default http://localhost:8080. |
No output schema declared.
No examples provided.
tide_playbook ~160
Read a step-by-step playbook for a specific Tide task
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Playbook name. Available: add-auth-nextjs-existing, add-auth-nextjs-fresh, add-rbac-nextjs, bootstrap-realm-from-template, configure-e2ee-roles-and-policies, deploy-forseti-policy, deploy-tidecloak-d… |
No output schema declared.
No examples provided.
tide_prompt ~62
Read a reusable starter prompt from the pack
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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 |
No output schema declared.
No examples provided.
tide_scenario ~69
Read a scenario summary from reference-apps/<scenario>/scenario.md
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Scenario name. Available: attested-provenance-registry, encrypted-communication, git-pr-signing-service, iga-admin-governance, organisation-password-manager, policy-governed-signing |
No output schema declared.
No examples provided.
tide_scenario_bootstrap ~74
Read a scenario bootstrap sequence from reference-apps/<scenario>/bootstrap-sequence.md
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Scenario name. Available: attested-provenance-registry, encrypted-communication, git-pr-signing-service, iga-admin-governance, organisation-password-manager, policy-governed-signing |
No output schema declared.
No examples provided.
tide_scenario_manifest ~70
Read a scenario manifest from reference-apps/<scenario>/manifest.yaml
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Scenario name. Available: attested-provenance-registry, encrypted-communication, git-pr-signing-service, iga-admin-governance, organisation-password-manager, policy-governed-signing |
No output schema declared.
No examples provided.
tide_scenario_roles ~75
Read a scenario role-policy matrix from reference-apps/<scenario>/role-policy-matrix.md
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Scenario name. Available: attested-provenance-registry, encrypted-communication, git-pr-signing-service, iga-admin-governance, organisation-password-manager, policy-governed-signing |
No output schema declared.
No examples provided.
tide_security_analysis ~128
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tide_skill ~94
Read a composable skill definition
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Skill name. Available: grc-review, 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-scenar… |
No output schema declared.
No examples provided.
What is the Raziel MCP server?
Raziel is an MCP server listed in the public MCP registry as io.github.tide-foundation/raziel. MCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis. This page covers its npm package (@tideorg/mcp).
Is the Raziel MCP server safe to use?
Raziel scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 Raziel MCP server expose?
Raziel exposes 20 tools: tide_list, tide_canon, tide_playbook, tide_skill, tide_prompt, and 15 more. Their descriptions and schemas cost roughly 2,167 tokens of context every time the server is loaded.
Is the Raziel MCP server still maintained?
Raziel is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.