Turkish IBAN, Tax Number & National ID Validation
REMOTE · FOSTER-MCP.ESAKIZ.WORKERS.DEV
Checksum validation of Turkish IBANs, tax numbers (VKN) and national IDs (TCKN). Nothing stored.
Available components
Last scanned (8 hours ago)
Scores higher than 58% 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 288 tokens (~96/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 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.
- 31 Oct 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.
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 68
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://foster-mcp.esakiz.workers.dev/validate/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=esakiz.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 689b10d79e7405d35f09f24110640f23ffa |
| SANs: *.esakiz.workers.dev, esakiz.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 foster-mcp.esakiz.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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://foster-mcp.esakiz.workers.dev/validate/mcp | Verified | 200 | |
| http (plaintext) | http://foster-mcp.esakiz.workers.dev/validate/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 →
validate_iban Validate a Turkish IBAN ~100
Validates a Turkish (TR) IBAN: 26 characters, structure, reserved digit and ISO 13616 mod-97 checksum. Returns the normalized and grouped form, the 5-digit bank code and the account number part. Format and checksum only: a valid result does not prove the number is registered or belongs to anyone. Inputs are not stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | IBAN; spaces and hyphens are ignored |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| formatted | string|null | yes | – |
| normalized | string | yes | – |
| note | string | yes | – |
| parts | – | yes | – |
| type | string | yes | – |
| valid | boolean | yes | – |
No examples provided.
validate_national_id Validate a Turkish national ID number (TCKN) ~109
Validates the check digits of an 11-digit Turkish national identity number (T.C. Kimlik Numarası, TCKN), which individuals also use as their tax number. The number is personal data: it is not echoed back. It does not confirm the person exists. Format and checksum only: a valid result does not prove the number is registered or belongs to anyone. Inputs are not stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| tckn | string | yes | 11-digit TCKN |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| note | string | yes | – |
| type | string | yes | – |
| valid | boolean | yes | – |
No examples provided.
validate_tax_number Validate a Turkish tax number (VKN) ~79
Validates the check digit of a 10-digit Turkish tax identification number (Vergi Kimlik Numarası, VKN) used by companies. Format and checksum only: a valid result does not prove the number is registered or belongs to anyone. Inputs are not stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| vkn | string | yes | 10-digit VKN |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| normalized | string | yes | – |
| note | string | yes | – |
| type | string | yes | – |
| valid | boolean | yes | – |
No examples provided.
How do I install the Turkish IBAN, Tax Number & National ID Validation MCP server?
Turkish IBAN, Tax Number & National ID Validation is a hosted endpoint at https://foster-mcp.esakiz.workers.dev/validate/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 · foster-mcp.esakiz.workers.dev
claude mcp add --transport http foster-ops-turkey-identifier-validation 'https://foster-mcp.esakiz.workers.dev/validate/mcp'
What is the Turkish IBAN, Tax Number & National ID Validation MCP server?
Turkish IBAN, Tax Number & National ID Validation is an MCP server listed in the public MCP registry as io.github.foster-ops/turkey-identifier-validation. Checksum validation of Turkish IBANs, tax numbers (VKN) and national IDs (TCKN). Nothing stored. This page covers its hosted endpoint (https://foster-mcp.esakiz.workers.dev/validate/mcp).
Is the Turkish IBAN, Tax Number & National ID Validation MCP server safe to use?
Turkish IBAN, Tax Number & National ID Validation scores 72 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 Turkish IBAN, Tax Number & National ID Validation MCP server expose?
Turkish IBAN, Tax Number & National ID Validation exposes 3 tools: validate_iban, validate_tax_number, validate_national_id. Their descriptions and schemas cost roughly 288 tokens of context every time the server is loaded.
Does the Turkish IBAN, Tax Number & National ID Validation MCP server require authentication?
No. We connected to Turkish IBAN, Tax Number & National ID Validation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Turkish IBAN, Tax Number & National ID Validation MCP server still maintained?
Turkish IBAN, Tax Number & National ID Validation 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.
What did VerifyMCP test on the Turkish IBAN, Tax Number & National ID Validation MCP server?
VerifyMCP ran 12 checks on Turkish IBAN, Tax Number & National ID Validation, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Turkish IBAN, Tax Number & National ID Validation: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.