Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
tide-foundation/raziel-mcp
GitHub Stars
2
Server Listing
Raziel (Tide MCP)
ChatGPT
–
Claude
–

TDQS

B3.3/5.0

Scored across 22 tools

Disambiguation3/5

Most tools have distinct roles, but the pack contains many parallel content readers (tide_canon, tide_playbook, tide_prompt, tide_skill, tide_scenario, tide_gaps) whose boundaries are only clear after reading long descriptions. tide_blast_radius and tide_security_analysis also overlap as security-gap analyses of existing apps, and the four tide_scenario_* readers plus tide_list versus tide_list_scenarios can be confused.

Naming Consistency4/5

All names use a consistent snake_case with a tide_ namespace prefix, which makes the set predictable. However, naming mixes verbs with nouns/gerunds (tide_doctor, tide_branding, tide_hosting, tide_blast_radius) rather than following a uniform verb_noun pattern.

Tool Count3/5

At 22 tools, the server is on the heavy side for what is essentially a documentation pack plus a few workflow helpers. Several thin file-reader tools (tide_scenario_manifest, tide_scenario_roles, tide_adapter, tide_gaps) may not each justify a dedicated tool.

Completeness4/5

The surface covers the main Tide lifecycle: discovery, choosing playbooks/scenarios, scaffolding, DPoP assets, auth diagnosis, onboarding, branding, hosting, and security assessment. Minor gaps exist around searching/filtering the pack contents and general realm/app management beyond diagnostics and generated commands.

Available Tools

22 tools
tide_adapterA
Read-only
Inspect

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

Inputs: name (required).

tide_blast_radiusA
Read-only
Inspect

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.

Inputs: part.

tide_brandingA
Read-only
Inspect

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.

Inputs: realm, accent, appName, tidecloakUrl.

tide_canonB
Read-only
Inspect

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

Inputs: name (required), part, section.

tide_choose_playbookC
Read-only
Inspect

Recommend the right playbook for a given situation

Inputs: situation (required).

tide_choose_scenarioA
Read-only
Inspect

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

Inputs: situation (required).

tide_doctorA
Read-only
Inspect

FIND AND FIX WHAT IS WRONG WITH A TIDE APP, IN ONE COMMAND. Returns the command that checks an app for the faults behind most broken logins and unprotected APIs. It REPAIRS the mechanical ones itself (re-copies the DPoP page byte-exact, corrects a wrong rewrite path, gitignores .env) and prints the exact fix for the rest, which YOU apply — do not pass the list to the user. Covers: DPoP page missing/stale/served without its headers, useDPoP passed as a JSX prop (silently OFF), createTideCloakProxy called without protectedRoutes (protects nothing), adapter without its embedded key, remote JWKS, Bearer-only token parsing, no server-side verification, secrets about to be committed, a destructive change request pending. CALL THIS after scaffolding or changing auth code, BEFORE telling the user it works, and FIRST whenever a login or an API check misbehaves. This tool call itself only returns the command.

Inputs: realm, appDir, appUrl, checkOnly.

tide_dpop_assetA
Read-only
Inspect

Returns the exact command that installs 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. @tidecloak/js ships the file from 0.14.34; older SDKs and the TideCloak container do not, and a GitHub search finds 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.

Inputs: no named parameters.

tide_gapsA
Read-only
Inspect

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

Inputs: part.

tide_hostingA
Read-only
Inspect

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.

Inputs: part.

tide_listA
Read-only
Inspect

List all available content in the Tide agent pack by category

Inputs: category (required).

tide_list_scenariosA
Read-only
Inspect

List all available scenario patterns under reference-apps/

Inputs: no named parameters.

tide_onboardingA
Read-only
Inspect

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.

Inputs: realm, fields, appName, framework, +2 more.

tide_playbookB
Read-only
Inspect

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

Inputs: name (required), part.

tide_promptC
Read-only
Inspect

Read a reusable starter prompt from the pack

Inputs: name (required).

tide_scaffoldA
Read-only
Inspect

START A NEW TIDE APP FROM A WORKING TEMPLATE. Returns the exact commands to copy a complete, building app — login, the DPoP page and its wiring, server-side token AND proof verification, and the realm bootstrap script — then install, bootstrap and check it. CALL THIS when building a new app, BEFORE writing any auth code: the code that most often goes wrong (provider config, DPoP, route and API protection) is then copied, not retyped. Pass situation and it picks the template; or name one. Not for adding Tide to an existing app.

Inputs: appDir, appName, template, situation.

tide_scenarioC
Read-only
Inspect

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

Inputs: name (required), part.

tide_scenario_bootstrapB
Read-only
Inspect

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

Inputs: name (required).

tide_scenario_manifestB
Read-only
Inspect

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

Inputs: name (required).

tide_scenario_rolesA
Read-only
Inspect

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

Inputs: name (required).

tide_security_analysisA
Read-only
Inspect

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

Inputs: part, include_runtime_probes.

tide_skillC
Read-only
Inspect

Read a composable skill definition

Inputs: name (required), part, section.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.