# Identifier Validator + Stablecoin Peg Verdict (remote · identifier-validator-api.yuechenxi-importexport.workers.dev)

Offline IBAN/BIC/EU VAT/card/ISBN/GTIN validators + live USD stablecoin peg-health verdict.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `identifier-validator-api.yuechenxi-importexport.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-yuechenxi-importexport-identifier-validator-api-identifier-validator/identifier-validator-api.md), [page](https://verifymcp.io/servers/dev-workers-yuechenxi-importexport-identifier-validator-api-identifier-validator/identifier-validator-api)

## Channel facts

- Endpoint: `https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 661 tokens (~82/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Identifier Validator + Stablecoin Peg Verdict MCP server?

Identifier Validator + Stablecoin Peg Verdict is a hosted endpoint at https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-workers-yuechenxi-importexport-identifier-va 'https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-yuechenxi-importexport-identifier-va": {
      "url": "https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-yuechenxi-importexport-identifier-va": {
      "type": "http",
      "url": "https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-yuechenxi-importexport-identifier-va]
url = "https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-yuechenxi-importexport-identifier-va": {
      "type": "remote",
      "url": "https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-yuechenxi-importexport-identifier-va --url 'https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-yuechenxi-importexport-identifier-va:
    url: "https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-yuechenxi-importexport-identifier-va": {
      "Transport": "http",
      "Url": "https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-yuechenxi-importexport-identifier-va -t streamable-http -u 'https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-yuechenxi-importexport-identifier-va": {
      "type": "http",
      "url": "https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 64)

First indexed and scored.

## MCP tools (8)

### `validate_iban` (~78 tokens)

Validate IBAN

Validate an IBAN offline: country rules, length, BBAN structure, mod-97 checksum. Returns validity, country, SEPA flag and formatted IBAN. Structural check only: cannot tell whether the account exists.

Input parameters:

- `iban` (string, required): The IBAN, spaces allowed. e.g. DE89370400440532013000

### `validate_bic` (~54 tokens)

Validate BIC/SWIFT

Validate a BIC/SWIFT code structure (8 or 11 chars), country, location and branch code.

Input parameters:

- `bic` (string, required): The BIC/SWIFT code. e.g. DEUTDEFF

### `validate_vat` (~81 tokens)

Validate EU VAT number

Validate an EU/EEA (plus GB, NO, CH and more) VAT number format and checksum offline. Does not check VIES registration status.

Input parameters:

- `country` (string): Optional ISO country code if the number has no prefix.
- `vat` (string, required): The VAT number, with or without country prefix. e.g. DE811569869

### `validate_card` (~71 tokens)

Validate payment card number

Luhn check and network detection (Visa, Mastercard, Amex, Discover, Diners, JCB, UnionPay, Maestro, Mir). Returns masked output only; nothing is stored.

Input parameters:

- `number` (string, required): The card number (use test numbers). e.g. 4111111111111111

### `validate_isbn` (~44 tokens)

Validate ISBN

Validate ISBN-10 or ISBN-13 check digit and convert between the two.

Input parameters:

- `isbn` (string, required): The ISBN. e.g. 9780306406157

### `validate_gtin` (~49 tokens)

Validate GTIN/EAN/UPC

Validate GTIN-8/12/13/14 (EAN/UPC barcode) check digit.

Input parameters:

- `code` (string, required): The barcode digits. e.g. 4006381333931

### `validate_batch` (~40 tokens)

Validate many identifiers

Validate up to 25 mixed identifiers (iban, bic, vat, card, isbn, gtin) in one call.

Input parameters:

- `items` (array, required)

### `stablecoin_peg_verdict` (~200 tokens)

Stablecoin peg verdict

Live peg-health verdict for USD stablecoins: PEGGED / WATCH / DEPEG_RISK / DEPEGGED, 0-100 risk score, price deviation in bps, 1d/7d/30d supply change and per-chain liquidity, computed from DefiLlama (cached 5 min). Free tier: 30 calls/hour per client; for unlimited use pay per call via x402 (USDC on Base, $0.005): https://identifier-validator-api.yuechenxi-importexport.workers.dev/x402/v1/stablecoin-peg. Informational only, not financial advice.

Input parameters:

- `asset` (string, required): USD stablecoin symbol, name, DefiLlama id or CoinGecko id, e.g. USDC. Up to 10 comma-separated.
- `chain` (string): Optional chain name (e.g. Base) to add on-chain supply/liquidity checks.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-yuechenxi-importexport-identifier-validator-api-identifier-validator/identifier-validator-api#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 64

## Common questions

### What is the Identifier Validator + Stablecoin Peg Verdict MCP server?

Identifier Validator + Stablecoin Peg Verdict is an MCP server listed in the public MCP registry as dev.workers.yuechenxi-importexport.identifier-validator-api…. Offline IBAN/BIC/EU VAT/card/ISBN/GTIN validators + live USD stablecoin peg-health verdict. This page covers its hosted endpoint (https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp).

### Is the Identifier Validator + Stablecoin Peg Verdict MCP server safe to use?

Identifier Validator + Stablecoin Peg Verdict scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Identifier Validator + Stablecoin Peg Verdict MCP server expose?

Identifier Validator + Stablecoin Peg Verdict exposes 8 tools: validate_iban, validate_bic, validate_vat, validate_card, validate_isbn, and 3 more. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.

### Does the Identifier Validator + Stablecoin Peg Verdict MCP server require authentication?

No. We connected to Identifier Validator + Stablecoin Peg Verdict without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Identifier Validator + Stablecoin Peg Verdict MCP server still maintained?

Identifier Validator + Stablecoin Peg Verdict is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp
- Website: https://identifier-validator-api.yuechenxi-importexport.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-yuechenxi-importexport-identifier-validator-api-identifier-validator/identifier-validator-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-yuechenxi-importexport-identifier-validator-api-identifier-validator/identifier-validator-api.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-yuechenxi-importexport-identifier-validator-api-identifier-validator/identifier-validator-api