data-verify-mcp
data-verify-mcp is an MCP server that exposes tools for China-focused data verification and risk-related checks, including identity (ID/phone/bank card), face comparison, enterprise工商 lookup and risk queries, vehicle info and vehicle risk scoring, OCR recognition for multiple document types, and personal综合风险评估.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README claims HTTPS in transit, and that sensitive fields are returned with automatic masking and that it does not store original user-submitted raw data. However, scope/granularity for the access token is not described, and there is no evidence provided of TLS configuration details, secure secret-handling implementation, audit logging controls, or dependency vulnerability status.
⚡ Reliability
Best When
When an agent integration wants a ready MCP-tool interface with clearly named functions covering common KYC/OCR/risk checks, and the deployment context can manage an access token/throughput constraints.
Avoid When
When you require formally specified error codes, retry/idempotency semantics, or strong evidence of dependency/security posture; also avoid if you cannot verify data residency/compliance needs for regulated data.
Use Cases
- • KYC/identity verification workflows (name+ID, phone three-element checks, bank card checks)
- • Fraud/falsification checks using face comparison and OCR extraction
- • Enterprise due diligence (工商信息 lookup and enterprise risk checks)
- • Vehicle management and underwriting (vehicle info lookup and risk scoring)
- • Automated form/data entry assistance via OCR results
- • Risk-scoring triage for lending/lease/booking risk decisions
Not For
- • Real-time regulatory decisioning without human/legal review
- • Handling highly sensitive personal data without appropriate governance, logging controls, and consent
- • Batch processing at very high scale without documented throughput guarantees or SLAs
- • Cases requiring guaranteed data accuracy or audit-grade traceability beyond the tool’s documented outputs
Interface
Authentication
README indicates an optional access token via DATA_VERIFY_ACCESS_TOKEN; no scope model or refresh mechanism is described. Also mentions a free tier of 100/day 'without token'.
Pricing
Pricing is described only qualitatively (free calls/day; registered users unlimited) and lacks explicit cost for higher usage or overage rules.
Agent Metadata
Known Gotchas
- ⚠ Doc examples use a simple {code,msg,data} pattern, but no full error catalog, HTTP/MCP status mapping, or retry guidance is provided.
- ⚠ OCR/face tools require base64 images; input size/format guidance is partial (JPG/PNG, suggest <2MB) without programmatic validation details.
- ⚠ Outputs include masked PII (e.g., id_card/phone partially hidden), which may affect downstream strict matching logic.
- ⚠ Free tier limit is stated, but behavior when exhausted (error code, throttling headers, backoff guidance) is not documented.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for data-verify-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.