@tideorg/mcp

MCPcommunitylive
v1.9.23io.github.tide-foundationUnknownUpdated 1mo agonpmGitHub

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

Endpoint healthlive
checked 4 days ago · 1035ms
100% of the last 4 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.tide-foundation
LicenseUnknown
Version1.9.23
Sourcenpm+mcp-registry
npm@tideorg/mcp
GitHubtide-foundation/raziel-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface18 tools · 1 privileged
Security scan✓ Cleanv1.9.11 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 16, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

18 tools · 1 privileged
Statically extracted from the published packagev1.9.11 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

tide_listNo description published

This tool published no description. Forge does not invent one.

tide_canonNo description published

This tool published no description. Forge does not invent one.

tide_playbookNo description published

This tool published no description. Forge does not invent one.

tide_skillprivilegedNo description published

This tool published no description. Forge does not invent one.

tide_promptNo description published

This tool published no description. Forge does not invent one.

tide_adapterNo description published

This tool published no description. Forge does not invent one.

tide_list_scenariosNo description published

This tool published no description. Forge does not invent one.

tide_scenarioNo description published

This tool published no description. Forge does not invent one.

tide_scenario_manifestNo description published

This tool published no description. Forge does not invent one.

tide_scenario_rolesNo description published

This tool published no description. Forge does not invent one.

tide_scenario_bootstrapNo description published

This tool published no description. Forge does not invent one.

tide_choose_scenarioNo description published

This tool published no description. Forge does not invent one.

tide_choose_playbookNo description published

This tool published no description. Forge does not invent one.

tide_security_analysisNo description published

This tool published no description. Forge does not invent one.

tide_blast_radiusNo description published

This tool published no description. Forge does not invent one.

tide_hostingNo description published

This tool published no description. Forge does not invent one.

tide_brandingNo description published

This tool published no description. Forge does not invent one.

tide_gapsNo description published

This tool published no description. Forge does not invent one.

0 of 18 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

18 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.