Shadow Warden AI — Gateway v7.10 — Explore the API Reference
◧

Shadow Warden AI MCP Server

Call the security gateway as tools from Claude, ChatGPT or any Model Context Protocol client. One endpoint, Streamable HTTP, JSON-RPC 2.0.

streamable-httpJSON-RPC 2.02025-06-182025-03-262024-11-05

Connect

Endpoint POST only — this server has no GET stream
https://api.shadow-warden-ai.com/mcp/
Claude Code / Claude Desktop mcp config
{
  "mcpServers": {
    "shadow-warden": {
      "type": "http",
      "url": "https://api.shadow-warden-ai.com/mcp/",
      "headers": { "X-API-Key": "$WARDEN_API_KEY" }
    }
  }
}

The manifest lives at /.well-known/mcp.json — endpoint, transport, supported protocol revisions, auth schemes and the full tool list, generated from the server rather than written by hand.

Free tools — the security gateway

No nanopayment, no registration. filter_text goes through POST /filter exactly like a REST call, so it consumes your own request quota and is rate-limited the same way — billing it again per MCP call would charge twice for one request.

Tool
filter_text
Screen text through the nine-stage pipeline — prompt injection, obfuscation decoding, secret and PII redaction. Runs against your own gateway quota, so it needs your API key.
gateway_health
Liveness, version and pipeline readiness. Use it before you route traffic through the gateway.
list_pricing
Plans, request allowances and prices, read from the same table the checkout charges from.

Paid tools — business operations

Twelve staff tools, $0.001–$0.10 per call, settled with Flex Credits, x402 USDC or L402 Lightning. Prices are published at /mcp/pricing. An unfunded call returns JSON-RPC error -32099 with HTTP 402 and the instructions to fund.

screen_sanctions_listscore_kyc_profilegenerate_sarfetch_market_signalsgenerate_seo_contentadjust_ad_budgetcrm_searchcrm_upsert_leadsend_email_draftschedule_meeting_slotget_ticketresolve_ticket_kb

Try it without a client

curl
curl -sS https://api.shadow-warden-ai.com/mcp/ \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

What this server does not implement

  • Protocol revision 2026-07-28. It replaced the initialize handshake with per-request _meta negotiation and a mandatory server/discover RPC. Neither is implemented here, so 2026-07-28 is deliberately absent from the advertised list rather than claimed and then failed.
  • No GET stream. A GET that asks for text/event-stream answers 405 with Allow: POST.
  • No sessions and no resumability. Mcp-Session-Id and Last-Event-ID are ignored.
  • No resources or prompts. Tools only — capabilities says so.