io.github.freshfos/dropcoin-validation
REMOTE · VALIDATION-API.DROPCOIN.WORKERS.DEV · SCANNED AUG 9
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 →
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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · validation-api.dropcoin.workers.dev
claude mcp add --transport http freshfos-dropcoin-validation 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": {
"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.
- 8 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Aug 26 52
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 9 Aug 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 |
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 |
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.
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.