QCC — Shareholders

Retrieve registered shareholders, ownership percentages, subscribed contributions, and contribution dates for ownership analysis with the QCC API. Supply a search key. Sample fields include content and text. Use the result as input for a related analysis or application.

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
Company full registered name or Unified Social Credit Code.
Retrieve registered shareholders, ownership percentages, subscribed contributions, and contribution dates for ownership analysis.

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
{
  "企业名称": "企查查科技股份有限公司",
  "摘要": "该查询实体共有13条股东信息记录。",
  "股东信息": [
    {
      "股东名称": "陈德强",
      "持股比例": "35.4938%",
      "持股数": "128,576,121"
    },
    {
      "股东名称": "上海荷花缘企业管理中心(有限合伙)",
      "持股比例": "16.3440%",
      "持股数": "59,205,999"
    },
    {
      "股东名称": "杨京",
      "持股比例": "12.0739%",
      "持股数": "43,737,785"
    },
    {
      "股东名称": "苏州知彼信息科技中心(有限合伙)",
      "持股比例": "11.5446%",
      "持股数": "41,820,487"
    },
    {
      "股东名称": "苏州知己网络科技中心(有限合伙)",
      "持股比例": "5.9627%",
      "持股数": "21,600,004"
    },
    {
      "股东名称": "杭州险峰投资合伙企业(有限合伙)",
      "持股比例": "5.6899%",
      "持股数": "20,611,842"
    },
    {
      "股东名称": "施阳",
      "持股比例": "4.7345%",
      "持股数": "17,150,788"
    },
    {
      "股东名称": "苏州中新兴富新兴产业投资合伙企业(有限合伙)",
      "持股比例": "2.8025%",
      "持股数": "10,152,000"
    },
    {
      "股东名称": "苏州工业园区元禾鼎业创业投资合伙企业(有限合伙)",
      "持股比例": "1.9876%",
      "持股数": "7,199,995"
    },
    {
      "股东名称": "苏州中新兴富数智创业投资合伙企业(有限合伙)",
      "持股比例": "1.3273%",
      "持股数": "4,807,987"
    },
    {
      "股东名称": "上海国方构筑企业服务中心(有限合伙)",
      "持股比例": "0.8295%",
      "持股数": "3,004,992"
    },
    {
      "股东名称": "中信证券投资有限公司",
      "持股比例": "0.6211%",
      "持股数": "2,250,000"
    },
    {
      "股东名称": "宁波君安控股有限公司",
      "持股比例": "0.5885%",
      "持股数": "2,132,000"
    }
  ]
}
"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 — Shareholders with your agent

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