Skip to content

Raziel MCP server

io.github.tide-foundation/razieltide-foundationstreamable-httpv1.9.34Scanned

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

22 tools: 7 change things and 15 only read.

Tools: 0 delete, 0 irreversible, 7 write, 15 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • 5 findings, 2 high

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Raziel MCP server can do

The Raziel MCP server is published by the GitHub account tide-foundation. It has 22 tools. It can create or change data (7 tools: tide_choose_scenario, tide_choose_playbook, tide_blast_radius, tide_hosting and 3 more), but cannot delete data. 15 tools only read.

2 tools read private data (tide_canon and tide_adapter); 1 tool brings in text other people can write (tide_dpop_asset).

The fixed checks matched 5 findings, 2 of them high severity (annotation-conflict and sensitive-path). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.9.34.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

22 tools

Changes things 7Claude Code: ask
  • tide_blast_radiusRun 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 ev…1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "tide_blast_radius" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_brandingBRAND THE ENCLAVE FOR THE USER — generate a logo + background and upload them so the Tide login/approval screen is branded.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_choose_playbookRecommend the right playbook for a given situationNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Recommend the right playbook for a given situation

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_choose_scenarioMatch a user request to a known scenario pattern before falling back to generic playbooksNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Match a user request to a known scenario pattern before falling back to generic playbooks

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_hostingWhere TideCloak runs: local Docker vs partner-hosted (Skycloak managed TideCloak-as-a-service).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_onboardingSTOP KEYCLOAK'S 'UPDATE ACCOUNT INFORMATION' PAGE and collect the details in-app instead.1 finding

    Why it is in this group

    • The description's first verb is "stop": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "tide_onboarding" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "stop": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_scaffoldSTART A NEW TIDE APP FROM A WORKING TEMPLATE.1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "tide_scaffold" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
Only reads 15Show 15 read-only tools
  • tide_adapterRead an adapter instruction file (AGENTS, CLAUDE, replit)Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "file": it reads files.
    Description, as the server wrote it
    Read an adapter instruction file (AGENTS, CLAUDE, replit)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_canonRead a canon file (invariants, anti-patterns, concepts, framework-matrix, feature-mapping, troubleshooting, tidecloak-bootstrap, etc.)Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "file": it reads files.
    Description, as the server wrote it
    Read a canon file (invariants, anti-patterns, concepts, framework-matrix, feature-mapping, troubleshooting, tidecloak-bootstrap, etc.)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_doctorFIND AND FIX WHAT IS WRONG WITH A TIDE APP, IN ONE COMMAND.2 findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.

    Findings

    • High

      The description refers to ".env".

      Matched text

      description: "...rrects a wrong rewrite path, gitignores .env) and prints the exact fix for the rest,..."

      What this check looks for
    • High

      The input schema at properties.realm.description refers to ".env".

      Matched text

      inputSchema.properties.realm.description: "...alm checks (needs the admin password in .env)."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_dpop_assetReturns 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 rewrit…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_gapsRead the gap register — what is still uncertain or unresolved in the packNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read the gap register — what is still uncertain or unresolved in the pack

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_listList all available content in the Tide agent pack by categoryNo findings

    Why it is in this group

    • The name "tide_list" says "list": a word for reading.
    Description, as the server wrote it
    List all available content in the Tide agent pack by category

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_list_scenariosList all available scenario patterns under reference-apps/No findings

    Why it is in this group

    • The name "tide_list_scenarios" says "list": a word for reading.
    Description, as the server wrote it
    List all available scenario patterns under reference-apps/

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_playbookRead a step-by-step playbook for a specific Tide taskNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a step-by-step playbook for a specific Tide task

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_promptRead a reusable starter prompt from the packNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a reusable starter prompt from the pack

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_scenarioRead a scenario summary from reference-apps/<scenario>/scenario.mdNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a scenario summary from reference-apps/<scenario>/scenario.md

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_scenario_bootstrapRead a scenario bootstrap sequence from reference-apps/<scenario>/bootstrap-sequence.mdNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a scenario bootstrap sequence from reference-apps/<scenario>/bootstrap-sequence.md

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_scenario_manifestRead a scenario manifest from reference-apps/<scenario>/manifest.yamlNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a scenario manifest from reference-apps/<scenario>/manifest.yaml

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_scenario_rolesRead a scenario role-policy matrix from reference-apps/<scenario>/role-policy-matrix.mdNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a scenario role-policy matrix from reference-apps/<scenario>/role-policy-matrix.md

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_security_analysisAnalyze an EXISTING (possibly non-Tide) system for security gaps and map them to Tide capabilities.No findings

    Why it is in this group

    • The description's first verb is "analyze": a word for reading.
    Description, as the server wrote it
    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'.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • tide_skillRead a composable skill definitionNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a composable skill definition

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.tide.org/mcp: tools/list returned 22 tools to an anonymous client, including tide_choose_scenario (write), tide_choose_playbook (write), tide_blast_radius (write), tide_hosting (write), tide_onboarding (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 high3 warn
  • The description refers to ".env".

    Matched text

    description: "...rrects a wrong rewrite path, gitignores .env) and prints the exact fix for the rest,..."

    What this check looks for
  • The input schema at properties.realm.description refers to ".env".

    Matched text

    inputSchema.properties.realm.description: "...alm checks (needs the admin password in .env)."

    What this check looks for
  • The server marks "tide_blast_radius" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "tide_onboarding" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "stop": a word for a change.

    What this check looks for
  • The server marks "tide_scaffold" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The description's first verb is "start": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools20 changed.~20 changedView diff

Install

Pinned to version 1.9.34. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__raziel__tide_list",
      "mcp__raziel__tide_canon",
      "mcp__raziel__tide_playbook",
      "mcp__raziel__tide_skill",
      "mcp__raziel__tide_prompt",
      "mcp__raziel__tide_adapter",
      "mcp__raziel__tide_list_scenarios",
      "mcp__raziel__tide_scenario",
      "mcp__raziel__tide_scenario_manifest",
      "mcp__raziel__tide_scenario_roles",
      "mcp__raziel__tide_scenario_bootstrap",
      "mcp__raziel__tide_security_analysis",
      "mcp__raziel__tide_dpop_asset",
      "mcp__raziel__tide_doctor",
      "mcp__raziel__tide_gaps"
    ],
    "ask": [
      "mcp__raziel__tide_choose_scenario",
      "mcp__raziel__tide_choose_playbook",
      "mcp__raziel__tide_blast_radius",
      "mcp__raziel__tide_hosting",
      "mcp__raziel__tide_onboarding",
      "mcp__raziel__tide_branding",
      "mcp__raziel__tide_scaffold"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as raziel. Review it before you use it.

Capability tags behind 3 rules
  • mcp__raziel__tide_canon private-data
  • mcp__raziel__tide_adapter private-data
  • mcp__raziel__tide_dpop_asset untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.tide-foundation/raziel/verify?hash=95d52e6ba04324944e32a8bdd2d6c7f6a9577a26476af2acc571abfafa7b1555" | jq -e '.changed == false'

Pinned hash 95d52e6ba043, from Nov 10, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.tide-foundation/raziel/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.tide-foundation/raziel
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.tide-foundation/raziel.svg)](https://radar.anlyon.com/servers/io.github.tide-foundation/raziel)

Source: MCP Registry · repository. Synced Oct 29, 2026, 09:17 UTC.

Raziel MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Raziel MCP server safe?

No scan can promise that. What its definitions show: 22 tools, 7 of which can change, send or delete something, and 5 findings (2 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Raziel MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Raziel MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Raziel MCP server have?

22 tools: 7 write, 15 read. tide_choose_scenario, tide_choose_playbook, tide_blast_radius, tide_hosting, tide_onboarding, tide_branding, tide_scaffold, tide_list and 14 more.

Does the Raziel MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Raziel MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Raziel MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.