Designs, prices, and deploys AWS/GCP cloud infrastructure from plain-English requirements.
Cloud & Infrav0.36.3streamable-httpapp.luthersystems.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 496ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo insideout-agent@v2.0.0 |
| tooling | 35 / 35 | tools/list OK: 24 tools e.g. "awsinspect"; 24/24 described, 24/24 fully-typed schemas, median description 1196 chars |
| latency | 10 / 10 | initialize round-trip 496ms |
| provenance | 8 / 15 | description present; repository linked; version 0.36.3; namespace com.luthersystems.insideout does NOT match remote host (expected *.insideout.luthersystems.com) |
Score 93/100 · latency 496ms · 24 tools · auth: open
Claude Code:
claude mcp add --transport http mcp https://app.luthersystems.com/v1/insideout-mcp
Generic MCP client config:
{ "mcpServers": { "mcp": { "type": "http", "url": "https://app.luthersystems.com/v1/insideout-mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/com.luthersystems.insideout/mcp · referral link https://mcpqueen.com/go/com.luthersystems.insideout/mcp (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.luthersystems.insideout/mcp)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 03:45 | A | 93 | 496ms |