Should my agent depend on the MCP server io.github.tide-foundation/raziel?

Verdict: allow — mid-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Raziel

io.github.tide-foundation/raziel

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

— the operator's own registry description reported

Publisher io.github.tide-foundation · first seen 2026-08-12 · endpoint https://mcp.tide.org/mcp

allow

verdict

mid-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-slow-solo — safe to depend on

Cluster mid-slow-solo · distinctiveness 0.381 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency644 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools18

vs populationmid

capabilities2

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_4895788bd89e0033e5d8ed64 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

tide_adapter tide_blast_radius tide_branding tide_canon tide_choose_playbook tide_choose_scenario tide_gaps tide_hosting tide_list tide_list_scenarios tide_playbook tide_prompt tide_scenario tide_scenario_bootstrap tide_scenario_manifest tide_scenario_roles tide_security_analysis tide_skill

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	18/18	✓
has a description	18/18	✓
description is substantive	17/18	17/18
parameters are typed	18/18	✓
parameters are described	18/18	✓

18 of 18 tools graded · 18 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.9.11

server version @tideorg/mcp

Capabilities: prompts tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-08-14	inventory	tools 17 → 18
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:16Z	ok_tools	200	644	2025-06-18
2026-08-12T05:35:28Z	ok_tools	200	683	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.tide-foundation/raziel.svg)](https://robinsaige.com/s/io.github.tide-foundation/raziel)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview