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.
Available components
Last scanned (1 hour ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 661 tokens (~82/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yuechenxi-importexport.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 628bf169dff846de1a310ac8e61d46532db |
| SANs: *.yuechenxi-importexport.workers.dev, yuechenxi-importexport.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of identifier-validator-api.yuechenxi-importexport.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
stablecoin_peg_verdict Stablecoin peg verdict ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | 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. |
No output schema declared.
No examples provided.
validate_batch Validate many identifiers ~40
Validate up to 25 mixed identifiers (iban, bic, vat, card, isbn, gtin) in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
validate_bic Validate BIC/SWIFT ~54
Validate a BIC/SWIFT code structure (8 or 11 chars), country, location and branch code.
| Name | Type | Req | Description |
|---|---|---|---|
| bic | string | yes | The BIC/SWIFT code. e.g. DEUTDEFF |
No output schema declared.
No examples provided.
validate_card Validate payment card number ~71
Luhn check and network detection (Visa, Mastercard, Amex, Discover, Diners, JCB, UnionPay, Maestro, Mir). Returns masked output only; nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The card number (use test numbers). e.g. 4111111111111111 |
No output schema declared.
No examples provided.
validate_gtin Validate GTIN/EAN/UPC ~49
Validate GTIN-8/12/13/14 (EAN/UPC barcode) check digit.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The barcode digits. e.g. 4006381333931 |
No output schema declared.
No examples provided.
validate_iban Validate IBAN ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | The IBAN, spaces allowed. e.g. DE89370400440532013000 |
No output schema declared.
No examples provided.
validate_isbn Validate ISBN ~44
Validate ISBN-10 or ISBN-13 check digit and convert between the two.
| Name | Type | Req | Description |
|---|---|---|---|
| isbn | string | yes | The ISBN. e.g. 9780306406157 |
No output schema declared.
No examples provided.
validate_vat Validate EU VAT number ~81
Validate an EU/EEA (plus GB, NO, CH and more) VAT number format and checksum offline. Does not check VIES registration status.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO country code if the number has no prefix. |
| vat | string | yes | The VAT number, with or without country prefix. e.g. DE811569869 |
No output schema declared.
No examples provided.
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.
remote · identifier-validator-api.yuechenxi-importexport.workers.dev
claude mcp add --transport http dev-workers-yuechenxi-importexport-identifier-va 'https://identifier-validator-api.yuechenxi-importexport.workers.dev/mcp'
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.