Skip to main content
Glama

Server Details

DataSF MCP — San Francisco open data (data.sfgov.org, Socrata SODA API).

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-data-sf
GitHub Stars
0
Server Listing
DataSF MCP

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

The set spans many distinct domains, but the research/meta-tool layer is crowded: ask_pipeworx, ask_pipeworx_beta (currently an exact duplicate of ask_pipeworx), ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions, validate_claim, compare_entities, entity_profile, and recent_changes all compete for 'ask a data question' workflows. Descriptions explicitly guide selection, which helps, but the beta duplicate and multiple overlapping Polymarket opportunity finders leave real room for misselection.

Naming Consistency4/5

Names are consistently snake_case and mostly action-oriented or clear noun phrases, with sensible prefixes like polymarket_, sf_, and ask_pipeworx. Minor deviations exist: bare verbs (remember, recall, forget, subscribe, unsubscribe) and noun phrases (entity_profile, recent_alerts) mix with verb_noun patterns, but the style remains readable and predictable.

Tool Count2/5

34 tools is heavy for an MCP server surface, even one covering multiple domains. While breadth is intentional, the count includes niche/advanced tools and several overlapping research entry points, increasing agent load and selection risk; consolidation or clearer namespacing would help.

Completeness4/5

The surface is broad and covers discovery, structured lookup, grounding, entity resolution, comparison, recent changes, memory, subscriptions, feedback, and domain-specific areas (SF open data, Polymarket, AI visibility). Minor gaps remain, such as no direct tool to fetch a record by pipeworx:// citation URI and limited schema introspection for SF datasets, but overall coverage is strong for a data-gateway server.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous 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": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous 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 (\"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."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous 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

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.