Is the Supplygraphai Daasmart MCP server down?

mcp-registry/io.github.supplygraphai/daasmart · v1.0.0

healthy
Last checked 2026-10-20 09:46 UTC · handshake 1.4s

As of 2026-10-20 09:46 UTC, the Supplygraphai Daasmart MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 81 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.4%
checks observed
3,910
outages (90d)
81
tools
198

Official SupplyGraph.AI data MCP: POIs, parks, regions, industry chains, and companies.

Install Supplygraphai Daasmart MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http supplygraphai-daasmart-mcp-server https://mcp.daasmart.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "supplygraphai-daasmart-mcp-server": {
      "type": "http",
      "url": "https://mcp.daasmart.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 5 warning(s) across 198 tool(s); ~38,467 tokens of tool definitions.
Scores higher than 12% of 15,392 MCP servers Glimind has audited.
Its tool list costs an agent ~38,467 tokens per session — more than 99% of servers.
75 → 75 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints17
Token cost35
Client compatibility100
Protocol100
Reliability70
Stability100

What to fix (5)

198 of 198 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: business_surrounding_company, business_surrounding_shop, cbd_surrounding_amenity, cbd_surrounding_consumption, cbd_surrounding_housing and 193 more

198 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

8 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: chain_close_company_num, company_executed_person, company_executive, enterprise_change_branch_setup, enterprise_change_competitor_moves and 3 more

Loading this server's tool list costs an agent ~38,467 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

Handshake + tools/list takes ~4,014 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 141 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.supplygraphai%2Fdaasmart/fixes

chain_a_taxpayer_company_list 1 change
{
  "name": "chain_a_taxpayer_company_list",
  "description": "基于具体地区(国家,省份,城市,区县)以及具体产业链名称A级纳税人企业列表查询(合并返回总量/生产型/销售型/依赖型文本)。\n涉及指标/类型:A级纳税人企业列表;生产型A级纳税人企业列表;销售型A级纳税人企业列表;依赖型A级纳税人企业列表\n不包含:其他企业分类的统计;仅返回数量不返回名单\n典型问法:2024年全国集成电路A级纳税人企业名单;成都市新能源产业链A级纳税人企业列表;海淀区人工智能A级纳税人企业有哪些\n\nPricing: {\"unit\": \"credits\", \"billing_model\": \"per_run\", \"per_run\": 100, \"unit_description\": \"optional\"}",
  "inputSchema": {
    "type": "object",
    "required": [
      "region",
      "chain_name"
    ],
    "properties": {
      "year": {
        "type": "integer",
        "description": "统计年份,如 2024;可选。"
      },
      "region": {
        "type": "string",
        "description": "地区名称,如「全国」「成都」「北京市海淀区」。"
      },
      "chain_name": {
        "type": "string",
        "description": "产业链或节点名称,如「集成电路」「新能源」「人工智能」。"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "openWorldHint": true,
    "readOnlyHint": true
  },
  "title": "Chain A Taxpayer Company List"
}
chain_a_taxpayer_company_num 1 change
{
  "name": "chain_a_taxpayer_company_num",
  "description": "基于具体地区(国家,省份,城市,区县)以及具体产业链名称A级纳税人企业数量查询(合并返回总量/生产型/销售型/依赖型文本)。\n涉及指标/类型:A级纳税人企业数量;生产型A级纳税人企业数量;销售型A级纳税人企业数量;依赖型A级纳税人企业数量\n不包含:其他企业分类的统计;企业名单明细\n典型问法:2024年全国集成电路A级纳税人企业有多少;成都市新能源产业链A级纳税人企业数量;海淀区人工智能A级纳税人企业有多少家\n\nPricing: {\"unit\": \"credits\", \"billing_model\": \"per_run\", \"per_run\": 100, \"unit_description\": \"optional\"}",
  "inputSchema": {
    "type": "object",
    "required": [
      "region",
      "chain_name"
    ],
    "properties": {
      "year": {
        "type": "integer",
        "description": "统计年份,如 2024;可选。"
      },
      "region": {
        "type": "string",
        "description": "地区名称,如「全国」「成都」「北京市海淀区」。"
      },
      "chain_name": {
        "type": "string",
        "description": "产业链或节点名称,如「集成电路」「新能源」「人工智能」。"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "openWorldHint": true,
    "readOnlyHint": true
  },
  "title": "Chain A Taxpayer Company Count"
}
chain_close_company_list 1 change
{
  "name": "chain_close_company_list",
  "description": "基于具体地区(国家,省份,城市,区县)以及具体产业链名称当年注销的企业列表查询(合并返回总量/生产型/销售型/依赖型文本)。\n涉及指标/类型:当年注销的企业列表;生产型当年注销的企业列表;销售型当年注销的企业列表;依赖型当年注销的企业列表\n不包含:其他企业分类的统计;仅返回数量不返回名单\n典型问法:2024年全国集成电路当年注销的企业名单;成都市新能源产业链当年注销的企业列表;海淀区人工智能当年注销的企业有哪些\n\nPricing: {\"unit\": \"credits\", \"billing_model\": \"per_run\", \"per_run\": 100, \"unit_description\": \"optional\"}",
  "inputSchema": {
    "type": "object",
    "required": [
      "region",
      "chain_name"
    ],
    "properties": {
      "year": {
        "type": "integer",
        "description": "统计年份,如 2024;可选。"
      },
      "region": {
        "type": "string",
        "description": "地区名称,如「全国」「成都」「北京市海淀区」。"
      },
      "chain_name": {
        "type": "string",
        "description": "产业链或节点名称,如「集成电路」「新能源」「人工智能」。"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "openWorldHint": true,
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  },
  "title": "Chain Close Company List"
}

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.github.supplygraphai/daasmart"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.supplygraphai/daasmart"}) 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. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.supplygraphai%2Fdaasmart.svg)](https://glimind.com/server/mcp-registry%2Fio.github.supplygraphai%2Fdaasmart?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.supplygraphai%2Fdaasmart?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.supplygraphai%2Fdaasmart.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.supplygraphai%2Fdaasmart.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.supplygraphai%2Fdaasmart?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

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

Tools (198)

Compare: most reliable data servers · most reliable knowledge servers · most reliable retrieval 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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Supplygraphai Daasmart MCP server down right now?

As of 2026-10-20 09:46 UTC, the Supplygraphai Daasmart MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 81 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Supplygraphai Daasmart MCP server provide?

Supplygraphai Daasmart MCP server advertises 198 tools, including business_surrounding_company, business_surrounding_shop, cbd_surrounding_amenity, cbd_surrounding_consumption, cbd_surrounding_housing.

How do I install Supplygraphai Daasmart MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.daasmart.com/mcp

Is the Supplygraphai Daasmart MCP server safe to connect to an AI agent?

Glimind scanned all 198 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 Supplygraphai Daasmart 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