Ext Ops Panel
Open dashboard
Comparison

ast-grep vs Indiana Code

ast-grep is an MCP server published by dgageot. Marketplaces we read that list it: 1 (Docker MCP Catalog). Indiana Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplaceast-grepIndiana Code
Docker MCP Catalog Listed
Version: sha256:5fc3f2e9dcf2
Forks (GitHub): 0
Pulls (Docker Hub): 101 232
Stars (Docker Hub): 2
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
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

ast-grep vs Indiana Code
Factast-grepIndiana Code
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)0 (worse)
Pulls (Docker Hub) (differs)101 232No figure on Docker Hub
Forks (GitHub)00
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (mcp/ast-grep)Remote server (gateway.pipeworx.io/indiana-code/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/dgageot/mcp-ast-grepgithub.com/pipeworx-io/mcp-indiana-code
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 45 h ago

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

ast-grep

In its own words, on Docker MCP Catalog:

ast-grep is a fast and polyglot tool for code structural search, lint, rewriting at large scale.

Indiana Code

In its own words, on Official MCP Registry:

Indiana Code — state statutes by citation, plus topic search and historical (per-year) versions.…

How to run each

ast-grep As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio ast-grep -- docker run -i --rm mcp/ast-grep

Indiana Code As a remote MCP server

Claude Code
claude mcp add --transport http indiana-code https://gateway.pipeworx.io/indiana-code/mcp

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

Only Indiana Code has a remote endpoint we check. How we check endpoints

Tools each declares

Only ast-grep has

  • ast-grep

Only Indiana Code has

  • ai_visibility_check
  • archive_compare
  • archive_evidence
  • ask_pipeworx
  • ask_pipeworx_beta
  • ask_pipeworx_grounded
  • bet_research
  • classify_row
  • company_facts
  • company_register_search
  • compare_entities
  • deep_research
Show the remaining 31
  • discover_tools
  • entity_profile
  • forget
  • generate_llms_txt
  • in_code_search
  • in_code_section
  • kalshi_weather_edge
  • list_subscriptions
  • pipeworx_feedback
  • pipeworx_trending
  • polymarket_arbitrage
  • polymarket_edge_tracker
  • polymarket_edges
  • polymarket_fill_risk
  • polymarket_kalshi_spread
  • recall
  • recent_alerts
  • recent_changes
  • release_calendar_markets
  • remember
  • research_row
  • resolution_audit
  • resolution_diff
  • resolve_entity
  • scan_competitor_ai_presence
  • scan_dependency
  • search_within
  • subscribe
  • suggest_questions
  • unsubscribe
  • validate_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Indiana Code as of 2026-10-15). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

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

What it can do: ast-grep · What it can do: Indiana Code · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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