InsideOut (Riley)

Name: InsideOut (Riley)
Author: com.luthersystems.insideout

MCP serverMCP

Designs, prices, and deploys AWS/GCP cloud infrastructure from plain-English requirements.

by com.luthersystems.insideoutrepository ↗homepage ↗v0.36.3

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"insideout-riley","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability111/111 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	481 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
12 h ago	mcp initialize	ok	200	563 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
19 h ago	mcp initialize	ok	200	413 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
26 h ago	mcp initialize	ok	200	436 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
33 h ago	mcp initialize	ok	200	432 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
2 d ago	mcp initialize	ok	200	600 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
2 d ago	mcp initialize	ok	200	588 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
2 d ago	mcp initialize	ok	200	483 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
3 d ago	mcp initialize	ok	200	427 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools
3 d ago	mcp initialize	ok	200	464 ms	server insideout-agent v2.0.0 · protocol 2025-06-18 · 24 tools

Tools observed via MCP handshake

awsinspect — INSPECTION: Inspect AWS infrastructure for a deployed project ⚠️ **PREREQUISITE**: This tool requires a prior deployment ATTEMPT (successful or failed). Check c
awsinspect_batch — BATCH INSPECTION: run up to 32 AWS inspect probes in one call. ⚠️ **PREREQUISITE**: Same as awsinspect — deploy attempt required. Check convostatus for hasDeplo
convoawait — Wait for a pending response from Riley after a convoreply timeout. 🎯 USE THIS TOOL WHEN: convoreply returned a timeout error. This allows you to continue wait
convoinspect — INSPECTION: View a session's conversation transcript and metadata Returns the full message history (user / assistant / tool turns) plus the session's meta — wor
convoopen — WORKFLOW: Step 1 of 4 - Start infrastructure design conversation Open an InsideOut V2 session and receive the assistant's intro message. The response contains a
convoreply — WORKFLOW: Step 2 of 4 - Continue infrastructure design conversation Send a user message to the active InsideOut session and receive the assistant reply. The res
convostatus — INSPECTION: View the current infrastructure stack for a session Returns the current state of the user's infrastructure design including: **Components** - Selec
credawait — Wait for the user to securely connect their cloud account and subscribe to Luther Systems. Polls until credentials appear on the session. 🎯 USE THIS TOOL WHEN
gcpinspect — INSPECTION: Inspect GCP infrastructure for a deployed project ⚠️ **PREREQUISITE**: This tool requires a prior deployment ATTEMPT (successful or failed). Check c
gcpinspect_batch — BATCH INSPECTION: run up to 32 GCP inspect probes in one call. ⚠️ **PREREQUISITE**: Same as gcpinspect — deploy attempt required. Check convostatus for hasDeplo
help — Get workflow guidance for using InsideOut infrastructure tools. Call help() for a compact overview, or help(section=...) for a detailed guide. Sections: workflo
stackdiff — Structured diff showing what would be deployed if the user ran tfdeploy now. Returns component-level changes (added/removed/modified), field-level details, and
stackrollback — Create a draft version by reverting to a previous version's config. Copies components, config, and pricing from the target version. If a draft already exists, u
stackversions — List all stack versions for a session (newest first). Shows version history including version number, status (draft/confirmed/applied), change summaries, and ti
submit_feedback — FEEDBACK: Submit feedback, bug reports, or feature requests to Luther Systems Use this tool to forward user feedback directly to the Luther Systems team. This i
tfdeploy — WORKFLOW: Step 4 of 4 - Deploy infrastructure to the cloud Deploy infrastructure by starting a Terraform job for an InsideOut session. This tool initiates the a
tfdestroy — DESTROY: Tear down previously deployed infrastructure Destroys infrastructure by calling the Oracle destroy endpoint for a session that has a prior successful d
tfdrift — DRIFT CHECK: Run a read-only drift detection check Checks whether deployed infrastructure has drifted from the expected Terraform state. This is a read-only ope
tfgenerate — WORKFLOW: Step 3 of 4 - Generate Terraform files from completed design Generate Terraform files from an InsideOut session that has completed infrastructure desi
tflogs — MONITORING: Fetch Terraform deployment logs with pagination Fetches logs from a running or completed Terraform deployment job. For **completed jobs**: uses REST
tfoutputs — INSPECTION: Retrieve Terraform outputs from a completed deployment Returns structured output values (VPC IDs, endpoints, cluster names, etc.) after a successful
tfplan — PREVIEW: Run terraform plan to preview infrastructure changes Runs a terraform plan for an InsideOut session without applying any changes. This lets the user re
tfruns — INSPECTION: List all Terraform deployment runs for a session Returns job IDs, statuses, types (apply/destroy), and timestamps for every run. Use this to see dep
tfstatus — MONITORING: Quick status check for Terraform deployments Check the current status of a Terraform deployment job. Use this tool to quickly check if a deployment

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.luthersystems.insideout/mcp

first seen 2 mo ago · fetched 2 d agoopen ↗

Field history (7 recent events)

2 mo ago · declared · summary → "Designs, prices, and deploys AWS/GCP cloud infrastructure from plain-English requirements."
2 mo ago · declared · description → "Designs, prices, and deploys AWS/GCP cloud infrastructure from plain-English requirements."
2 mo ago · declared · publisherName → "com.luthersystems.insideout"
2 mo ago · declared · homepageUrl → "https://insideout.luthersystems.com"
2 mo ago · declared · repoUrl → "https://github.com/luthersystems/insideout-agent-skills"
2 mo ago · declared · version → "0.36.3"
2 mo ago · declared · protocols → ["mcp"]

InsideOut (Riley)

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from