Mercury Number
Server Details
mercury-number MCP — wraps StupidAPIs (keyless — no credential needed)
The last two health checks of this connector failed. 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 the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-mercury-number
- GitHub Stars
- 0
- Server Listing
- mercury-number
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 45 tools
Most families are clearly separated (archive_*, resolution_*, polymarket_*, memory trio), but the core routing layer is genuinely ambiguous: ask_pipeworx, ask_pipeworx_beta (whose own description admits it 'currently matches ask_pipeworx exactly'), ask_pipeworx_grounded, deep_research and discover_tools all compete for the same 'answer a data question' call. The prediction-market cluster is similarly crowded — polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker and kalshi_weather_edge all overlap around 'find/validate a bet', and only very long descriptions differentiate them.
Everything is snake_case, which is good, and there are useful prefixes (polymarket_*, updown_*, ask_pipeworx_*). But the verb/noun ordering is inconsistent — resolve_entity, compare_entities, discover_tools, validate_claim sit alongside entity_profile, company_facts, archive_compare, ai_visibility_check, mercury_number_generate — so there is no single predictable pattern to guess a name from.
45 tools is heavy for any single server, and it is wildly disproportionate to the advertised purpose ('Mercury Number', which is served by exactly one tool). Several entries are meta/duplicative (ask_pipeworx_beta, pipeworx_feedback, pipeworx_trending, suggest_questions, discover_tools) and inflate the surface beyond what the domain needs.
The data-gateway surface is broad — entity resolution, financials, registers, memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/recent_alerts), and a deep prediction-market stack all have full lifecycles. However the set is incoherent with its stated identity (astrology number generation) and has real dead ends: research_row and classify_row reference 'fetch_url' which is not in this tool list, and there is no general web-fetch/browse tool despite many tools depending on page retrieval.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
phoenix-number MCP — wraps StupidAPIs (keyless — no credential needed)
iss-number MCP — wraps StupidAPIs (keyless — no credential needed)
yesterdays-number MCP — wraps StupidAPIs (keyless — no credential needed)
buzzword-density MCP — wraps StupidAPIs (keyless — no credential needed)
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceHoroscope MCP — wraps the keyless Horoscope App API.263 npmMIT

Ready APIsofficial
AlicenseNot gradedqualityDmaintenanceMCP tools for geo, email, phone, company, DNS, FX, equities, weather, tax, economics, and intelligence — streamable HTTP, one API key.MIT- AlicenseAqualityBmaintenanceThe most comprehensive everyday calculator MCP server — 501 tools across 22 categories covering 8 countries' tax systems (FR, BE, CH, CA, US, UK, MA, SN). Finance, health, math, science, construction, conversions, education, sport, cooking, travel, and more. Free, no API key required. Streamable HTTP transport.1520 npm1MIT
- AlicenseAqualityBmaintenancePrecision-audited astrology MCP for natal charts, transits, synastry and moon phases. No API key.1089 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.