always-seven MCP — wraps StupidAPIs (keyless — no credential needed)
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.
Scored across 37 tools
The set is heavily overlapping around Polymarket/Kalshi market analysis (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, release_calendar_markets, resolution_audit/resolution_diff) and around Pipeworx universal-query routing (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research). Several boundaries are thin: ask_pipeworx_beta explicitly mirrors ask_pipeworx, and the polymarket tools all target 'find and size an edge' from slightly different angles. Other tools are distinct, but a handful of near-synonyms create real misselection risk.
Most tools use snake_case with family prefixes (polymarket_, ask_pipeworx, resolution_, entity_profile/compare_entities), but the conventions are mixed: camelCase in ai_visibility_check, bare verbs in forget/recall/remember/subscribe/unsubscribe, and non-parallel names like generate_llms_txt, search_within, scan_competitor_ai_presence, scan_dependency, suggest_questions, always_seven_generate. There is no single predictable pattern a caller could rely on.
37 tools is a heavy but defensible count for the scope: a general-purpose structured-data router plus entity research, prediction markets, subscriptions, memory, and utilities. The count is just above the 'too many' threshold but most tools earn their place. A tighter server could merge ask_pipeworx_beta into ask_pipeworx and reduce the four-plus Polymarket edge scanners, so it sits on the high edge of reasonable.
The domain is broad but well-covered: data lookup, grounded verification, entity research, company facts, market analysis, resolution audits, claim verification, subscriptions, and memory. Missing pieces are minor (no general-purpose web search besides news feeds, no direct market-order submission, subscriptions require an account) and the tool surfaces support the main user journeys end to end, including caveats and fallback paths.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
company_factskalshi_weather_edgerelease_calendar_marketsresolution_auditresolution_diffbet_research2 fields changedInput 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"
+ }
+]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."bet_research2 fields changedInput 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"
+ }
+]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."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]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."buzzword-density MCP — wraps StupidAPIs (keyless — no credential needed)
ship-on-friday MCP — wraps StupidAPIs (keyless — no credential needed)
victorian-complaint MCP — wraps StupidAPIs (keyless — no credential needed)
excuse MCP — wraps StupidAPIs (keyless — no credential needed)
Add one secure layer between your agents and this server.