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.

China Policy, Licensing & Country Information

REMOTE · MCP.AGENTDATACORE.COM · SCANNED SEP 27

Search policy entries by topic keywords.

+3 this week 70 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 Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1341 tokens (~268/item across 5 items; 5 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the China Policy, Licensing & Country Information MCP server?

China Policy, Licensing & Country Information is a hosted endpoint at https://mcp.agentdatacore.com/mcp/products/policy, 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.agentdatacore.com

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

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.

  • 26 Sept 26 +1

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

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Sept 26 65

    First indexed and scored.

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 27 Sept 2026 · Probed https://mcp.agentdatacore.com/mcp/products/policy

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.agentdatacore.com CN=YE1,O=Let's Encrypt,C=US 15 Sept 2026 14 Dec 2026 ECDSA 256 ECDSA-SHA384 5a7ec5bb97d88b547abb4eb30a6c23bff4a
SANs: agentdatacore.com, api.agentdatacore.com, mcp.agentdatacore.com, www.agentdatacore.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.agentdatacore.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agentdatacore.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.agentdatacore.com/mcp/products/policy Verified 200
http (plaintext) http://mcp.agentdatacore.com/mcp/products/policy Inconclusive 405
MCP tools · 5 exposed · ~1,127 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
find_country_institutions ~312

Find recorded institutions and roles for a country, optionally filtered by institution text. Inputs: country, institution. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: country. Missing required or invalid input produces an argument error.

NameTypeReqDescription
countrystringyesCountry or region label exactly as recorded; no country-code or alias conversion. Exact match. Non-empty string, at most 256 characters; control characters are not accepted. Required. Supplied filter…
institutionstring–Recorded institution name or entity identifier text. Literal, case-sensitive substring match; no fuzzy search. Non-empty string, at most 256 characters; control characters are not accepted. Optional;…
limitinteger–Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
offsetinteger–Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
snapshotstring–Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

No output schema declared.

No examples provided.

find_license_catalog_items ~238

Find licence catalog entries by recorded product or commodity text. Inputs: product. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: product. Missing required or invalid input produces an argument error.

NameTypeReqDescription
limitinteger–Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
offsetinteger–Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
productstringyesRecorded licence commodity or subject text. Literal, case-sensitive substring match; no fuzzy search. Non-empty string, at most 256 characters; control characters are not accepted. Required.
snapshotstring–Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

No output schema declared.

No examples provided.

get_gazette_items ~295

Find entries in a gazette issue, optionally filtered by document number. Inputs: issue, document_number. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: issue. Missing required or invalid input produces an argument error.

NameTypeReqDescription
document_numberstring–Document number exactly as recorded. Exact match. Non-empty string, at most 256 characters; control characters are not accepted. Optional; omitted means no filter on this field. Supplied filters are…
issuestringyesGazette issue label exactly as recorded. Exact match. Non-empty string, at most 256 characters; control characters are not accepted. Required. Supplied filters are combined with AND.
limitinteger–Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
offsetinteger–Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
snapshotstring–Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

No output schema declared.

No examples provided.

get_information_standard ~42

Retrieve definitions of information formation classes, provenance fields and snapshot/version metadata. Takes no arguments. Returns the information-standard document, not business records or an assessment of facts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_policy_facts ~240

Find policy and document facts by title or document-number text. Inputs: query. Returns paginated structured records with source_class, provenance, snapshot, pagination and limits. Recorded facts only; this query performs no new inference or aggregation. Coverage is limited to the available snapshot. No match returns an empty data array. Required: query. Missing required or invalid input produces an argument error.

NameTypeReqDescription
limitinteger–Maximum number of records returned. Integer 1–100; default 20. A page may contain fewer records.
offsetinteger–Zero-based pagination offset. Integer 0–999; default 0. Offsets of 1000 or greater are rejected. Use the returned next_offset when present.
querystringyesRecorded policy title or document-number text. Literal, case-sensitive substring match; no fuzzy search. Non-empty string, at most 256 characters; control characters are not accepted. Required.
snapshotstring–Optional expected snapshot.version, not a historical-version selector. If omitted, the current dataset snapshot is used. For continued pagination reuse the previous response snapshot.version; a misma…

No output schema declared.

No examples provided.

Common questions

What is the China Policy, Licensing & Country Information MCP server?

China Policy, Licensing & Country Information is an MCP server listed in the public MCP registry as io.github.huangjunsong404-crypto/china-policy-licensing-cou…. Search policy entries by topic keywords. This page covers its hosted endpoint (https://mcp.agentdatacore.com/mcp/products/policy).

Is the China Policy, Licensing & Country Information MCP server safe to use?

China Policy, Licensing & Country Information scores 70 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 China Policy, Licensing & Country Information MCP server expose?

China Policy, Licensing & Country Information exposes 5 tools: find_country_institutions, get_gazette_items, search_policy_facts, find_license_catalog_items, get_information_standard. Their descriptions and schemas cost roughly 1,127 tokens of context every time the server is loaded.

Does the China Policy, Licensing & Country Information MCP server require authentication?

No. We connected to China Policy, Licensing & Country Information without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the China Policy, Licensing & Country Information MCP server still maintained?

China Policy, Licensing & Country Information is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.