Ext Ops Panel
Open dashboard
Comparison

MCP Surface Lint vs io.github.arose26/make-audit-mcp

MCP Surface Lint is an MCP server published by DLeibner. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.arose26/make-audit-mcp is an MCP server published by arose26. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceMCP Surface Lintio.github.arose26/make-audit-mcp
Official MCP Registry Listed
Version: 0.4.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 310
Downloads/week (npm): 194
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

MCP Surface Lint vs io.github.arose26/make-audit-mcp
FactMCP Surface Lintio.github.arose26/make-audit-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcplint-web.vercel.app/api/mcp)On your machine (make-audit-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/dleibner/mcp-surface-lintgithub.com/arose26/make-audit-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-25no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

MCP Surface Lint

In its own words, on Official MCP Registry:

Statically audits MCP tool surfaces for token cost, schema quality, and design issues.

io.github.arose26/make-audit-mcp

In its own words, on Official MCP Registry:

Audit Make.com blueprints before importing: hardcoded secrets, dangling refs, risky settings.

How to run each

MCP Surface Lint As a remote MCP server

Claude Code
claude mcp add --transport http mcp-surface-lint https://mcplint-web.vercel.app/api/mcp

io.github.arose26/make-audit-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio make-audit-mcp -- npx -y make-audit-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only MCP Surface Lint has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: MCP Surface Lint · What it can do: io.github.arose26/make-audit-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built