Skip to main content
Glama

Server Details

pub.dev MCP — package registry for Dart & Flutter.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-pub-dev
GitHub Stars
0
Server Listing
mcp-pub-dev

TDQS

A3.9/5.0

Scored across 35 tools

Disambiguation3/5

Most tools target clearly distinct resources (pub.dev packages, Polymarket arb, memory, subscriptions, entity resolution), so boundaries are largely readable. However the ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research cluster overlaps heavily, and the beta tool is explicitly documented as identical to ask_pipeworx today, which invites misselection. Descriptions do a lot of work to steer callers, keeping it at a middling score.

Naming Consistency4/5

All 35 names are consistently snake_case with no camelCase or style mixing, and verb_noun patterns (get_package, resolve_entity, list_versions) dominate. The main deviation is heavy use of domain prefixes (polymarket_, ask_pipeworx_, pipeworx_), which is predictable grouping rather than chaos. Minor inconsistency in whether the noun or verb leads, but overall readable and consistent.

Tool Count2/5

35 tools is well into 'too many' territory, and the surface is wildly mismatched to the server's apparent name (Pub Dev) — only four tools touch pub.dev while 31 form a broad data gateway. Even granting the gateway a legitimately wide scope, the overlapping ask_pipeworx family shows the count is not tightly scoped. Many tools earn their place individually, but the set is oversized for any single stated purpose.

Completeness4/5

Lifecycle coverage is strong where it matters: memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list_subscriptions/recent_alerts), and entity resolution are complete, and the polymarket suite covers edges, arbitrage, fill risk, cross-venue, and decay. The pub.dev slice is thinner (no README/docs or dependency-detail fetch beyond scan_dependency), and there are no glaring dead ends for the gateway's core workflows.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
        -  "company"
        -]New value: +[
        +  "company",
        +  "ticker"
        +]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.