Skip to content

docks Produktberatung MCP server

io.docks/agentdocks.iostreamable-httpv1.0.0Scanned

Maschinendokumentation per QR-Code (EU-MVO 2023/1230): belegte Fakten prüfen, Pilotanfrage stellen.

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the docks Produktberatung MCP server can do

The docks Produktberatung MCP server is published by docks.io, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: assess_requirements, prepare_inquiry and submit_inquiry), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • assess_requirementsCheck buyer requirements against evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check buyer requirements against evidence. Returns met, unmet or unknown and questions for the buyer. Does not create a lead.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • prepare_inquiryPrepare a private inquiry draft only when the buyer wants to contact docks.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • submit_inquiryRetrieve the submission receipt after the buyer has approved the review page.1 finding

    Why it is in this group

    • The name "submit_inquiry" says "submit": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "submit_inquiry" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "submit_inquiry" says "submit": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Retrieve the submission receipt after the buyer has approved the review page. An unconfirmed draft is rejected. Repeated calls cannot create duplicate leads.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_inquiry_statusRead only this inquiry using its private access capability.No findings

    Why it is in this group

    • The name "get_inquiry_status" says "get": a word for reading.
    Description, as the server wrote it
    Read only this inquiry using its private access capability. A pending handover is not delivered. Cannot read other inquiries.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_product_informationRead sourced docks capabilities, limits and links.No findings

    Why it is in this group

    • The name "get_product_information" says "get": a word for reading.
    Description, as the server wrote it
    Read sourced docks capabilities, limits and links. Unknown integrations and prices must be clarified; never infer guarantees.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_offeringsFind relevant offers of docks.No findings

    Why it is in this group

    • The name "search_offerings" says "search": a word for reading.
    Description, as the server wrote it
    Find relevant offers of docks. This is vendor information from docks only, not an independent market comparison. No lead is created.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:55 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agent.docks.io/mcp: tools/list returned 6 tools to an anonymous client, including assess_requirements (write), prepare_inquiry (write), submit_inquiry (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "submit_inquiry" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "submit_inquiry" says "submit": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent https://agent.docks.io/mcp
claude mcp add --transport http agent https://agent.docks.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent__search_offerings",
      "mcp__agent__get_product_information",
      "mcp__agent__get_inquiry_status"
    ],
    "ask": [
      "mcp__agent__assess_requirements",
      "mcp__agent__prepare_inquiry",
      "mcp__agent__submit_inquiry"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.docks/agent/verify?hash=bc659da297920a4514c47ba9cad9f494ea7c52c74abdc968b24f0e943ad0be47" | jq -e '.changed == false'

Pinned hash bc659da29792, from Nov 11, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.docks/agent/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.docks/agent
[![Anlyon Radar](https://radar.anlyon.com/badge/io.docks/agent.svg)](https://radar.anlyon.com/servers/io.docks/agent)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:13 UTC.

docks Produktberatung MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the docks Produktberatung MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the docks Produktberatung MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the docks Produktberatung MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the docks Produktberatung MCP server have?

6 tools: 3 write, 3 read. assess_requirements, prepare_inquiry, submit_inquiry, search_offerings, get_product_information and get_inquiry_status.

Does the docks Produktberatung MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the docks Produktberatung MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the docks Produktberatung MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.