risk_insight_fuzzy_searchLABSCO SUMMARY
Due diligence on a Chinese company, one identifier at a time.
The eleven calls line up with the questions a credit, procurement or legal check actually asks — is this company on a violation list, is it being sued, has it been penalised, is its equipment already pledged — and the composite score is there for when you want one number with its reasoning attached. Begin with the fuzzy search: the other ten want a registered name or code, not the brand you know it by.
What it is
A server over Handaas's Chinese corporate-risk data. Name a company — full registered name, registration number, unified social credit code or Handaas id — and it returns what the public record holds: serious-violation listings, chattel mortgages, business anomalies, administrative penalties, court hearings and announcements, intellectual-property pledges, consumption restrictions, and a composite risk score with the reasons behind it. The company-level calls want an exact identifier, so a fuzzy keyword search turns a brand, product, person or partial name into the records the rest accept.
What you get
- A fuzzy search over companies by brand, product, person or partial name, returning the identifiers every other call needs
- Serious-violation records: who listed the company, when, on what grounds, and whether it has since been removed
- Chattel mortgages with the registering authority and number, secured amount, term, mortgagees and the pledged property
- Business-anomaly listings, with the reason and deciding authority for both the listing and the removal
- Administrative penalties: date, amount, grounds, type, deciding authority, decision number, legal basis and status
- Court hearing notices and court announcements — case number, cause of action, court, parties, date and venue, paged
- A litigation risk profile in one call: announcements, filings, hearings, judgments, enforcement, dishonest-debtor and consumption-restriction records with totals
- Consumption restrictions naming the restricted person, the enforcing court, the case number and the filing date
- Intellectual-property pledges: what was pledged, to whom, the registration number, the term, and any cancellation
- A composite risk score and risk level, with the list of reasons that produced it
Requirements
A Handaas account: register at handaas.com for an integrator id, secret id and secret key, or a token if you point a client at Handaas's own hosted endpoint instead. Run locally it needs Python 3.10 or newer and serves over stdio, SSE or streamable HTTP. The data is the mainland-China register throughout, it expects Chinese company identifiers, and results come back in Chinese.
Setup effort
Build from source — clone the repository, then follow the project's own run instructions
USE CASES
01
Screening a company before you sign with it
Turn the brand name into the registered entity, get the composite risk score with its reasons, then read the serious-violation record behind it.
02
Finding out whether a company is in court
One call for the whole litigation picture — filings, hearings, judgments, enforcement and dishonest-debtor records — then the hearing and announcement lists for the detail.
03
Checking whether regulators have already acted
Read the administrative penalties with their amounts, grounds and deciding authority, and whether the company sits on the business-anomaly list.
04
Seeing what is already pledged before you lend
Chattel mortgages with the secured amount, term and mortgagee, plus any intellectual property that has been put up as security.
05
Judging whether a debt is collectable
Check for consumption restrictions on the company and its officers, then read the enforcement and dishonest-debtor totals in the litigation profile.
11 tools
Listed in project docs. Your client may show a different list.
risk_insight_serious_violationsrisk_insight_chattel_mortgagerisk_insight_court_hearingsrisk_insight_litigation_risk_profilerisk_insight_court_announcementsrisk_insight_intellectual_property_pledgerisk_insight_penaltiesrisk_insight_business_anomaliesrisk_insight_consumption_restrictionsenterprise_risk_insight_scoreBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- uv on PATH
- Python 3.10+
- SECRET_ID in your environment
- SECRET_KEY in your environment
- INTEGRATOR_ID in your environment
Where it runs
Of the 6 documented setups, 4 run the server on your machine and 2 connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
uv
TERMINAL
uv run mcp run <YOUR_WORKDIR>/server/mcp_server.pyHosted endpoint
ENDPOINT URL
https://mcp.handaas.com/enterprise/risk_insight?token=<YOUR_TOKEN>Add this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Cursor — local HTTP, Cherry Studio — local HTTP
JSON
{
"mcpServers": {
"enterprise-risk-mcp-server": {
"type": "streamableHttp",
"url": "http://127.0.0.1:8000/mcp"
}
}
}Cursor — stdio, Cherry Studio — stdio
JSON
{
"mcpServers": {
"enterprise-risk-mcp-server": {
"command": "uv",
"args": [
"run",
"mcp",
"run",
"<YOUR_WORKDIR>/server/mcp_server.py"
],
"env": {
"PATH": "<YOUR_WORKDIR>/mcp_env/bin:$PATH",
"PYTHONPATH": "<YOUR_WORKDIR>/mcp_env",
"INTEGRATOR_ID": "<YOUR_INTEGRATOR_ID>",
"SECRET_ID": "<YOUR_SECRET_ID>",
"SECRET_KEY": "<YOUR_SECRET_KEY>"
}
}
}
}Cursor — remote, Cherry Studio — remote
JSON
{
"mcpServers": {
"handaas-ent-mcp-server": {
"type": "streamableHttp",
"url": "https://mcp.handaas.com/enterprise/risk_insight?token=<YOUR_TOKEN>"
}
}
}
