Open Collective public collective/transaction data
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 35 tools
The Pipeworx meta-router tools heavily overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all offer entry-point search/lookup behavior, and the descriptions spend most of their length disambiguating themselves. The Polymarket family (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) is better separated but still crowded, and ai_visibility_check vs scan_competitor_ai_presence overlap. An agent will frequently misselect between the ask_pipeworx variants and the research tools.
Most names are snake_case verb_noun (resolve_entity, validate_claim, recent_changes, scan_dependency), but the set also contains bare nouns (collective, events, members, transactions) and bare verbs (remember, recall, forget, subscribe, unsubscribe), plus variant suffixes (_beta, _grounded) that read as siblings. It is readable but the pattern is mixed rather than predictable.
35 tools is heavy for a single server, and the surface is dominated by a generic Pipeworx gateway toolkit rather than a focused domain. Only about four tools (collective, events, members, transactions) relate to the OpenCollective name, so most tools do not earn their place for the stated scope.
For the OpenCollective domain the surface is read-only (collective, events, members, transactions) with no create/update/delete or search operations, a notable gap if write workflows are intended. The Pipeworx side is richer, but the two domains are mismatched enough that coverage of the apparent server purpose is partial.
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_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."OpenFEC MCP — Federal Election Commission campaign finance data
OpenCorporates MCP — Global company registry data (free, no auth, rate limited)
US government + SEC data as clean JSON: SAM.gov, USAspending, Grants.gov, Congress, SEC filings.
Read-only U.S. healthcare dataset metadata, schemas, immutable downloads, and checksums.
Add one secure layer between your agents and this server.
