docks Produktberatung
REMOTE · AGENT.DOCKS.IO
Maschinendokumentation per QR-Code (EU-MVO 2023/1230): belegte Fakten prüfen, Pilotanfrage stellen.
Available components
Last scanned (18 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 22 Oct 2026.
Category CRM and Sales
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. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 355 tokens (~59/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 21 Oct 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.
- 18 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 66
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 22 Oct 2026 · Probed https://agent.docks.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sales.ecompanion.io | CN=YE1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 54be391fb8a475de0955cb1ec1bd36cf922 |
| SANs: agent.docks.io, sales.ecompanion.io | ||||||
| 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 insecure
Validation of agent.docks.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| docks.io. | 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 |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; font-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| 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://agent.docks.io/mcp | Verified | 200 | |
| http (plaintext) | http://agent.docks.io/mcp | HTTPS enforced | 301 | https://agent.docks.io/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 →
assess_requirements ~48
Check buyer requirements against evidence. Returns met, unmet or unknown and questions for the buyer. Does not create a lead.
| Name | Type | Req | Description |
|---|---|---|---|
| offeringId | string | yes | – |
| requirements | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_inquiry_status ~48
Read only this inquiry using its private access capability. A pending handover is not delivered. Cannot read other inquiries.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | – |
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product_information ~38
Read sourced docks capabilities, limits and links. Unknown integrations and prices must be clarified; never infer guarantees.
| Name | Type | Req | Description |
|---|---|---|---|
| offeringId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
prepare_inquiry ~121
Prepare a private inquiry draft only when the buyer wants to contact docks. Return the reviewUrl to the buyer for review and explicit submission in their browser. Do not open or approve it on their behalf. Keep accessToken private. Drafts are not handed to sales.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| contactName | string | yes | – |
| details | object | – | – |
| string | yes | – | |
| offeringId | string | yes | – |
| requirements | array | – | – |
| role | string | – | – |
| useCase | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_offerings ~41
Find relevant offers of docks. This is vendor information from docks only, not an independent market comparison. No lead is created.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
submit_inquiry ~59
Retrieve the submission receipt after the buyer has approved the review page. An unconfirmed draft is rejected. Repeated calls cannot create duplicate leads.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | – |
| id | string | yes | – |
| revision | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the docks Produktberatung MCP server?
docks Produktberatung is a hosted endpoint at https://agent.docks.io/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.docks.io
claude mcp add --transport http io-docks-agent 'https://agent.docks.io/mcp'
What is the docks Produktberatung MCP server?
docks Produktberatung is an MCP server listed in the public MCP registry as io.docks/agent. Maschinendokumentation per QR-Code (EU-MVO 2023/1230): belegte Fakten prüfen, Pilotanfrage stellen. This page covers its hosted endpoint (https://agent.docks.io/mcp).
Is the docks Produktberatung MCP server safe to use?
docks Produktberatung 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 docks Produktberatung MCP server expose?
docks Produktberatung exposes 6 tools: search_offerings, get_product_information, assess_requirements, prepare_inquiry, submit_inquiry, get_inquiry_status. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.
Does the docks Produktberatung MCP server require authentication?
No. We connected to docks Produktberatung without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the docks Produktberatung MCP server still maintained?
docks Produktberatung is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.