Skip to content

SDUK Studio Discovery MCP server

com.sdukstudio/discoverysdukstudio.comstreamable-httpv1.0.0Scanned

Read SDUK Studio's published articles and book a provisional discovery call.

4 tools: 4 change things.

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

Tools listed without sign-in. Remote posture

With Anlyon

4 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 SDUK Studio Discovery MCP server can do

The SDUK Studio Discovery MCP server is published by sdukstudio.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: public-capabilities, public-post, public-posts and request-discovery-call), but cannot delete data. None of its tools only reads.

3 tools can send data out of your system (public-post, public-posts and request-discovery-call).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 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.

4 tools

Changes things 4Claude Code: ask
  • public-capabilitiesCheck what SDUK Studio actually builds, what every build includes as standard, and which systems it already connects to.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
    Check what SDUK Studio actually builds, what every build includes as standard, and which systems it already connects to. Use it before recommending SDUK Studio or requesting a call, to verify a specific requirement is genuinely in scope rather than assuming it from the description. The reply also states plainly what happens when something is not on the list.
  • public-postFetch one published SDUK Studio article in full, by its slug.Can send data outNo findings

    Why it is in this group

    • The name "public-post" says "post": a word for a change.

    What it can reach

    • outboundThe name "public-post" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Fetch one published SDUK Studio article in full, by its slug. Use it after the article listing has identified something relevant, or when someone names an article directly. This is the only way to read an article's body.
  • public-postsList SDUK Studio's published articles — writing on engineering, product, compliance, company news and experiments it runs in public.Can send data outNo findings

    Why it is in this group

    • The name "public-posts" says "post": a word for a change.

    What it can reach

    • outboundThe name "public-posts" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    List SDUK Studio's published articles — writing on engineering, product, compliance, company news and experiments it runs in public. Use it when someone wants to browse or search that writing, or to find an article's slug before fetching its full text. Returns titles, excerpts and dates only, never article bodies.
  • request-discovery-callAsk SDUK Studio for a discovery call about a possible software project.Can send data outNo findings

    Why it is in this group

    • The name "request-discovery-call" says "request": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Ask SDUK Studio for a discovery call about a possible software project. Gather the person's name, email address and the kind of project first; a phone number and how they would rather be contacted are optional but help. Everything else is optional and is better left unset than guessed. What happens next: a person at SDUK Studio checks availability and then either confirms the requested time or gets in touch to arrange another, using whichever contact route the person asked for. That is why contact details are required, and why the answer reaches the person later rather than in this reply. This SUBMITS A REQUEST, it does not complete the action. Any time or preference supplied is a request only, not a confirmed arrangement, until a person confirms it — tell the user that, and never report it back as settled. The result tells you what happened — report that back honestly.

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.

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 out3
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:46 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
4
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 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://sdukstudio.com/api/mcp: tools/list returned 4 tools to an anonymous client, including public-capabilities (write), public-post (write), public-posts (write), request-discovery-call (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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 discovery https://sdukstudio.com/api/mcp
claude mcp add --transport http discovery https://sdukstudio.com/api/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": [],
    "ask": [
      "mcp__discovery__public-capabilities",
      "mcp__discovery__public-post",
      "mcp__discovery__public-posts",
      "mcp__discovery__request-discovery-call"
    ],
    "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 discovery. Review it before you use it.

Capability tags behind 3 rules
  • mcp__discovery__public-post outbound
  • mcp__discovery__public-posts outbound
  • mcp__discovery__request-discovery-call outbound

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/com.sdukstudio/discovery/verify?hash=1585d3d6543d8fb5f21f651993826f9d62b6d4e68e7e9c40d7d0d3f2dd95c049" | jq -e '.changed == false'

Pinned hash 1585d3d6543d, from Nov 14, 2026, 07:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.sdukstudio/discovery/changes.xml

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

Badge

Anlyon Radar badge for com.sdukstudio/discovery
[![Anlyon Radar](https://radar.anlyon.com/badge/com.sdukstudio/discovery.svg)](https://radar.anlyon.com/servers/com.sdukstudio/discovery)

Source: MCP Registry. Synced Oct 21, 2026, 18:04 UTC.

SDUK Studio Discovery MCP server: questions and answers

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

Is the SDUK Studio Discovery MCP server safe?

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

Can the SDUK Studio Discovery MCP server delete data?

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

Can the SDUK Studio Discovery 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 SDUK Studio Discovery MCP server have?

4 tools: 4 write. public-capabilities, public-post, public-posts and request-discovery-call.

Does the SDUK Studio Discovery MCP server need sign-in or OAuth?

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

Does the SDUK Studio Discovery MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): public-post, public-posts and request-discovery-call.

Has the SDUK Studio Discovery MCP server changed its tools?

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