Apis Guru
Server Details
APIs.guru MCP — keyless directory of 2,500+ public APIs and their OpenAPI specs.
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-apis-guru
- GitHub Stars
- 0
- Server Listing
- mcp-apis-guru
TDQS
Scored across 35 tools
Many tools overlap heavily: ask_pipeworx, ask_pipeworx_beta (explicitly 'identical'), ask_pipeworx_grounded, deep_research, and validate_claim all answer factual questions, and discover_tools/suggest_questions/search_apis all serve discovery. The extremely detailed descriptions with explicit 'prefer X over Y' guidance partially mitigate this, but an agent still faces real misselection risk.
Names use consistent snake_case throughout and are mostly readable. Minor inconsistency between verb-first names (get_api, list_providers, search_apis) and noun-phrase names (entity_profile, deep_research, polymarket_edges), but the pattern stays predictable enough.
35 tools is heavy and sits above the comfortable 3-15 band. Several could be consolidated (three ask_pipeworx variants, four meta-discovery tools), but the gateway's intentionally broad scope across many data domains makes a large surface somewhat justified.
Coverage is broad and coherent: memory CRUD (remember/recall/forget), subscription lifecycle (subscribe/list/unsubscribe/recent_alerts), entity resolution, comparison, research, verification, and discovery meta-tools. Only minor gaps, e.g. no explicit subscription-update or richer subscription inspection.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread1 field changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +]
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread1 field changed- changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
HUD MCP — U.S. Department of Housing and Urban Development APIs.
Federal Register MCP — US Federal Register API (free, no auth)
One MCP endpoint over 69 public PPN APIs: search_apis to discover, execute_api to call. Free tier.
MCP server for AI access to Swagger by SmartBear.
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP server for searching and discovering 4,000+ public APIs3MIT
- FlicenseBqualityDmaintenanceProvides access to all 471+ DigitalOcean API endpoints through an MCP server that dynamically extracts them from the OpenAPI specification, enabling search, filtering, and direct API calls with proper authentication.61-
- AlicenseNot gradedqualityCmaintenanceMCP server for querying Swagger/OpenAPI metadata efficiently from AI tools, enabling fast API discovery, search, and schema inspection.301 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resources for client-side exploration.116 npm76MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.