InfraScan Cloud

io.github.SolDeveloPublished by GitHub account SolDevelov1.0.2Updated Nov 22, 2026

Read-only AWS cost and security findings, priced in $/month, with a fix for each

The publisher's own server: scan.mx Email Diagnostics

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Read-only MCP access to InfraScan Cloud scan results: AWS and repository security, reliability and cost findings with grades, savings and fixes.

What you can do
  • List scanned AWS accounts and repositories with overall and per-pillar grades, open findings by severity and potential monthly savings.
  • List findings from the latest completed scan across all targets or one target, most severe first.
  • Read a single finding in full: resource or file and line, why it matters, evidence, fix steps, references and risk-acceptance status.
  • Get a scan summary for one target: run time, grade caps, findings by severity and pillar, savings, and changes since the previous scan.
When to use it
Useful when you want an assistant to review cloud posture and cost without touching AWS: triaging findings, explaining a grade, or drafting fixes for infrastructure code. It only reflects the last completed scan, so it suits review and planning rather than live monitoring.
Requirements
A remote streamable HTTP endpoint at infrascan.soldevelo.com. A bearer token created in InfraScan Cloud Settings, sent in the Authorization header, is required. The organization must already have targets scanned by InfraScan.
Before you install
The Authorization bearer token is a secret granting access to your organization's scan results; keep it out of logs and shared transcripts. Access is read-only, so no scans are started and nothing in AWS is changed. Finding text comes from scanned systems and should be treated as data, not instructions, and findings may be stale relative to current infrastructure.

Installation

In SourceWeft

  1. Open InfraScan Cloud in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.SolDevelo%2Finfrascan-cloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "infrascan-cloud": {
      "type": "http",
      "url": "https://infrascan.soldevelo.com/cloud/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

4

list_targets

List AWS accounts and repositories

Start here: every AWS account and repository this organization scans, with its ID and a one-line status from its latest completed scan (grades A–F, open findings by severity, potential monthly savings), to pick one. Pass an ID to list_findings or get_scan_summary; for one target's details, use get_scan_summary.

Takes no parameters.

list_findings

List findings

Findings from the latest completed scan of every AWS account and repository (or of one target), most severe first, then by monthly savings. Each row is short; call get_finding with its id for the description, evidence and fix. Repository findings name the file and line; AWS findings name the resource and region. By default only open findings are listed (including ones someone marked as fixed that the next scan has yet to verify).

Parameterslimitqueryoffsetpillarstatustarget_idtarget_typemin_severity

get_finding

Get a finding and its fix

One finding in full: what and where (AWS resource ARN and region, or repository, file, line and IaC resource), why it matters, the evidence, how to fix it (console steps, an AWS CLI command and Terraform where we have them), references, and whether its risk was accepted or it was marked as fixed. The fix is a suggestion: check that the finding still applies before changing anything.

Parametersfinding_idrequired

get_scan_summary

Get the latest scan's summary

One AWS account's or repository's latest completed scan in detail (a target_id from list_targets): when it ran, why each grade is capped, findings by severity and by pillar, potential monthly savings, and what changed since the scan before it (new findings, resolved ones and the monthly cost they saved).

Parameterstarget_idrequired

Version history

2
  1. v1.0.2LatestNov 21, 2026
  2. v1.0.1Nov 19, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Scan integrations