Skip to content

InfraScan Cloud MCP server

io.github.SolDevelo/infrascan-cloudSolDevelostreamable-httpv1.0.2Scanned

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

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 4
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the InfraScan Cloud MCP server can do

The InfraScan Cloud MCP server is published by the GitHub account SolDevelo. It has 4 tools. It can create or change data (1 tool: list_targets), but cannot delete data. 3 tools only read.

4 tools read private data (list_targets, list_findings, get_finding and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 1Claude Code: ask
  • list_targetsStart 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, poten…Reads private data1 finding

    Why it is in this group

    • The name "list_targets" says "list": a word for reading.
    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.

    Findings

    • Warn

      The server marks "list_targets" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_targets" says "list": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List AWS accounts and repositories
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_findingOne 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 CL…Reads private dataNo findings

    Why it is in this group

    • The name "get_finding" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a finding and its fix
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_scan_summaryOne 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, potent…Reads private dataNo findings

    Why it is in this group

    • The name "get_scan_summary" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Get the latest scan's summary
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_findingsFindings from the latest completed scan of every AWS account and repository (or of one target), most severe first, then by monthly savings.Reads private dataNo findings

    Why it is in this group

    • The name "list_findings" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: List findings
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:19 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "list_targets" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_targets" says "list": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http infrascan-cloud https://infrascan.soldevelo.com/cloud/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http infrascan-cloud https://infrascan.soldevelo.com/cloud/api/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__infrascan-cloud__list_findings",
      "mcp__infrascan-cloud__get_finding",
      "mcp__infrascan-cloud__get_scan_summary"
    ],
    "ask": [
      "mcp__infrascan-cloud__list_targets"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as infrascan-cloud. Review it before you use it.

Capability tags behind 4 rules
  • mcp__infrascan-cloud__list_targets private-data
  • mcp__infrascan-cloud__list_findings private-data
  • mcp__infrascan-cloud__get_finding private-data
  • mcp__infrascan-cloud__get_scan_summary private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.SolDevelo/infrascan-cloud/verify?hash=a30d8a9bffca470d79878d7b5c517867a79d1b1d2f239270a5b07b89db72c7a4" | jq -e '.changed == false'

Pinned hash a30d8a9bffca, from Nov 20, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.SolDevelo/infrascan-cloud/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.SolDevelo/infrascan-cloud
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.SolDevelo/infrascan-cloud.svg)](https://radar.anlyon.com/servers/io.github.SolDevelo/infrascan-cloud)

Source: MCP Registry. Synced Nov 20, 2026, 19:17 UTC.

InfraScan Cloud MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the InfraScan Cloud MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the InfraScan Cloud MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the InfraScan Cloud MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the InfraScan Cloud MCP server have?

4 tools: 1 write, 3 read. list_targets, list_findings, get_finding and get_scan_summary.

Does the InfraScan Cloud MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the InfraScan Cloud MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the InfraScan Cloud MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.