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.

Cutlab: CNC cutting, ships across Europe

REMOTE · AGENT.CUTLAB.EE

CNC cutting workshop in Estonia shipping across Europe: capabilities, quote estimate, RFQ.

Available components

+4 this week 68 Trust /100

Last scanned (15 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category IoT and Hardware

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 Security74
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 975 tokens (~325/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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

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

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.

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

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 64

    First indexed and scored.

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://agent.cutlab.ee/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cutlab.ee CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 a65c091195af157a0e5d8cf59740bc36
SANs: cutlab.ee, agent.cutlab.ee, *.agent.cutlab.ee
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 agent.cutlab.ee. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ee. DS published 34382 8 Verified
cutlab.ee. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent.cutlab.ee/mcp Verified 200
http (plaintext) http://agent.cutlab.ee/mcp HTTPS enforced 301 https://agent.cutlab.ee/mcp
MCP tools · 3 exposed · ~699 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
estimate_quote ~193

Preliminary price range in EUR excl. VAT for cutting simple rectangular parts from sheet material, from public rates. Rectangles only; shaped parts need submit_rfq. Pass destination_country (ISO code, for example DK) for shipments outside Estonia: the 150 EUR minimum order then applies. The result is a range, not an offer; material is not included. Limit: 30 calls per hour per IP.

NameTypeReqDescription
destination_countrystring–Delivery country, ISO 3166-1 alpha-2, for example DK or DE. Outside Estonia the 150 EUR minimum order applies; omit or use EE for Estonia
langstring––
materialstring––
partsarrayyes–
sheetobject–Optional sheet size, default 1250 x 2500 mm, at most 2070 x 4000 mm
thickness_mmnumber––

No output schema declared.

No examples provided.

get_capabilities ~68

Facts about Cutlab, a CNC workshop in Estonia shipping across Europe: delivery countries and transit times, machine and work area, materials, tolerances, public rates, minimum order (100 EUR in Estonia, 150 EUR outside Estonia), lead time, VAT rules and file formats. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_rfq ~438

Send a request for quotation to Cutlab on behalf of a customer in Estonia or anywhere in Europe. Not an order. Requires the customer's e-mail (contact_email), a description of at least 20 characters and customer_consent_to_contact = true. Files: public https links in file_links, or upload them after this call to the upload_url from the result (give the link to the customer: a browser page with drag and drop; or send each file with PUT {upload_url}/{filename} and the raw file as the body). Up to 10 files, 50 MB each: DXF, DWG, STEP/STP, PDF, AI, SVG, CDR, F3D, STL, 3MF, JPG/JPEG, PNG; the link is valid 7 days. POST {upload_url}/done after the last file (optional): notifies Cutlab at once; without it the notification is sent automatically about 2 minutes after the last file. Cutlab replies to the customer by e-mail, usually within 1–2 working days. Limit: 10 requests per day per IP.

NameTypeReqDescription
agentobject––
companystring––
contact_emailstringyesCustomer e-mail for confirmation (required)
contact_namestring––
countrystring–Customer country, ISO 3166-1 alpha-2, for example DK; customers from any country can send a request
customer_consent_to_contactbooleanyesThe customer agrees to be contacted by e-mail about this request
customer_typestring––
deadlinestring––
descriptionstringyes–
file_linksarray–Public https links to drawings or models. To send files without a public link, upload them to the upload_url returned in the response.
idempotency_keystring–Optional key that makes a retry safe: the same key never creates a second request
languagestring––
materialstring––
partsarray––
quantitystring––

No output schema declared.

No examples provided.

Install

How do I install the Cutlab: CNC cutting, ships across Europe MCP server?

Cutlab: CNC cutting, ships across Europe is a hosted endpoint at https://agent.cutlab.ee/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 · agent.cutlab.ee

# add to Claude Code
claude mcp add --transport http ee-cutlab-cnc 'https://agent.cutlab.ee/mcp'
Common questions

What is the Cutlab: CNC cutting, ships across Europe MCP server?

Cutlab: CNC cutting, ships across Europe is an MCP server listed in the public MCP registry as ee.cutlab/cnc. CNC cutting workshop in Estonia shipping across Europe: capabilities, quote estimate, RFQ. This page covers its hosted endpoint (https://agent.cutlab.ee/mcp).

Is the Cutlab: CNC cutting, ships across Europe MCP server safe to use?

Cutlab: CNC cutting, ships across Europe scores 68 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 Cutlab: CNC cutting, ships across Europe MCP server expose?

Cutlab: CNC cutting, ships across Europe exposes 3 tools: get_capabilities, estimate_quote, submit_rfq. Their descriptions and schemas cost roughly 699 tokens of context every time the server is loaded.

Does the Cutlab: CNC cutting, ships across Europe MCP server require authentication?

No. We connected to Cutlab: CNC cutting, ships across Europe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Cutlab: CNC cutting, ships across Europe MCP server still maintained?

Cutlab: CNC cutting, ships across Europe 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 Cutlab: CNC cutting, ships across Europe MCP server?

VerifyMCP ran 13 checks on Cutlab: CNC cutting, ships across Europe, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.