How do I find my Qichacha App Key and Secret?

Log in to the [Qichacha OpenAPI Platform](https://openapi.qcc.com/), go to [Console] -> [My Interfaces], and you will find your unique App Key and Secret Key there.

Is there a limit to the search queries?

The search limits depend on your Qichacha OpenAPI subscription plan. You can use the `get_account_status` tool to check your current balance and usage limits.

Can I check risk information for multiple companies?

Yes. You can use the `list_risks` tool sequentially for different company names to retrieve risk indicators and court cases for each enterprise.

Qichacha / 企查查 MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Qichacha / 企查查
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Qichacha / 企查查 through Vinkius, pass the Edge URL in the `mcps` parameter and every Qichacha / 企查查 tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Qichacha / 企查查 Specialist",
    goal="Help users interact with Qichacha / 企查查 effectively",
    backstory=(
        "You are an expert at leveraging Qichacha / 企查查 tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Qichacha / 企查查 "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Qichacha / 企查查 MCP Server

Empower your AI agent to orchestrate your business intelligence and due diligence with Qichacha (企查查), the premier enterprise data platform in China. By connecting Qichacha to your agent, you transform complex industrial research, ownership auditing, and risk monitoring into a natural conversation. Your agent can instantly search for companies, retrieve detailed registration metadata, browse shareholder structures, and monitor industrial abnormalities without you ever needing to navigate the comprehensive Qichacha portal. Whether you are conducting B2B lead research or auditing potential partners, your agent acts as a real-time business intelligence assistant, keeping your data accurate and your decisions informed.

When paired with CrewAI, Qichacha / 企查查 becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Qichacha / 企查查 tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Enterprise Orchestration — Fuzzy search for companies and retrieve detailed basic and industrial metadata.
Ownership Auditing — Browse shareholder lists and outward investments to identify corporate structures.
Personnel Monitoring — List main staff and executives to identify key decision-makers within an enterprise.
Risk Management — Retrieve risk indicators, court cases, and industrial abnormalities for any registered company.
IP Tracking — Browse registered trademarks, patents, and copyrights to audit intellectual property assets.

The Qichacha / 企查查 MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Qichacha / 企查查 to CrewAI via MCP

Follow these steps to integrate the Qichacha / 企查查 MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Qichacha / 企查查

Why Use CrewAI with the Qichacha / 企查查 MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Qichacha / 企查查 through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Qichacha / 企查查 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Qichacha / 企查查 MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Qichacha / 企查查 for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Qichacha / 企查查, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Qichacha / 企查查 tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Qichacha / 企查查 against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Qichacha / 企查查 MCP Tools for CrewAI (10)

These 10 tools become available when you connect Qichacha / 企查查 to CrewAI via MCP:

fuzzy_search

Enterprise fuzzy search

get_account_status

Get OpenAPI account status

get_basic_info

Get enterprise basic info

get_full_details

Get full enterprise details

list_branches

List company branches

list_investments

List outward investments

list_ip

List intellectual property

list_risks

List enterprise risk info

list_shareholders

List company shareholders

list_staff

List main staff/executives

Example Prompts for Qichacha / 企查查 in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Qichacha / 企查查 immediately.

"Search for companies named 'Xiaomi' in Qichacha."

"Show me the shareholder structure for 'Tencent'."

"Check for any risk information regarding 'Ant Group'."

Troubleshooting Qichacha / 企查查 MCP Server with CrewAI

Common issues when connecting Qichacha / 企查查 to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Qichacha / 企查查 + CrewAI FAQ

Common questions about integrating Qichacha / 企查查 MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.