Skip to main content
Glama

Homebrew Formulae

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Homebrew formulae.brew.sh MCP.

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
Uptime
0.0% over 49 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-homebrew-formulae
GitHub Stars
0
Server Listing
mcp-homebrew-formulae

TDQS

C2.9/5.0

Scored across 19 tools

Disambiguation2/5

The tool set mixes Homebrew-related tools (5) with a large set of unrelated Pipeworx data analysis tools (14), creating two distinct domains that are hard to distinguish. Within the Pipeworx group, tools like compare_entities, entity_profile, and validate_claim overlap in purpose, causing ambiguity.

Naming Consistency3/5

All tool names use snake_case, which is consistent in style. However, the naming pattern is not predictable: some combine a verb and noun (e.g., resolve_entity), while others are noun-centric (entity_profile) or verb-only (forget). The lack of a uniform verb_noun pattern reduces predictability.

Tool Count2/5

At 19 tools, the count is high for a server named after a niche domain (Homebrew Formulae). Only 5 tools relate to Homebrew, while the remaining 14 serve a completely different purpose, making the server feel bloated and unfocused.

Completeness2/5

For the Homebrew domain, the tools only provide analytics and lookups, missing common operations like searching or updating. For the Pipeworx domain, there are gaps such as no tool for placing bets or managing SEC filings directly. The server tries to cover too many areas without full coverage in any.

Tool Schema Changelog

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

  1. 19 tool updates
    • First observedanalytics_cask_install
    • First observedanalytics_install
    • First observedask_pipeworx
    • First observedbet_research
    • First observedcask
    • First observedcompare_entities
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedformula
    • First observedpipeworx_feedback
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edges
    • First observedrecall
    • First observedrecent_changes
    • First observedrecent_formulae
    • First observedremember
    • First observedresolve_entity
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources