mcpbeat Sign in

Fd Health Config MCP Server

answering

Fd Health Config is answering right now. Last checked 8 min ago.

finddata 中央库健康巡检配置(总闸/限流)只读 MCP — fd_open_data.public.health_config — 想 7×24 常驻 → 萬星

Uptime history 70 hours of history · worst hour 0%
70 hours agonow
87.9%
Uptime 24h
80 of 91 checks
—
Tools
hidden behind auth
1326 ms
Response time
average over 24h
API key
Access
streamable-http

Fd Health Config does not always answer

Over the last week it answered 93.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add fd-health-config --transport http https://mcp.finddatatech.cloud/fd-health-config/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.finddatatech.cloud/fd-health-config/mcp
~/.codex/config.toml
[mcp_servers.fd-health-config]
url = "https://mcp.finddatatech.cloud/fd-health-config/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fd-health-config": {
      "url": "https://mcp.finddatatech.cloud/fd-health-config/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "fd-health-config": {
      "type": "http",
      "url": "https://mcp.finddatatech.cloud/fd-health-config/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.finddatatech.cloud/fd-health-config/mcp streamable-http needs key 1027 ms 8 min ago

Alternatives to Fd Health Config

same job, measured the same way
F
Fd Daas MCP Cust1
by finddatatechnology

FindData DAAS MCP — 第二客户工作区实例(per-customer isolation witness, facet-mcp-foundation… — 想 7×24 常驻 → 萬星

answering
Bag Health MCP
by malkreide

BAG public-health open data: indicators, programmes, statistics

119 installs/wk local only
Opencollective
by pipeworx-io

Open Collective public MCP.

378 installs/wk 48 tools answering
Avoindata Fi
by pipeworx-io

Finland Open Data (www.avoindata.fi/data/en) CKAN MCP.

403 installs/wk 47 tools answering
Nihr
by pipeworx-io

UK NIHR (National Institute for Health and Care Research) open-data MCP.

355 installs/wk 49 tools answering
Osf
by pipeworx-io

OSF (Open Science Framework, by the Center for Open Science) MCP. Keyless public-data API…

365 installs/wk 48 tools answering
Datos Gob Do MCP Server
by alcastaro

MCP server for datos.gob.do — Dominican Republic open government data (CKAN 2.11).

108 installs/wk local only
Data Paris
by pipeworx-io

Paris Open Data (opendata.paris.fr) — OpenDataSoft MCP.

445 installs/wk 47 tools answering

Fd Health Config — questions

Answers built from our own checks of this server.

Why is there no tool list for Fd Health Config?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 87.9% of checks in the last 24 hours got a reply.
Is Fd Health Config working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 80 of 91 checks got a reply (87.9%), average response time 1326 ms. The bar chart above shows every period we have measured.
How do I connect Fd Health Config?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.
Does Fd Health Config need an API key?
Yes. Every time we knock, Fd Health Config answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Fd Health Config?
It answers our handshake in 1326 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.