pickfit

BrowseMCP servers

Infrawise

MCP server that statically analyzes codebase, infra and schemas for AI assistants.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js 22 or later
  • System packages: python3
  1. install infrawise globally via npm

    npm install -g infrawise

Check that it works

infrawise --version; infrawise --help

The output should contain “1.0.0”.

Add it to your agent

claude mcp add infrawise -- infrawise serve --stdio --config '<config>'
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "infrawise": {
      "command": "infrawise",
      "args": [
        "serve",
        "--stdio",
        "--config",
        "<config>"
      ]
    }
  }
}

Replace <config> with your own path.

Add Infrawise as an MCP server in your AI assistant's settings, then ask the assistant for an infrastructure overview to start.

What it does

  • Analyze your code and cloud infrastructure
    Not shown working
  • Find infrastructure and query anti-patterns
    Not shown working
  • Get GSI and index suggestions
    Not shown working
  • Find drift between IaC and deployed resources
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Good for

  • Detect full table scans on DynamoDB tables
  • Suggest missing PostgreSQL indexes
  • Inspect SQS queues for DLQ and encryption issues
  • Check Terraform and CloudFormation drift versus deployed state
  • List API Gateway routes and Lambda integrations

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 1.0.0

An MCP client handshake over stdio listed 22 tools, and a call to get_infra_overview returned a result.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.