Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .env.example
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# API base URL (required)
DATA_VERIFY_API_BASE=https://api.example.com

# Access token for unlimited usage (optional)
# Free tier: 20-50 requests/day per tool without token
DATA_VERIFY_ACCESS_TOKEN=your_token_here
5 changes: 5 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
node_modules/
dist/
*.js.map
.env
.DS_Store
Empty file.
674 changes: 0 additions & 674 deletions .ipynb_checkpoints/LICENSE-checkpoint

This file was deleted.

131 changes: 0 additions & 131 deletions .ipynb_checkpoints/README-checkpoint.md

This file was deleted.

Empty file.
Empty file.
Empty file removed CNAME
Empty file.
19 changes: 19 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Code of Conduct

## Our Pledge

We are committed to providing a friendly, safe, and welcoming environment for all contributors.

## Our Standards

- Be respectful and inclusive
- Accept constructive criticism gracefully
- Focus on what is best for the community

## Enforcement

Instances of abusive behavior may be reported to the project maintainers. All complaints will be reviewed and investigated.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1.
49 changes: 49 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
# Contributing

Thank you for your interest in contributing to Data Verify MCP Server!

## How to Contribute

1. Fork the repository
2. Create a feature branch (`git checkout -b feature/my-feature`)
3. Commit your changes (`git commit -m 'Add my feature'`)
4. Push to the branch (`git push origin feature/my-feature`)
5. Open a Pull Request

## Development Setup

```bash
git clone https://github.com/pancheng/data-verify-mcp.git
cd data-verify-mcp
npm install
npm run dev
```

## Building

```bash
npm run build
```

## Testing

```bash
npm test
```

## Code Style

- Use TypeScript strict mode
- Follow existing code patterns
- Add JSDoc comments for public APIs
- Keep tool descriptions clear and bilingual (English + Chinese)

## Reporting Issues

Please use [GitHub Issues](https://github.com/pancheng/data-verify-mcp/issues) to report bugs or request features.

## Security

- **Never** commit API tokens or credentials
- Use environment variables for sensitive configuration
- See [SECURITY.md](SECURITY.md) for vulnerability reporting
695 changes: 21 additions & 674 deletions LICENSE

Large diffs are not rendered by default.

571 changes: 477 additions & 94 deletions README.md

Large diffs are not rendered by default.

213 changes: 213 additions & 0 deletions README_EN.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,213 @@
[中文](https://github.com/CCCpan/data-verify-mcp/blob/main/README.md) | English

# 🔐 data-verify-mcp

[![npm version](https://img.shields.io/npm/v/data-verify-mcp.svg)](https://www.npmjs.com/package/data-verify-mcp)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

**The most comprehensive MCP Server for Chinese data verification**, integrating **5 categories with 10 verification tools** — covering identity authentication, enterprise credit, vehicle logistics, intelligent OCR, and risk assessment.

Seamlessly integrates with **OpenClaw / QClaw / Claude / Cursor / VSCode** and other mainstream AI tools, empowering your AI assistant with professional-grade data verification capabilities.

## Features

| Category | Tools | Description |
|---|---|---|
| Identity Verification | 4 | ID card, phone, bank card verification & face comparison |
| Enterprise Verification | 2 | Business info query & enterprise risk check |
| Vehicle | 2 | Vehicle information query & risk scoring |
| OCR Recognition | 1 | Document OCR for ID cards, bank cards, licenses |
| Risk Assessment | 1 | Comprehensive personal risk assessment |

## Quick Start

### Run directly with npx

```bash
npx data-verify-mcp@latest
```

### Install globally

```bash
npm install -g data-verify-mcp
data-verify-mcp
```

## Configuration

You need to set the `DATA_VERIFY_API_KEY` environment variable to authenticate API requests.

### OpenClaw / QClaw / Claude Desktop

Add the following to your Claude Desktop configuration file (`claude_desktop_config.json`):

```json
{
"mcpServers": {
"data-verify-mcp": {
"command": "npx",
"args": ["-y", "data-verify-mcp@latest"],
"env": {
"DATA_VERIFY_API_KEY": "your-api-key"
}
}
}
}
```

### Claude Code

```bash
claude mcp add data-verify-mcp -e DATA_VERIFY_API_KEY=your-api-key -- npx -y data-verify-mcp@latest
```

### Cursor / Windsurf

Add to your Cursor MCP configuration (`.cursor/mcp.json`):

```json
{
"mcpServers": {
"data-verify-mcp": {
"command": "npx",
"args": ["-y", "data-verify-mcp@latest"],
"env": {
"DATA_VERIFY_API_KEY": "your-api-key"
}
}
}
}
```

## Tools

### Identity Verification

#### `verify_identity`

ID card two-element verification — checks whether a name matches an ID number.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | Yes | Full name |
| `id_number` | string | Yes | 18-digit ID card number |

#### `verify_phone_three`

Phone three-element verification — checks whether name, ID number, and phone number match.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | Yes | Full name |
| `id_number` | string | Yes | 18-digit ID card number |
| `phone` | string | Yes | 11-digit mobile phone number |

#### `verify_bank_card`

Bank card three/four-element verification — validates bank card holder information.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | Yes | Full name |
| `id_number` | string | Yes | 18-digit ID card number |
| `bank_card` | string | Yes | Bank card number |
| `phone` | string | No | Mobile phone number (4-element mode) |

#### `face_compare`

Face comparison — compares two face photos and returns a similarity score.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `photo_a` | string | Yes | Base64-encoded first photo |
| `photo_b` | string | Yes | Base64-encoded second photo |

### Enterprise Verification

#### `verify_enterprise`

Enterprise business information query — retrieves registration details by company name or credit code.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `keyword` | string | Yes | Company name or unified social credit code |

#### `query_enterprise_risk`

Enterprise risk check — queries risk records such as legal proceedings and penalties.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `keyword` | string | Yes | Company name or unified social credit code |

### Vehicle

#### `query_vehicle_info`

Vehicle information query — retrieves vehicle details by plate number or VIN.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `plate_number` | string | No | License plate number |
| `vin` | string | No | Vehicle identification number (VIN) |

> At least one of `plate_number` or `vin` must be provided.

#### `vehicle_risk_score`

Vehicle risk scoring — evaluates risk level based on vehicle and owner information.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `plate_number` | string | Yes | License plate number |
| `vin` | string | Yes | Vehicle identification number (VIN) |
| `owner_name` | string | Yes | Vehicle owner name |

### OCR Recognition

#### `ocr_recognize`

Document OCR recognition — extracts text fields from various document types.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `image` | string | Yes | Base64-encoded document image |
| `doc_type` | string | Yes | Document type: `id_card_front`, `id_card_back`, `bank_card`, `driver_license`, `vehicle_license` |

### Risk Assessment

#### `risk_assessment`

Comprehensive personal risk assessment — evaluates an individual's overall risk profile.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | Yes | Full name |
| `id_number` | string | Yes | 18-digit ID card number |
| `phone` | string | No | Mobile phone number |

## FAQ

**Q: How do I obtain an API key?**
A: Contact the service provider to apply for an API key, then set it via the `DATA_VERIFY_API_KEY` environment variable.

**Q: Which regions are supported?**
A: This service is designed for Chinese data verification scenarios, including mainland China ID cards, phone numbers, enterprises, and vehicles.

**Q: What image formats are supported for OCR?**
A: JPEG and PNG formats are supported. Images must be Base64-encoded before being passed to the tool.

**Q: Is there a rate limit?**
A: Rate limits depend on your API plan. Refer to your service agreement for details.

## Contact

- WeChat: chenganp
- Email: 345048305@qq.com

> 💡 Need a custom MCP Server? Check out our [MCP Development Service](https://github.com/CCCpan/mcp-custom-dev)

## License

[MIT](LICENSE)
23 changes: 23 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# Security Policy

## Reporting a Vulnerability

If you discover a security vulnerability, please report it responsibly:

- **Do NOT** open a public issue
- Email the maintainer directly or use GitHub's private vulnerability reporting

## Security Considerations

- API tokens and access credentials should only be stored in environment variables
- Never commit `.env` files or tokens to version control
- The MCP server communicates with the verification API over HTTPS
- All sensitive data (ID card numbers, phone numbers, bank card numbers) is transmitted encrypted and not stored locally
- Face comparison images are processed in memory and not persisted

## Best Practices

- Rotate your `DATA_VERIFY_ACCESS_TOKEN` periodically
- Use the minimum required permissions
- Monitor your API usage for unexpected patterns
- Do not log or store personally identifiable information (PII) in plain text
Binary file removed build.zip
Binary file not shown.
Binary file removed chome-extension/build.zip
Binary file not shown.
Binary file removed datas/train/datas.zip
Binary file not shown.
Loading