Microlink MCP — wraps Microlink API (free tier, no auth required)
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 33 tools
Several tools overlap in practice: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are variants of the same router (beta currently identical), discover_tools and suggest_questions both help agents explore capabilities, and the polymarket family has multiple scanning/research tools. The descriptions are unusually detailed and explicitly cross-reference alternatives, which helps, but an agent can still misselect without careful reading.
All names use snake_case, but the verb/noun ordering is mixed: verb-first names like compare_entities and validate_claim coexist with noun-first/domain-prefixed names like entity_profile, polymarket_arbitrage, and recent_alerts, plus bare verbs like remember and subscribe. It is readable but does not follow a single predictable convention.
33 tools exceeds the 25+ threshold for an overloaded surface, even accounting for the server's broad data/meta-platform scope. The set is heavy enough that tool selection becomes a burden, and several clusters (ask_pipeworx variants, polymarket tools, discovery/meta tools) could be consolidated.
The surface covers a wide range of agent workflows: data research, entity resolution and profiles, comparisons, claim validation, prediction-market research and risk checks, subscriptions, memory, feedback, and web utilities. Minor gaps exist, such as no explicit update operation for saved memories or subscriptions and no standalone raw page-body fetch, but most workflows have a viable path.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_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_research1 field changedInput 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."bet_research1 field 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"
+ }
+]Firecrawl MCP — wraps the Firecrawl API (firecrawl.dev) for web
Crawlbase MCP — wraps the Crawlbase Crawling API (crawlbase.com, formerly
ScrapingBee MCP — wraps the ScrapingBee headless-scraping API (scrapingbee.com)
ScrapingAnt MCP — wraps the ScrapingAnt web scraping API (scrapingant.com)
Add one secure layer between your agents and this server.