io.github.freshfos/dropcoin-validation
REMOTE · VALIDATION-API.DROPCOIN.WORKERS.DEV · SCANNED SEP 28
EU compliance checks for AI agents: sanctions, company, VAT ID, IBAN, email. Pay per call.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 434 tokens (~72/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the io.github.freshfos/dropcoin-validation MCP server?
io.github.freshfos/dropcoin-validation is a hosted endpoint at https://validation-api.dropcoin.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 · validation-api.dropcoin.workers.dev
claude mcp add --transport http freshfos-dropcoin-validation 'https://validation-api.dropcoin.workers.dev/mcp'
{
"mcpServers": {
"freshfos-dropcoin-validation": {
"url": "https://validation-api.dropcoin.workers.dev/mcp"
}
}
} {
"servers": {
"freshfos-dropcoin-validation": {
"type": "http",
"url": "https://validation-api.dropcoin.workers.dev/mcp"
}
}
} [mcp_servers.freshfos-dropcoin-validation] url = "https://validation-api.dropcoin.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"freshfos-dropcoin-validation": {
"type": "remote",
"url": "https://validation-api.dropcoin.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add freshfos-dropcoin-validation --url 'https://validation-api.dropcoin.workers.dev/mcp' --transport streamable-http
mcp_servers:
freshfos-dropcoin-validation:
url: "https://validation-api.dropcoin.workers.dev/mcp" {
"McpServers": {
"freshfos-dropcoin-validation": {
"Transport": "http",
"Url": "https://validation-api.dropcoin.workers.dev/mcp"
}
}
} assistant mcp add freshfos-dropcoin-validation -t streamable-http -u 'https://validation-api.dropcoin.workers.dev/mcp'
{
"mcpServers": {
"freshfos-dropcoin-validation": {
"type": "http",
"url": "https://validation-api.dropcoin.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Sept 26 +1
- Stability: 0.97 → pass security
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 28 Sept 2026 · Probed https://validation-api.dropcoin.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=dropcoin.workers.dev | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | c4bdce5cae65bdde0e4473041ea36c40 |
| SANs: dropcoin.workers.dev, *.dropcoin.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of validation-api.dropcoin.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://validation-api.dropcoin.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://validation-api.dropcoin.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 →
screen_sanctions ~99
Screen a person or company against the official EU, US (OFAC SDN) and UK (OFSI) sanctions lists. Fuzzy name matching with an auditable reason per hit — review every hit yourself; a clean result is not legal clearance and covers no PEP data. 15 credits, requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| minScore | number | – | – |
| name | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
validate_email ~49
Validate an email address: syntax, disposable-domain check, MX record via DNS-over-HTTPS. Returns a deliverability verdict. 2 credits, requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
No output schema declared.
No examples provided.
validate_iban ~43
Validate an IBAN (ISO 13616 check digits) incl. SEPA membership. 2 credits, requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | – |
No output schema declared.
No examples provided.
validate_vatid ~62
Validate an EU VAT ID against the live VIES registry (format check first — an invalid format still costs the full price, it never reaches VIES but you got an answer). 5 credits, requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| vatId | string | yes | – |
No output schema declared.
No examples provided.
validate_vatid_format ~61
Free EU VAT-ID FORMAT check (syntax only, no registry lookup), rate-limited per IP, no API key needed. For a live VIES registry check use the paid validate_vatid tool (5 credits).
| Name | Type | Req | Description |
|---|---|---|---|
| vatId | string | yes | – |
No output schema declared.
No examples provided.
verify_company ~120
Verify a business partner in one call: EU VAT registration (VIES), LEI register (GLEIF), IBAN checksum and country consistency — one verdict (pass|fail|inconclusive) with an auditable check log. Provide at least one of name, vatId, lei. Does not include commercial-register existence checks. 150 credits, requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| iban | string | – | – |
| lei | string | – | – |
| name | string | – | – |
| vatId | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.freshfos/dropcoin-validation MCP server?
io.github.freshfos/dropcoin-validation is an MCP server listed in the public MCP registry as io.github.freshfos/dropcoin-validation. EU compliance checks for AI agents: sanctions, company, VAT ID, IBAN, email. Pay per call. This page covers its hosted endpoint (https://validation-api.dropcoin.workers.dev/mcp).
Is the io.github.freshfos/dropcoin-validation MCP server safe to use?
io.github.freshfos/dropcoin-validation scores 69 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 io.github.freshfos/dropcoin-validation MCP server expose?
io.github.freshfos/dropcoin-validation exposes 6 tools: validate_vatid_format, validate_email, validate_vatid, validate_iban, screen_sanctions, verify_company. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.
Does the io.github.freshfos/dropcoin-validation MCP server require authentication?
No. We connected to io.github.freshfos/dropcoin-validation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.freshfos/dropcoin-validation MCP server still maintained?
io.github.freshfos/dropcoin-validation is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.