Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SupplyGraph.AI Data

REMOTE · MCP.DAASMART.COM · SCANNED SEP 21

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

Available components

remote · mcp.daasmart.com 74
+2 this week 74 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 47185 tokens (~238/item across 198 items; 198 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 198 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 199 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the SupplyGraph.AI Data MCP server?

SupplyGraph.AI Data is a hosted endpoint at https://mcp.daasmart.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.daasmart.com

# add to Claude Code
claude mcp add --transport http supplygraphai-daasmart 'https://mcp.daasmart.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "supplygraphai-daasmart": {
      "url": "https://mcp.daasmart.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "supplygraphai-daasmart": {
      "type": "http",
      "url": "https://mcp.daasmart.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.supplygraphai-daasmart]
url = "https://mcp.daasmart.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "supplygraphai-daasmart": {
      "type": "remote",
      "url": "https://mcp.daasmart.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add supplygraphai-daasmart --url 'https://mcp.daasmart.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  supplygraphai-daasmart:
    url: "https://mcp.daasmart.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "supplygraphai-daasmart": {
      "Transport": "http",
      "Url": "https://mcp.daasmart.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add supplygraphai-daasmart -t streamable-http -u 'https://mcp.daasmart.com/mcp'
// mcp.json
{
  "mcpServers": {
    "supplygraphai-daasmart": {
      "type": "http",
      "url": "https://mcp.daasmart.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://mcp.daasmart.com/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.daasmart.com CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 4 Nov 2025 5 Dec 2026 RSA 2048 SHA256-RSA 93fb1d71ce4c77ff6a27bed15b3ba6c
SANs: *.daasmart.com, daasmart.com
CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA b259422ced9812a15a04e99528a0efa
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US 18 Jan 2024 9 Nov 2031 RSA 2048 SHA256-RSA fe032ab844d033106c50c8e13c8b068

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.daasmart.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
daasmart.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.daasmart.com/mcp Verified 200
http (plaintext) http://mcp.daasmart.com/mcp HTTPS enforced 301 https://mcp.daasmart.com/mcp
MCP tools · 198 exposed · ~47,087 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
park_discredited_company_list ~170

基于具体园区名称失信人企业列表查询。 涉及指标/类型：失信人企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园失信人企业名单；张江高科技园区失信人企业列表；苏州工业园区失信人企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_discredited_company_num ~171

基于具体园区名称失信人企业数量查询。 涉及指标/类型：失信人企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园失信人企业有多少；张江高科技园区失信人企业数量；苏州工业园区失信人企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_have_copyright_company_list ~176

基于具体园区名称拥有软著的企业列表查询。 涉及指标/类型：拥有软著的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园拥有软著的企业名单；张江高科技园区拥有软著的企业列表；苏州工业园区拥有软著的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_have_copyright_company_num ~177

基于具体园区名称拥有软著的企业数量查询。 涉及指标/类型：拥有软著的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园拥有软著的企业有多少；张江高科技园区拥有软著的企业数量；苏州工业园区拥有软著的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_have_no_patent_company_list ~177

基于具体园区名称没有专利的企业列表查询。 涉及指标/类型：没有专利的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园没有专利的企业名单；张江高科技园区没有专利的企业列表；苏州工业园区没有专利的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_have_no_patent_company_num ~178

基于具体园区名称没有专利的企业数量查询。 涉及指标/类型：没有专利的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园没有专利的企业有多少；张江高科技园区没有专利的企业数量；苏州工业园区没有专利的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_have_patent_company_list ~176

基于具体园区名称拥有专利的企业列表查询。 涉及指标/类型：拥有专利的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园拥有专利的企业名单；张江高科技园区拥有专利的企业列表；苏州工业园区拥有专利的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_have_patent_company_num ~177

基于具体园区名称拥有专利的企业数量查询。 涉及指标/类型：拥有专利的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园拥有专利的企业有多少；张江高科技园区拥有专利的企业数量；苏州工业园区拥有专利的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_high_tech_company_list ~171

基于具体园区名称高新技术企业列表查询。 涉及指标/类型：高新技术企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园高新技术企业名单；张江高科技园区高新技术企业列表；苏州工业园区高新技术企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_high_tech_company_num ~172

基于具体园区名称高新技术企业数量查询。 涉及指标/类型：高新技术企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园高新技术企业有多少；张江高科技园区高新技术企业数量；苏州工业园区高新技术企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_invest_company_list ~195

基于具体园区名称近两年有对外投资的企业列表查询。 涉及指标/类型：近两年有对外投资的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园近两年有对外投资的企业名单；张江高科技园区近两年有对外投资的企业列表；苏州工业园区近两年有对外投资的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_invest_company_num ~196

基于具体园区名称近两年有对外投资的企业数量查询。 涉及指标/类型：近两年有对外投资的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园近两年有对外投资的企业有多少；张江高科技园区近两年有对外投资的企业数量；苏州工业园区近两年有对外投资的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_invested_company_list ~196

基于具体园区名称近两年有对外融资的企业列表查询。 涉及指标/类型：近两年有对外融资的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园近两年有对外融资的企业名单；张江高科技园区近两年有对外融资的企业列表；苏州工业园区近两年有对外融资的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_invested_company_num ~197

基于具体园区名称近两年有对外融资的企业数量查询。 涉及指标/类型：近两年有对外融资的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园近两年有对外融资的企业有多少；张江高科技园区近两年有对外融资的企业数量；苏州工业园区近两年有对外融资的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_issued_tender_company_list ~202

基于具体园区名称近两年发起过招标的企业列表查询。 涉及指标/类型：近两年发起过招标的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园近两年发起过招标的企业名单；张江高科技园区近两年发起过招标的企业列表；苏州工业园区近两年发起过招标的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_issued_tender_company_num ~203

基于具体园区名称近两年发起过招标的企业数量查询。 涉及指标/类型：近两年发起过招标的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园近两年发起过招标的企业有多少；张江高科技园区近两年发起过招标的企业数量；苏州工业园区近两年发起过招标的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_listed_company_list ~160

基于具体园区名称上市企业列表查询。 涉及指标/类型：上市企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园上市企业名单；张江高科技园区上市企业列表；苏州工业园区上市企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_listed_company_num ~161

基于具体园区名称上市企业数量查询。 涉及指标/类型：上市企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园上市企业有多少；张江高科技园区上市企业数量；苏州工业园区上市企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_new_start_company_list ~175

基于具体园区名称当年新增的企业列表查询。 涉及指标/类型：当年新增的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园当年新增的企业名单；张江高科技园区当年新增的企业列表；苏州工业园区当年新增的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_new_start_company_num ~176

基于具体园区名称当年新增的企业数量查询。 涉及指标/类型：当年新增的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园当年新增的企业有多少；张江高科技园区当年新增的企业数量；苏州工业园区当年新增的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_participated_tender_company_list ~198

基于具体园区名称近两年参与过投标的企业列表查询。 涉及指标/类型：近两年参与过投标的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园近两年参与过投标的企业名单；张江高科技园区近两年参与过投标的企业列表；苏州工业园区近两年参与过投标的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_participated_tender_company_num ~199

基于具体园区名称近两年参与过投标的企业数量查询。 涉及指标/类型：近两年参与过投标的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园近两年参与过投标的企业有多少；张江高科技园区近两年参与过投标的企业数量；苏州工业园区近两年参与过投标的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_specialized_company_list ~175

基于具体园区名称专精特新企业列表查询。 涉及指标/类型：专精特新企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园专精特新企业名单；张江高科技园区专精特新企业列表；苏州工业园区专精特新企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_specialized_company_num ~176

基于具体园区名称专精特新企业数量查询。 涉及指标/类型：专精特新企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园专精特新企业有多少；张江高科技园区专精特新企业数量；苏州工业园区专精特新企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_tech_oriented_company_list ~182

基于具体园区名称科技型中小型企业列表查询。 涉及指标/类型：科技型中小型企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园科技型中小型企业名单；张江高科技园区科技型中小型企业列表；苏州工业园区科技型中小型企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_tech_oriented_company_num ~183

基于具体园区名称科技型中小型企业数量查询。 涉及指标/类型：科技型中小型企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园科技型中小型企业有多少；张江高科技园区科技型中小型企业数量；苏州工业园区科技型中小型企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_won_tender_company_list ~192

基于具体园区名称近两年有中标的企业列表查询。 涉及指标/类型：近两年有中标的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园近两年有中标的企业名单；张江高科技园区近两年有中标的企业列表；苏州工业园区近两年有中标的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_won_tender_company_num ~193

基于具体园区名称近两年有中标的企业数量查询。 涉及指标/类型：近两年有中标的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园近两年有中标的企业有多少；张江高科技园区近两年有中标的企业数量；苏州工业园区近两年有中标的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_year5_company_list ~180

基于具体园区名称存续5年以上的企业列表查询。 涉及指标/类型：存续5年以上的企业列表 不包含：其他企业分类的统计；仅返回数量不返回名单 典型问法：中关村软件园存续5年以上的企业名单；张江高科技园区存续5年以上的企业列表；苏州工业园区存续5年以上的企业有哪些 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company list result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

park_year5_company_num ~181

基于具体园区名称存续5年以上的企业数量查询。 涉及指标/类型：存续5年以上的企业数量 不包含：其他企业分类的统计；企业名单明细 典型问法：中关村软件园存续5年以上的企业有多少；张江高科技园区存续5年以上的企业数量；苏州工业园区存续5年以上的企业有多少家 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
park_namestringyes园区名称，如「中关村软件园」「张江高科技园区」「苏州工业园区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the company count result. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

patent_chain_classify ~204

基于中国境内具体地区（国家、省份、城市、区县）以及具体产业链名称，统计该范围内指定产业链上的专利数量。 涉及指标/类型：专利数量 不包含：专利明细列表；企业名单；海外地区专利统计 典型问法：2024年全国集成电路专利有多少；成都市新能源产业链专利数量；海淀区人工智能专利数量 Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 100, "unit_description": "optional"}

NameTypeReqDescription
chain_namestringyes产业链或节点名称，如「集成电路」「新能源」「人工智能」。
regionstringyes地区名称，如「全国」「成都」「北京市海淀区」。
yearinteger–统计年份，如 2024；可选。
NameTypeReqDescription
textstringyesText or Markdown response with the patent count result for the specified region and industry chain. Also used for in-progress, failed, cancelled, or waiting-user messages.

No examples provided.

poi_data_automotive ~363

基于明确的市级或区县级行政区名称，查询该行政区范围内的汽车与摩托相关 POI 明细列表。覆盖：加油站、充电站、4S店、汽修洗车、摩托车服务等。不回答加油站数量等统计（请用兴趣点数量指标）。典型问法：某区加油站分布、充电站列表、洗车场有哪些。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「加油站充电站汽修等汽车服务分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的加油站分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_dining ~367

基于明确的市级或区县级行政区名称，查询该行政区范围内的餐饮 POI 明细列表（门店名称与坐标）。覆盖：中餐厅、快餐、咖啡厅、茶饮、甜品等。不回答餐饮门店数量/密度（请用兴趣点数量指标）。典型问法：某区星巴克分布、有哪些中餐厅、肯德基门店列表。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「餐厅咖啡茶饮等餐饮门店分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的星巴克分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_education_culture ~354

基于明确的市级或区县级行政区名称，查询该行政区范围内的科教文化 POI 明细列表。覆盖：小学/中学/高校、博物馆、图书馆、科技馆等。不回答学校/场馆数量统计（请用兴趣点数量指标）。典型问法：某区小学分布、有哪些高等院校、博物馆列表。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「学校博物馆图书馆等科教分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的小学分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_finance_business ~349

基于明确的市级或区县级行政区名称，查询该行政区范围内的金融商务与住宅 POI 明细列表。覆盖：银行、写字楼、产业园区、住宅小区等。不回答银行/小区数量统计（请用兴趣点数量指标）。典型问法：某区银行分布、商务写字楼列表、住宅小区分布。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「银行写字楼住宅小区等分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的银行分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_life_service ~356

基于明确的市级或区县级行政区名称，查询该行政区范围内的生活服务与休闲娱乐 POI 明细列表。覆盖：美容美发、维修、物流、健身房、电影院、娱乐场所等。不回答这类设施的数量统计（请用兴趣点数量指标）。典型问法：某区健身房分布、电影院列表、美容美发店有哪些。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「健身房影院美容等生活休闲分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的健身房分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_lodging_scenic ~362

基于明确的市级或区县级行政区名称，查询该行政区范围内的酒店与景区 POI 明细列表。覆盖：星级宾馆、经济型酒店、公园、动物园、风景名胜等。不回答酒店/公园数量统计（请用兴趣点数量指标）。典型问法：某区五星级宾馆分布、有哪些公园、风景名胜列表。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「酒店公园景区等住宿景区分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的五星级宾馆分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_medical ~348

基于明确的市级或区县级行政区名称，查询该行政区范围内的医疗保健 POI 明细列表。覆盖：综合医院、三甲医院、专科医院、卫生院、药店等。不回答医院/药店数量（请用兴趣点数量指标）。典型问法：某区综合医院分布、有哪些三甲医院、药店列表。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「医院诊所药店等医疗点分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的综合医院分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_public_facility ~351

基于明确的市级或区县级行政区名称，查询该行政区范围内的公共与政务 POI 明细列表。覆盖：政府机关、派出所、社会团体、公共厕所等。不回答这类设施的数量统计（请用兴趣点数量指标）。典型问法：某区派出所分布、有哪些政府机关、公共厕所列表。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「政府机关派出所公厕等公共设施分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的派出所分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_shopping ~347

基于明确的市级或区县级行政区名称，查询该行政区范围内的购物 POI 明细列表。覆盖：超市、商场、购物中心、便利店、专卖店等。不回答超市/商场数量统计（请用兴趣点数量指标）。典型问法：某区超市分布、有哪些购物中心、便利店列表。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「超市商场便利店等购物点分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：武侯区的超市分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

poi_data_transport ~399

基于明确的市级或区县级行政区名称，查询该行政区范围内的交通设施 POI 明细列表（名称、坐标、分布、有哪些）。覆盖：机场、火车站、地铁站、公交站、停车场等。不回答「有多少个地铁站」等数量统计（数量请用医院超市等兴趣点数量指标 gov_data_poi_amenity；通行速度/吞吐量请用通行速度运量等交通运行指标）。典型问法：某区地铁站分布、有哪些火车站、公交站列表。 Pricing: {"unit": "credits", "billing_model": "per_data_unit", "meter": {"credits_per_unit": 1, "unit_description": "One data unit = one region × one POI type (example: Wuhou District × metro station). Not charged per POI store/row."}}

NameTypeReqDescription
gov_namestring–可选，单一地区名（地级市或区县）。不支持同时查多个地区；不传时从 input_text 抽取。
input_textstringyes用户查询文本，描述「地铁站公交站火车站等交通设施分布」POI 明细/分布意图；须指向单一地区（地级市或区县）。示例：成都市武侯区的地铁站分布
poi_typestring–可选，POI 类型名或编码（如 地铁站 / 150500）；用于消歧；不传时从 input_text 识别，且限定在本主题候选集内。
versionstring–可选数据版本，如 '2022' 或 '2022-12-01'；不传则使用库内默认/最近可用版本。

Structured output declared, but exposes no named fields.

No examples provided.

search_company_candidates ~108

Search company candidates by company name, optionally filtered by country or region, and return possible matching records with mapped company IDs for caller-side selection. Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 1}

NameTypeReqDescription
textstringyesCompany name with optional country or region. The input should contain a company name, and may optionally include its country or region (e.g. 'Tesla United States', 'Samsung South Korea', 'Huawei Chi…

Structured output declared, but exposes no named fields.

No examples provided.

search_region_candidates ~131

Resolves natural-language country or region names (including aliases and abbreviations) against SupplyGraph’s internal geography registry and returns a list of standardized region names for downstream agent and MCP tool consumption. Pricing: {"unit": "credits", "billing_model": "per_run", "per_run": 1}

NameTypeReqDescription
textstringyesCountry or region name in natural language, including aliases and abbreviations (e.g. 'China', 'USA', 'South Korea', 'Hong Kong', '中国', '美国'). The tool searches the internal geography registry and re…

Structured output declared, but exposes no named fields.

No examples provided.

sg_chokepoint ~131

Analyzes multi-tier supply chains to detect single-country concentration and quantify geographic dependency across regions. Pricing: {"unit": "credits", "per_run": 264590}

NameTypeReqDescription
pidstringyesInternal company ID for the target enterprise, obtained from the search_company_candidates MCP tool (e.g. a77828f060c866441f2403384b271e63 for Tesla, Inc.).
region_namestringyesStandardized country or region name for geographic concentration analysis, obtained from the search_region_candidates MCP tool (e.g. China, United States, Hong Kong).

Structured output declared, but exposes no named fields.

No examples provided.

sg_visualization ~88

Generates global multi-tier supply-chain graphs providing full visibility into enterprise and product dependencies. Pricing: {"unit": "credits", "per_run": 264590}

NameTypeReqDescription
pidstringyesInternal company ID for the target enterprise, obtained from the search_company_candidates MCP tool (e.g. a77828f060c866441f2403384b271e63 for Tesla, Inc.).

Structured output declared, but exposes no named fields.

No examples provided.

supply_chain_risk_prediction ~81

Continuously monitors global supply chain risk events and evaluates whether, how, and to what extent those events may affect a target company. Pricing: {"unit": "credits", "per_run": 264590}

NameTypeReqDescription
event_infoobjectyesEvaluates how a supply chain risk event may affect a target company through multi-tier supply chain propagation analysis.

Structured output declared, but exposes no named fields.

No examples provided.

tariff_calc ~110

Calculates U.S. customs duties by combining HTS base rates with applicable Chapter 99 measures, providing transparent, rule-based tariff outcomes. Pricing: {"unit": "credits", "per_run": 10}

NameTypeReqDescription
country_or_regionstringyesCountry or region of origin for the imported product, e.g. China, Mexico, European Union.
product_descriptionstringyesDescription of the product to import into the United States, e.g. HS code, product name, material, or specifications.

Structured output declared, but exposes no named fields.

No examples provided.

tariff_classification ~69

Classifies products into correct HTS codes from text or documents, automating tariff lookup and ensuring customs compliance in real time. Pricing: {"unit": "credits", "per_run": 2}

NameTypeReqDescription
product_descriptionstringyesDescription of the product used to identify HS/HTS codes.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the SupplyGraph.AI Data MCP server?

SupplyGraph.AI Data is an MCP server listed in the public MCP registry as io.github.SupplyGraphAI/daasmart. Official SupplyGraph.AI data MCP: POIs, parks, regions, industry chains, and companies. This page covers its hosted endpoint (https://mcp.daasmart.com/mcp).

Is the SupplyGraph.AI Data MCP server safe to use?

SupplyGraph.AI Data scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SupplyGraph.AI Data MCP server expose?

SupplyGraph.AI Data exposes 198 tools: poi_data_shopping, gov_data_population, company_branch, company_certlist, company_can_apply_subsidy, and 193 more. Their descriptions and schemas cost roughly 47,087 tokens of context every time the server is loaded.

Does the SupplyGraph.AI Data MCP server require authentication?

No. We connected to SupplyGraph.AI Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SupplyGraph.AI Data MCP server still maintained?

SupplyGraph.AI Data is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.