Skip to content

dropcoin-validation MCP server

io.github.freshfos/dropcoin-validationfreshfosstreamable-httpv1.0.0Scanned

EU compliance checks for AI agents: sanctions, company, VAT ID, IBAN, email. Pay per call.

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the dropcoin-validation MCP server can do

The dropcoin-validation MCP server is published by the GitHub account freshfos. It has 6 tools. It can create or change data (2 tools: screen_sanctions and verify_company), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • screen_sanctionsScreen a person or company against the official EU, US (OFAC SDN) and UK (OFSI) sanctions lists.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • verify_companyVerify 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 audita…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • validate_emailValidate an email address: syntax, disposable-domain check, MX record via DNS-over-HTTPS.No findings

    Why it is in this group

    • The name "validate_email" says "validate": a word for reading.
    Description, as the server wrote it
    Validate an email address: syntax, disposable-domain check, MX record via DNS-over-HTTPS. Returns a deliverability verdict. 2 credits, requires an API key.
  • validate_ibanValidate an IBAN (ISO 13616 check digits) incl.No findings

    Why it is in this group

    • The name "validate_iban" says "validate": a word for reading.
    Description, as the server wrote it
    Validate an IBAN (ISO 13616 check digits) incl. SEPA membership. 2 credits, requires an API key.
  • validate_vatidValidate 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).No findings

    Why it is in this group

    • The name "validate_vatid" says "validate": a word for reading.
    Description, as the server wrote it
    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.
  • validate_vatid_formatFree EU VAT-ID FORMAT check (syntax only, no registry lookup), rate-limited per IP, no API key needed.No findings

    Why it is in this group

    • The name "validate_vatid_format" says "validate": a word for reading.
    Description, as the server wrote it
    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).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://validation-api.dropcoin.workers.dev/mcp: tools/list returned 6 tools to an anonymous client, including screen_sanctions (write), verify_company (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dropcoin-validation https://validation-api.dropcoin.workers.dev/mcp
claude mcp add --transport http dropcoin-validation https://validation-api.dropcoin.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dropcoin-validation__validate_vatid_format",
      "mcp__dropcoin-validation__validate_email",
      "mcp__dropcoin-validation__validate_vatid",
      "mcp__dropcoin-validation__validate_iban"
    ],
    "ask": [
      "mcp__dropcoin-validation__screen_sanctions",
      "mcp__dropcoin-validation__verify_company"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dropcoin-validation. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.freshfos/dropcoin-validation/verify?hash=05211ace1ce94e5d3d099b724c3dec824beabc7c107c363182bdf7584b21addc" | jq -e '.changed == false'

Pinned hash 05211ace1ce9, from Nov 21, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.freshfos/dropcoin-validation/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.freshfos/dropcoin-validation
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.freshfos/dropcoin-validation.svg)](https://radar.anlyon.com/servers/io.github.freshfos/dropcoin-validation)

Source: MCP Registry. Synced Oct 21, 2026, 18:34 UTC.

dropcoin-validation MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the dropcoin-validation MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the dropcoin-validation MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the dropcoin-validation MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the dropcoin-validation MCP server have?

6 tools: 2 write, 4 read. screen_sanctions, verify_company, validate_vatid_format, validate_email, validate_vatid and validate_iban.

Does the dropcoin-validation MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the dropcoin-validation MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the dropcoin-validation MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.