QCC — Executive — Personal Risk Scan

Retrieve personal risk scan for a named director, supervisor, or senior executive with the QCC API. Supply a person name and a search key. Sample fields include content and text. Use it for account research or company due diligence.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body* object
Director, supervisor, or senior executive name. Use together with searchKey to identify the correct person and avoid namesake matches.
Company full registered name or Unified Social Credit Code.
Retrieve personal risk scan for a named director, supervisor, or senior executive. Both the company identity and person name anchor the query.

Sample response

"_meta": {
  "io.modelcontextprotocol/serverInfo": {
    "icons": [
      {
        "mimeType": "image/png",
        "sizes": [
          "60x60"
        ],
        "src": "https://qcc-static.qcc.com/resources/web/omaterial/favicon.png"
      }
    ],
    "name": "qcc-mcp",
    "title": "QCC MCP",
    "version": "1.0.0",
    "websiteUrl": "https://www.qcc.com/"
  }
}
content [1]
[0] {}
textJSON string · parsed preview
content[0].text
{
  "企业名称": "企查查科技股份有限公司",
  "人员名称": "陈德强",
  "摘要": "已扫描陈德强的 18 项个人风险因子:0 项有记录、18 项无记录。",
  "有记录因子数": 0,
  "无记录因子数": 18,
  "风险因子扫描": [
    {
      "风险因子": "失信被执行人",
      "条目数": 0,
      "明细工具": "get_executive_dishonest"
    },
    {
      "风险因子": "被执行人",
      "条目数": 0,
      "明细工具": "get_executive_judgment_debtor"
    },
    {
      "风险因子": "限制高消费",
      "条目数": 0,
      "明细工具": "get_executive_high_consumption_ban"
    },
    {
      "风险因子": "裁判文书",
      "条目数": 0,
      "明细工具": "get_executive_judicial_docs"
    },
    {
      "风险因子": "股权冻结",
      "条目数": 0,
      "明细工具": "get_executive_equity_freeze"
    },
    {
      "风险因子": "立案信息",
      "条目数": 0,
      "明细工具": "get_executive_case_filing"
    },
    {
      "风险因子": "终本案件",
      "条目数": 0,
      "明细工具": "get_executive_terminated_cases"
    },
    {
      "风险因子": "开庭公告",
      "条目数": 0,
      "明细工具": "get_executive_hearing_notice"
    },
    {
      "风险因子": "法院公告",
      "条目数": 0,
      "明细工具": "get_executive_court_notice"
    },
    {
      "风险因子": "送达公告",
      "条目数": 0,
      "明细工具": "get_executive_service_notice"
    },
    {
      "风险因子": "股权出质",
      "条目数": 0,
      "明细工具": "get_executive_equity_pledge"
    },
    {
      "风险因子": "股权质押",
      "条目数": 0,
      "明细工具": "get_executive_stock_pledge"
    },
    {
      "风险因子": "限制出境",
      "条目数": 0,
      "明细工具": "get_executive_exit_restriction"
    },
    {
      "风险因子": "询价评估",
      "条目数": 0,
      "明细工具": "get_executive_valuation_inquiry"
    },
    {
      "风险因子": "行政处罚",
      "条目数": 0,
      "明细工具": "get_executive_admin_penalty"
    },
    {
      "风险因子": "税收违法",
      "条目数": 0,
      "明细工具": "get_executive_tax_violation"
    },
    {
      "风险因子": "诉前调解",
      "条目数": 0,
      "明细工具": "get_executive_pre_litigation_mediation"
    },
    {
      "风险因子": "财产悬赏公告",
      "条目数": 0,
      "明细工具": "get_executive_property_reward_notice"
    }
  ]
}
"type": "text"
"resultType": "complete"

Response result

Response structure

Inferred from examples
  • _metaobject
    • io.modelcontextprotocol/serverInfoobject
      • iconsobject[]
        • mimeTypestring
        • sizesstring[]
        • srcstring
      • namestring
      • titlestring
      • versionstring
      • websiteUrlstring
  • contentobject[]
    • textstring
    • typestring
  • resultTypestring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use QCC — Executive — Personal Risk Scan with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.