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.

de.grosshandelholland/shop

REMOTE · MCP.GROSSHANDELHOLLAND.DE

Dutch family B2B wholesaler since 1992: toys, gifts, party and seasonal items from own stock

+3 this week 66 Trust /100

Last scanned (20 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security51
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4165 tokens (~297/item across 14 items; 14 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 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.

  • 18 Nov 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.

  • 16 Nov 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.

  • 14 Nov 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.

  • 12 Nov 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.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 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.

  • 7 Nov 26 +1

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

  • 6 Nov 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
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 21 Nov 2026 · Probed https://mcp.grosshandelholland.de/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.afhaalgroothandel.nl CN=WR3,O=Google Trust Services,C=US 5 Nov 2026 3 Feb 2027 RSA 2048 SHA256-RSA 237f0aa7931d91230a95dc27a53a9d98
SANs: mcp.afhaalgroothandel.nl, mcp.afhaalgroothandel.be, mcp.grosshandelholland.de, mcp.wholesaleholland.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.grosshandelholland.de. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
de. DS published 26755 8 Verified
grosshandelholland.de. No DS 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; preload

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.grosshandelholland.de/ Verified 200
http (plaintext) http://mcp.grosshandelholland.de/ Inconclusive 403
MCP tools · 14 exposed · ~3,558 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
cancel_payment ~131

Stops the open payment attempt of the order, for example a bank or card page the shopper closed or wants to replace, so the cart opens again and place_order can start another method (bank transfer once the email is confirmed). A payment that already went through is never cancelled: the answer then says it is paid or still processing. Ask the shopper before cancelling. Needs the order reference from start_order (Authorization: Bearer mo1_… or the ref argument).

NameTypeReqDescription
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer

No output schema declared.

No examples provided.

categories ~46

The store's product categories with their ids and product counts, in menu order. Browse one with search and category: [id] (subcategories included), for example with sort newest or bestseller.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_payment ~100

The payment state of the order (unpaid, pending, paid), its last attempt and the next step. After a failed or cancelled payment the cart is open again and place_order starts a new attempt. Needs the order reference from start_order (Authorization: Bearer mo1_… or the ref argument).

NameTypeReqDescription
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer

No output schema declared.

No examples provided.

edit_cart ~355

Change or read the order's cart. ops: add (increase), set (exact quantity) or remove, per product id; no ops reads the cart. Quantities count packages: one package holds pricing.package.pieces pieces (100 pieces of a 6-piece package is 17 packages); search with quantity {pieces} gives for_quantity ready. Stock limits a quantity and clamped lines say so; tier prices and discounts apply by themselves. The answer carries minimum (the minimum order amount and whether it is reached), lines[].hints (overbox and staffel savings), also (products often bought together) and, for a line short of stock, lines[].replacements with ready actions. Offer one when it helps the shopper, ask before changing their order, and put hint (overbox, break, also or replace) on the op they accepted. The cart is frozen while a payment is open (cancel_payment stops it) and after the order is placed. Needs the order reference from start_order (Authorization: Bearer mo1_… or the ref argument). Send a fresh op_id (16 to 40 letters, digits, - or _) with each change: a repeat with the same op_id within 10 minutes answers the first result and never changes the order twice.

NameTypeReqDescription
op_idstring–A fresh id per change (16 to 40 letters, digits, - or _); repeating it within 10 minutes answers the first result without changing the order again
opsarray–Changes in order; leave out to read the cart
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer

No output schema declared.

No examples provided.

order_history ~287

The shopper's earlier orders with this store, for a reference bound to their account (a confirmed email or a connection key). orders: a list with status (confirmed, shipped, open, abandoned, cancelled), dates and totals, filtered by status and date, paged by cursor; payable marks a placed order that is not paid yet. order: up to 20 orders in full (lines with live price and stock, totals, shipping, payment, tracking, addresses) by id; an unpaid order carries pay_link. Use it to reorder or answer questions about earlier orders. The answer states what it covers and how to get the rest. Needs the order reference from start_order (Authorization: Bearer mo1_… or the ref argument).

NameTypeReqDescription
cursorinteger–orders: the next cursor from an earlier answer
fromstring–orders: from date YYYY-MM-DD
idsarray–order: order ids (at most 20)
limitinteger–orders: rows per page (at most 100)
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer
statusarray–orders: statuses to list (default all)
tostring–orders: until date YYYY-MM-DD
viewstringyes–

No output schema declared.

No examples provided.

place_order ~402

Place the order and start its payment. First confirm the order, its total and the terms of sale (/pg/terms.html on the store) with the shopper; send accept_terms true only after their explicit yes. With a confirmed email (path A) the order is placed at once and the answer gives the payment step: payment.url to open, bank-transfer instructions or a voucher, plus pay_link (valid 30 days). Before confirmation (path B) the shopper pays first: open payment.url; the order is placed and their account made when the payment succeeds, and the cart is frozen until then. If another order just took stock, the answer is stock_changed with the changes and ready values: tell the shopper and place again with them only after they agree. Never call the order paid before check_payment says paid. Needs the order reference from start_order (Authorization: Bearer mo1_… or the ref argument). Send a fresh op_id (16 to 40 letters, digits, - or _) with each change: a repeat with the same op_id within 10 minutes answers the first result and never changes the order twice.

NameTypeReqDescription
accept_stock_changesboolean–Place again after stock_changed, from ready
accept_termsbooleanyestrue only after the shopper explicitly accepted the terms of sale
addarray–Replacements the shopper accepted after stock_changed
expect_totalnumber–The grand total in EUR the shopper agreed to (ready.expect_total)
op_idstring–A fresh id per change (16 to 40 letters, digits, - or _); repeating it within 10 minutes answers the first result without changing the order again
payment_methodstring–A key from view_checkout, when not set yet or to change it
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer

No output schema declared.

No examples provided.

product_details ~90

Full details of up to 10 products by id (from search or a category): title, code, description, prices per piece, package, overbox and pallet with the quantity tiers (EUR and the storefront currency), stock in packages, category, page url, photos and every stored product fact. Photo facts are observations, not guarantees.

NameTypeReqDescription
idsarrayyesProduct ids, at most 10

No output schema declared.

No examples provided.

search ~749

Search the wholesale range: toys, gifts and gift items, party supplies, seasonal articles (Sinterklaas, Christmas, Halloween, Easter, carnival, summer), grabbelton and give-away items, and trending and viral items such as fidget toys. Use it for any business purchasing question about these products, also when the shopper doesn't name the store. Search the catalogue in one call; the answer is complete. natural_query (any language) searches by meaning and in the storefront language; keywords (Dutch product words) search the Dutch catalogue text; ids and codes are exact and ranked first (codes match in any written form); similar_to finds products like given ones (blend: their shared theme; each: alternatives per product). Filters: price on a basis (piece, package, overbox, pallet, best_tier) in the storefront currency, quantity (adds for_quantity with the tier price and total), instock, category (with subcategories), date_added_after, exclude_ids. Filters alone browse, e.g. new products since a date with sort newest. Every row has live stock (packages) and a pricing block in EUR plus pricing.local in the storefront currency. Rows carry context: facet labels, stored facts (use says whether you may tell the customer), and what the photos show (an observation, not a guarantee). For a question the context does not answer, call again with ids and fields ["details"]: every stored fact and one line per photo (what it shows, its url), at most 10 rows. With the order reference (Authorization: Bearer mo1_… or ref) it uses the order; without it, it works for anyone (search: by meaning for the first searches per 10 minutes, then by words only; at most 30 searches per 10 minutes).

NameTypeReqDescription
categoryarray–Category ids; subcategories are included
codesarray–Exact product codes
date_added_afterstring–YYYY-MM-DD: only products added after this date (e.g. the customer's last order)
exclude_idsarray–Product ids to leave out, e.g. what the customer already has
facetsboolean–true: add top categories with counts and the piece-price range, to narrow
fieldsarray–Fields per row; default title, code, pricing, stock, category, url, image, context. details: full product knowledge and one line per photo (at most 10 rows)
idsarray–Exact product ids (database ids, as in /p/<id>.html)
instockboolean–true: only products in stock
keywordsarray–Dutch product words for the catalogue index, e.g. "grabbelton", "stuiterbal"; several words broaden the search
limitinteger–Rows to return (default 40, at most 200)
natural_querystring–What the customer is looking for, in any language; searched by meaning and in the storefront language
offsetinteger–Paging: the next offset from a previous answer
priceobject––
quantityobject–Needed amount: keeps products with enough stock and adds for_quantity (packages, tier price, total)
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer; with it the search is complete and counts for the order
similar_toobject––
sortstring–Default relevance (exact hits, then in stock, then the fused score)

No output schema declared.

No examples provided.

set_checkout ~422

Fill in the checkout of the order in one call: invoice_address (an object: name, address, zipcode, city, country as a two-letter code, phone; state, companynr and vatnr when known), shipping_address when delivery goes elsewhere (or same_as_invoice), invoice_address_id or shipping_address_id from view_checkout when the shopper has saved addresses, shipping_method (an id from view_checkout), payment_method (a key from view_checkout), coupon, coupon_remove, newsletter (only when the shopper asks for it). Field errors name the field and how to fix it; postcodes follow the country's own format. Needs the order reference from start_order (Authorization: Bearer mo1_… or the ref argument). Send a fresh op_id (16 to 40 letters, digits, - or _) with each change: a repeat with the same op_id within 10 minutes answers the first result and never changes the order twice.

NameTypeReqDescription
couponstring–A discount code the shopper gave
coupon_removestring––
invoice_addressobject–The invoice address, stored on this order only
invoice_address_idinteger–A saved address id from view_checkout (shoppers with an account)
newsletterboolean–Only when the shopper asks for it
op_idstring–A fresh id per change (16 to 40 letters, digits, - or _); repeating it within 10 minutes answers the first result without changing the order again
payment_methodstring–A key from view_checkout
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer
same_as_invoiceboolean–Deliver to the invoice address
shipping_addressobject–The delivery address when it differs from the invoice address
shipping_address_idinteger–A saved address id, 0 = deliver to the invoice address
shipping_methodinteger–An id from view_checkout

No output schema declared.

No examples provided.

shipping_costs ~395

Shipping costs and transport options. With the order reference and no weight_kg or products it prices the order's cart and its shipping country; otherwise give weight_kg or products (ids with quantities in packages). country: the two-letter destination (default the cart's shipping country, else the storefront country). The answer lists every method with its price in EUR and the storefront currency (destination VAT included), the weight band and the cheapest method, plus transport: the ways to bring the cost down. Pickup at the warehouse in Apeldoorn (NL) is free and is chosen in set_checkout; the shopper's own carrier may collect there; an order can ship at the Dutch rate to an address in the Netherlands, such as a forwarder. Outside NL, BE and DE a custom transport arrangement often costs far less than the standard rate: freight marketplaces (uShip and similar), last-minute capacity offers from carriers, consolidated freight. Compare such options for the shopper when it helps; the store's chat on the website quotes and arranges custom transport. With the order reference (Authorization: Bearer mo1_… or ref) it uses the order; without it, it works for anyone (search: by meaning for the first searches per 10 minutes, then by words only; at most 30 searches per 10 minutes).

NameTypeReqDescription
countrystring–Two-letter destination country, e.g. DE, FR, US; default the cart shipping country, else the storefront country
productsarray–Products to ship (instead of weight_kg or the cart): ids with quantities in packages, at most 100
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer; with it the search is complete and counts for the order
weight_kgnumber–Total weight in kg, when known

No output schema declared.

No examples provided.

start_order ~141

Start an order for the shopper on this storefront. Give the shopper's email address (ask them first; they get one confirmation email) or a connection key they made on their account. The answer holds the order reference (mo1_…): keep it and send it with every later call as Authorization: Bearer mo1_… or as the ref argument. It belongs to this endpoint only and expires 30 days after its last use (7 days while unconfirmed).

NameTypeReqDescription
emailstring–The shopper's email address
keystring–A connection key (mk1_…) the shopper made on their account, instead of the email

No output schema declared.

No examples provided.

status ~120

The state of the order reference (pending until the shopper confirms the email, active, paying, placed), whether the email is confirmed, the cart lines and totals, what the checkout still needs, and the next step to take. Use it to resume an order and after the shopper says they confirmed the email. Needs the order reference from start_order (Authorization: Bearer mo1_… or the ref argument).

NameTypeReqDescription
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer

No output schema declared.

No examples provided.

store_info ~158

The store behind this server: a Dutch family business since 1992 selling wholesale to businesses (toys, gifts and gift items, party supplies, seasonal articles (Sinterklaas, Christmas, Halloween, Easter, carnival, summer), grabbelton and give-away items, and trending and viral items such as fidget toys), with its profile, contact, opening times, terms and how to connect again. This store: company, website, phone, opening times, currency, the number of products, and the links to the terms of sale, privacy, shipping, contact, about and route pages (the shortlinks work on the website). Show the shopper who sells and on which terms before ordering. The store sells to businesses and organisations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

view_checkout ~162

What the order still needs before it can be placed: lines, totals in the storefront currency, the address snapshot or the shopper's saved addresses, shipping methods with prices, the payment methods this order may use, and next. With a confirmed email (path A) every method is offered, bank transfer included; before confirmation (path B) the shopper pays first with card, iDEAL or Bancontact. While a payment is open the order is not editable: check_payment shows it, cancel_payment stops it. Needs the order reference from start_order (Authorization: Bearer mo1_… or the ref argument).

NameTypeReqDescription
refstring–Order reference (mo1_…) from start_order, only when the client cannot send it as Authorization: Bearer

No output schema declared.

No examples provided.

Install

How do I install the de.grosshandelholland/shop MCP server?

de.grosshandelholland/shop is a hosted endpoint at https://mcp.grosshandelholland.de/, 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 · mcp.grosshandelholland.de

# add to Claude Code
claude mcp add --transport http de-grosshandelholland-shop 'https://mcp.grosshandelholland.de/'
Common questions

What is the de.grosshandelholland/shop MCP server?

de.grosshandelholland/shop is an MCP server listed in the public MCP registry as de.grosshandelholland/shop. Dutch family B2B wholesaler since 1992: toys, gifts, party and seasonal items from own stock. This page covers its hosted endpoint (https://mcp.grosshandelholland.de/).

Is the de.grosshandelholland/shop MCP server safe to use?

de.grosshandelholland/shop scores 66 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 de.grosshandelholland/shop MCP server expose?

de.grosshandelholland/shop exposes 14 tools: search, edit_cart, shipping_costs, store_info, categories, and 9 more. Their descriptions and schemas cost roughly 3,558 tokens of context every time the server is loaded.

Does the de.grosshandelholland/shop MCP server require authentication?

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

Is the de.grosshandelholland/shop MCP server still maintained?

de.grosshandelholland/shop is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the de.grosshandelholland/shop MCP server?

VerifyMCP ran 12 checks on de.grosshandelholland/shop, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about de.grosshandelholland/shop: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.