SDUK Studio Discovery
REMOTE · SDUKSTUDIO.COM · SCANNED OCT 1
Read SDUK Studio's published articles and book a provisional discovery call.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1070 tokens (~267/item across 4 items; 4 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 Management0
- Stability check failed: schema churn in the 19 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the SDUK Studio Discovery MCP server?
SDUK Studio Discovery is a hosted endpoint at https://sdukstudio.com/api/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 · sdukstudio.com
claude mcp add --transport http com-sdukstudio-discovery 'https://sdukstudio.com/api/mcp'
{
"mcpServers": {
"com-sdukstudio-discovery": {
"url": "https://sdukstudio.com/api/mcp"
}
}
} {
"servers": {
"com-sdukstudio-discovery": {
"type": "http",
"url": "https://sdukstudio.com/api/mcp"
}
}
} [mcp_servers.com-sdukstudio-discovery] url = "https://sdukstudio.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-sdukstudio-discovery": {
"type": "remote",
"url": "https://sdukstudio.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-sdukstudio-discovery --url 'https://sdukstudio.com/api/mcp' --transport streamable-http
mcp_servers:
com-sdukstudio-discovery:
url: "https://sdukstudio.com/api/mcp" {
"McpServers": {
"com-sdukstudio-discovery": {
"Transport": "http",
"Url": "https://sdukstudio.com/api/mcp"
}
}
} assistant mcp add com-sdukstudio-discovery -t streamable-http -u 'https://sdukstudio.com/api/mcp'
{
"mcpServers": {
"com-sdukstudio-discovery": {
"type": "http",
"url": "https://sdukstudio.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 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
- 25 Sept 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
- 23 Sept 26 0
- A breaking change shipped without a version bump: still 1 ▼ security
- Tool “book-discovery-call” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “public-capabilities” rewrote its description, which is the text the model reads security
- Tool “public-post” rewrote its description, which is the text the model reads security
- Tool “public-posts” rewrote its description, which is the text the model reads security
- Schema quality: 136 → 267 ▼ functional
- Tool coverage: 0% → 47% ▲ functional
- Schema quality: good → excellent functional
- New tool “request-discovery-call” functional
- 22 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 159 → 136 ▲ functional
- New tool “public-capabilities” functional
- 14 Sept 26 −2
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 1 ▼ security
- Tool “endpoint-book-discovery-call” was removed ▼ security
- Tool “endpoint-public-post” was removed ▼ security
- Tool “endpoint-public-posts” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- New tool “book-discovery-call” functional
- New tool “public-post” functional
- New tool “public-posts” functional
- 13 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 59
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 1 Oct 2026 · Probed https://sdukstudio.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sdukstudio.com | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5e81e86a75eca5de94234b1c36459ea7ecc |
| SANs: sdukstudio.com | ||||||
| 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 sdukstudio.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sdukstudio.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sdukstudio.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://sdukstudio.com/api/mcp | HTTPS enforced | 308 | https://sdukstudio.com/api/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 →
public-capabilities ~76
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
public-post ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
public-posts ~71
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request-discovery-call ~659
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alternative-times | string | – | Any other times that would also suit, in their own words. Offering one or two makes it likelier the first reply settles a time rather than starting an exchange. |
| company | string | – | – |
| compliance-level | string | – | Which regime the system must satisfy: ordinary UK GDPR, NHS DSPT, FCA, another regulated regime, or unsure. |
| concurrent-users-band | string | – | – |
| contact-preference | string | – | How the person would rather be reached about arranging the call: 'email', 'phone' or 'either'. Only offer 'phone' if a phone number has been supplied. Leave unset if they have no preference. |
| country | string | – | – |
| data-residency | string | – | – |
| data-volume-band | string | – | A rough sense of how much data the system will hold — a judgement, not a measurement. Use 'unsure' rather than guessing. |
| string | yes | – | |
| entity-count-band | string | – | Roughly how many distinct kinds of record the system needs (customers, jobs, invoices and so on), not how many rows. |
| full-name | string | yes | – |
| phone | string | – | A phone number, if the person is happy to be rung. Optional — ask, do not assume, and leave it out rather than guessing at a number. |
| project-type | string | yes | – |
| proposed-route | string | – | Which part of SDUK Studio should take the work, if the person has a view. 'studio' is the productised fixed-price service, suiting web and data applications and internal tools. 'bespoke-sduk-team' is… |
| requested-time | string | – | The person's preferred date and time for the call, in their own words (for example 'Tuesday 23rd at 2pm' or 'next week, mornings'). UK time unless they say otherwise. A preference, not a slot. |
| summary | string | – | – |
| tenancy-need | string | – | Whether many separate customer organisations will use the system ('multi-tenant') or just one ('single-org'). |
| timeline | string | – | – |
No output schema declared.
No examples provided.
What is the SDUK Studio Discovery MCP server?
SDUK Studio Discovery is an MCP server listed in the public MCP registry as com.sdukstudio/discovery. Read SDUK Studio's published articles and book a provisional discovery call. This page covers its hosted endpoint (https://sdukstudio.com/api/mcp).
Is the SDUK Studio Discovery MCP server safe to use?
SDUK Studio Discovery scores 59 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 SDUK Studio Discovery MCP server expose?
SDUK Studio Discovery exposes 4 tools: public-capabilities, public-post, public-posts, request-discovery-call. Their descriptions and schemas cost roughly 866 tokens of context every time the server is loaded.
Does the SDUK Studio Discovery MCP server require authentication?
No. We connected to SDUK Studio Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SDUK Studio Discovery MCP server still maintained?
SDUK Studio Discovery is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.