Adopter quickstart

MCP proof path

Public waitlist preview for adopting Imladri with MCP: initialize the adapter, wrap one risky capability, run the local scanner, and review the proof artifacts before a private design-partner workspace is opened.

Join waitlist View pilot packet Read integration docs

Certification status

Certified

Certified stdio MCP server with JSON-RPC tools/list, proof verification, and Claude Desktop/Cursor/Windsurf config artifacts.

4 MCP lanes passed; hosted remote HTTP MCP is an optional additional proof lane when configured.

Runtimemcp

Public modeWaitlist preview

One-command starter

imladri init --mcp --ci-provider github

Install

npm install
node mcp-server/server.mjs

Minimal wrapper

IMLADRI_AGENT_ID=<pilot-agent-id>
IMLADRI_AUTHORITY_TOKEN=<short-lived-pilot-token>
IMLADRI_WORKER_URL=https://<worker>
node mcp-server/server.mjs

Local proof artifacts

node scripts/certify-mcp-clients.mjs --output logs/mcp-client-proof.json --profile-output logs/mcp-client-profile-certification.json --config-dir logs/mcp-client-configs
imladri agent init --runtime mcp --skip-connect
imladri agent verify --samples 100 --concurrency 100

CI scanner

imladri scan init-ci --provider github --output .github/workflows/imladri-scan.yml

CI scanning is optional for MCP host repos. The MCP proof itself is the stdio JSON-RPC lane plus Claude Desktop, Cursor, and Windsurf config artifacts.

What this proves

Boundary wrapped

MCP strict tools route through Imladri preflight before the tool body runs.

Evidence generated

The local scan and SDK certification commands create artifacts for design-partner review.

No account required

This public preview uses local artifacts. Private proof workspaces open only during design-partner onboarding.

Pilot notes

Use short-lived Profile-issued MCP authority tokens for private pilots; do not reuse long-lived SDK keys in MCP hosts.

← Back to all adopters