Home / MCP registry index / io.github.tide-foundation/raziel
Raziel
io.github.tide-foundation/raziel in the official MCP registry.
Endpoint https://mcp.tide.org/mcp. Source: github.com/tide-foundation/raziel-mcp.
The registry describes it as: MCP server teaching AI agents to implement TideCloak: auth, E2EE, IGA, security analysis
We read its 22 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
tide_list tide_canon tide_playbook tide_skill tide_prompt tide_adapter tide_list_scenarios tide_scenario tide_scenario_manifest tide_scenario_roles tide_scenario_bootstrap tide_choose_scenario tide_choose_playbook tide_security_analysis tide_blast_radius tide_hosting tide_dpop_asset tide_onboarding tide_branding tide_scaffold tide_doctor tide_gaps
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-tide-foundation-raziel)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.