Homebrew Formulae
Server Details
Homebrew formulae + casks + install analytics (formulae.brew.sh)
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-homebrew-formulae
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.9/5 across 19 of 19 tools scored. Lowest: 1.8/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.
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.
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.
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!