Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WinkelFactuur

REMOTE · API.WINKELFACTUUR.NL · SCANNED SEP 24

Free EU VAT, IBAN and bol.com commission tools for marketplace sellers

+4 this week 78 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 682 tokens (~227/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 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
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the WinkelFactuur MCP server?

WinkelFactuur is a hosted endpoint at https://api.winkelfactuur.nl/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 · api.winkelfactuur.nl

# add to Claude Code
claude mcp add --transport http nl-winkelfactuur-tools 'https://api.winkelfactuur.nl/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "nl-winkelfactuur-tools": {
      "url": "https://api.winkelfactuur.nl/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nl-winkelfactuur-tools": {
      "type": "http",
      "url": "https://api.winkelfactuur.nl/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nl-winkelfactuur-tools]
url = "https://api.winkelfactuur.nl/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nl-winkelfactuur-tools": {
      "type": "remote",
      "url": "https://api.winkelfactuur.nl/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nl-winkelfactuur-tools --url 'https://api.winkelfactuur.nl/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nl-winkelfactuur-tools:
    url: "https://api.winkelfactuur.nl/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nl-winkelfactuur-tools": {
      "Transport": "http",
      "Url": "https://api.winkelfactuur.nl/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nl-winkelfactuur-tools -t streamable-http -u 'https://api.winkelfactuur.nl/mcp'
// mcp.json
{
  "mcpServers": {
    "nl-winkelfactuur-tools": {
      "type": "http",
      "url": "https://api.winkelfactuur.nl/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 24 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.

  • 22 Sept 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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 24 Sept 2026 · Probed https://api.winkelfactuur.nl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=winkelfactuur.nl CN=WE1,O=Google Trust Services,C=US 20 Aug 2026 18 Nov 2026 ECDSA 256 ECDSA-SHA256 36f6a72a17b8d2f8138a350ec5e178be
SANs: winkelfactuur.nl, *.winkelfactuur.nl
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 api.winkelfactuur.nl. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
nl. present 17153 13 Verified
winkelfactuur.nl. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.winkelfactuur.nl/mcp Verified 200
http (plaintext) http://api.winkelfactuur.nl/mcp HTTPS enforced 301 https://api.winkelfactuur.nl/mcp
MCP tools · 3 exposed · ~563 tokens

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 →

Tool Tokens
bol_commission ~206

Work out what bol.com keeps from a sale: the commission percentage for the product category, any fixed fee, and what the seller is left with. Category names are the Dutch ones bol.com uses ("Elektronica", "Boeken", "Speelgoed"). If the category is unknown or missing, the tool returns the list of categories it knows, so call it again with one of those.

NameTypeReqDescription
categorystringyesbol.com main category, in Dutch. For example: Elektronica, Boeken, Speelgoed, Wonen & Koken.
fulfilment_typestring–lvb for Logistiek via bol, fbr when the seller ships. Leave out if it does not matter.
pricenumberyesSelling price in euros, including VAT, as shown to the buyer.
subcategorystring–Subcategory when the main one splits by rate, e.g. Telefoons or Televisies under Elektronica.

No output schema declared.

No examples provided.

calculate_vat ~257

Calculate EU VAT (Dutch: BTW) for a cross-border or domestic sale, using the destination-country principle that applies to e-commerce. Handles the cases sellers get wrong: OSS distance selling to another EU country, B2B reverse charge when the buyer has a VIES-valid VAT number, and zero-rated exports outside the EU. Rates are the statutory ones for the destination country, including reduced rates when a category is given.

NameTypeReqDescription
amountnumberyesNet amount (excluding VAT) in euros.
categorystring–Optional product category, used to find a reduced rate (books, food, medicine and similar).
customer_countrystringyesTwo-letter country code the goods are shipped to, e.g. NL, DE, FR. This is what determines the rate.
customer_vat_numberstring–Buyer VAT number. Required for B2B reverse charge; it is checked against VIES, so an invented number will not zero the VAT.
is_businessboolean–True when the buyer is a business (B2B). Reverse charge also needs a valid VAT number.
seller_countrystring–Two-letter country code the seller is established in. Defaults to NL.

No output schema declared.

No examples provided.

validate_iban ~100

Validate an IBAN (bank account number) and report whether its check digits and country-specific length are correct. Catches transposed or missing digits before a payment or an invoice goes out with the wrong account number. This checks the number's structure, not whether the account exists or who owns it.

NameTypeReqDescription
ibanstringyesThe IBAN to check. Spaces, dots and dashes are ignored, so it can be pasted as printed.

No output schema declared.

No examples provided.

Common questions

What is the WinkelFactuur MCP server?

WinkelFactuur is an MCP server listed in the public MCP registry as nl.winkelfactuur/tools. Free EU VAT, IBAN and bol.com commission tools for marketplace sellers. This page covers its hosted endpoint (https://api.winkelfactuur.nl/mcp).

Is the WinkelFactuur MCP server safe to use?

WinkelFactuur scores 78 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 WinkelFactuur MCP server expose?

WinkelFactuur exposes 3 tools: calculate_vat, validate_iban, bol_commission. Their descriptions and schemas cost roughly 563 tokens of context every time the server is loaded.

Does the WinkelFactuur MCP server require authentication?

No. We connected to WinkelFactuur without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the WinkelFactuur MCP server still maintained?

WinkelFactuur is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.