Is the StackData MCP server down?

mcp-registry/io.stackdata/stackdata · registry v0.1.0 · server reports v0.1

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 12:33 UTC · handshake 19ms

As of 2026-11-22 12:33 UTC, the StackData MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
6,883
outages (90d)
7
tools
6

Official statistics, China censuses & yearbooks, and as-of customs tariffs with legal citations.

Point your MCP client at this streamable-http endpoint: https://api.stackdata.io/mcp

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 2 warning(s) across 6 tool(s); ~1,222 tokens of tool definitions.
Scores higher than 20% of 27,585 MCP servers Glimind has audited.
Its tool list costs an agent ~1,222 tokens per session — lighter than 65% of servers.
77 → 78 since 2026-10-17
no tool-poisoning patterns
Descriptions67
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (3)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_series, get_structure, get_table, resolve_data, search_datasets and 1 more

3 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: search_datasets, tariff_lookup

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.stackdata%2Fstackdata/fixes

get_series 1 change
{
  "name": "get_series",
  "description": "Fetch ONE series with every dimension named by you (no guessing or relaxing): dataset, ISO3 countries, an ISO period range and a member code for every dimension from get_structure. Returns status ok/empty/refused with each value's provenance, and the missing country-periods listed. A bad request is a named 400 error saying which field and what is allowed.",
  "inputSchema": {
    "type": "object",
    "required": [
      "dataset",
      "countries",
      "period",
      "select"
    ],
    "properties": {
      "period": {
        "type": "object",
        "required": [
          "start",
          "end"
        ],
        "properties": {
          "end": {
            "type": "string",
            "pattern": "^\\d{4}(-Q[1-4]|-(0[1-9]|1[0-2]))?$",
            "description": "Last period, same form and frequency as start."
          },
          "start": {
            "type": "string",
            "pattern": "^\\d{4}(-Q[1-4]|-(0[1-9]|1[0-2]))?$",
            "description": "First period, ISO form: YYYY, YYYY-Qn or YYYY-MM. Must match a frequency the dataset serves."
          }
        },
        "description": "Inclusive ISO period range. \"latest\" is not accepted: name the periods you want. Annual 2020, quarterly 2020-Q1, monthly 2020-01.",
        "additionalProperties": false
      },
      "select": {
        "type": "object",
        "description": "A member code for every dimension of the dataset (other than geography and time) as listed in /structure, including frequency. Every dimension must be named; a missing or unknown dimension or code is a 400, never defaulted.",
        "additionalProperties": {
          "type": "string"
        }
      },
      "dataset": {
        "type": "string",
        "description": "A dataset id from the catalog, as returned by search (/v1/search, or the search_datasets MCP tool), e.g. \"ilo-sdmx:DF_X\"."
      },
      "countries": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 25,
        "minItems": 1,
        "description": "ISO 3166-1 alpha-3 codes (e.g. \"JPN\") or an aggregate code listed in the dataset's /structure. 1 to 25 entries."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_structure 1 change
{
  "name": "get_structure",
  "description": "The published structure of one dataset, free: its dimensions with every member code and label, frequencies, period coverage, the ISO3 countries it serves, and whether it is servable. Call this before get_series to learn the codes to send. Dataset ids come from search_datasets.",
  "inputSchema": {
    "type": "object",
    "required": [
      "dataset"
    ],
    "properties": {
      "dataset": {
        "type": "string",
        "description": "catalog dataset id, e.g. 'ilo-sdmx:DF_X'"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_table 1 change
{
  "name": "get_table",
  "description": "Fetch a STORED table whole, by dataset id (families cn-nbs-census and cn-nbs-yearbook): labelled rows × columns with original-language labels, English overlay, units, and provenance down to the source file. Ids look like 'cn-nbs-census:2010_a0101a'.",
  "inputSchema": {
    "type": "object",
    "required": [
      "dataset_id"
    ],
    "properties": {
      "dataset_id": {
        "type": "string",
        "description": "catalog dataset id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.stackdata/stackdata"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.stackdata/stackdata"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.stackdata%2Fstackdata.svg)](https://glimind.com/server/mcp-registry%2Fio.stackdata%2Fstackdata?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.stackdata%2Fstackdata?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.stackdata%2Fstackdata.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:406d2c70bf2088e9…, first seen 2026-10-17, included at leaf 11453 of 383,755. Version history · verify what your client received.

Tools (6)

Compare: most reliable retrieval servers · most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the StackData MCP server down right now?

As of 2026-11-22 12:33 UTC, the StackData MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 7 minutes.

How many tools does StackData MCP server provide?

StackData MCP server advertises 6 tools, including get_series, get_structure, get_table, resolve_data, search_datasets.

How do I install StackData MCP server?

Point your MCP client at this streamable-http endpoint: https://api.stackdata.io/mcp

Is the StackData MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of StackData MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve