CheckBiz Merchant Check
REMOTE · API.CHECKBIZ.EU
Let your shopping agent check the shop before it pays: a real, active, EU-registered company?
Available components
Last scanned (22 hours ago)
Scores higher than 82% of remote servers
Reachable. Last reached 23 Oct 2026.
Category E-commerce
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 Security77
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 316 tokens (~316/item across 1 items; 1 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 Management50
- Stability observed for 15 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 8 Oct 26 72
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 23 Oct 2026 · Probed https://api.checkbiz.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.checkbiz.eu | CN=YE1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a3e123597931c7c5e1fc1e9c7eff5740cb |
| SANs: api.checkbiz.eu | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 secure
Validation of api.checkbiz.eu. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| checkbiz.eu. | present | 13855 | 13 | Verified |
| api.checkbiz.eu. | Verified address RRset verified with the apex keys |
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://api.checkbiz.eu/mcp | Verified | 200 | |
| http (plaintext) | http://api.checkbiz.eu/mcp | HTTPS enforced | 301 | https://api.checkbiz.eu/mcp |
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 →
check_merchant Check a merchant before paying ~316
Check a web shop BEFORE paying it: is the shop on this domain a real, active, registered company in a European business register, and does the domain belong to that company? Reads the registration / VAT number the shop states on its own imprint, terms or footer, looks it up in the national register (Denmark, Sweden, Norway, Finland, UK, Germany and other EU countries), validates VAT in VIES/HMRC, screens the company against sanctions lists, and checks domain age, TLS certificate and a public phishing list. Returns match = verified | partial | not_found | attention with evidence per signal and the source of each field. Evidence, not a verdict — you decide. Pass vat_number (and country) from the checkout or invoice when you have it; it also catches a checkout VAT number that belongs to a different or ceased company. When the free monthly lookups run out, the result contains buy_url: show it to your user — one payment adds 150 lookups.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | Company name shown at checkout, if any |
| country | string | – | ISO country code of that number, e.g. "dk", "se", "uk" — helps read a bare number |
| domain | string | yes | The shop's domain or URL, e.g. "example-shop.dk" |
| vat_number | string | – | VAT or company registration number shown at checkout / on the invoice, e.g. "DK27528430" or "556710-4699" |
No output schema declared.
No examples provided.
How do I install the CheckBiz Merchant Check MCP server?
CheckBiz Merchant Check is a hosted endpoint at https://api.checkbiz.eu/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.checkbiz.eu
claude mcp add --transport http eu-checkbiz-merchant-check 'https://api.checkbiz.eu/mcp'
What is the CheckBiz Merchant Check MCP server?
CheckBiz Merchant Check is an MCP server listed in the public MCP registry as eu.checkbiz/merchant-check. Let your shopping agent check the shop before it pays: a real, active, EU-registered company? This page covers its hosted endpoint (https://api.checkbiz.eu/mcp).
Is the CheckBiz Merchant Check MCP server safe to use?
CheckBiz Merchant Check scores 79 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 CheckBiz Merchant Check MCP server expose?
CheckBiz Merchant Check exposes 1 tool: check_merchant. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.
Does the CheckBiz Merchant Check MCP server require authentication?
No. We connected to CheckBiz Merchant Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CheckBiz Merchant Check MCP server still maintained?
CheckBiz Merchant Check is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.