# SDUK Studio Discovery (remote · sdukstudio.com)

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

- Trust score: 59/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

- remote · `sdukstudio.com`: 59/100 (this document), [markdown](https://verifymcp.io/servers/com-sdukstudio-discovery/api-mcp.md), [page](https://verifymcp.io/servers/com-sdukstudio-discovery/api-mcp)

## Channel facts

- Endpoint: `https://sdukstudio.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-01.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 19 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 47% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-sdukstudio-discovery 'https://sdukstudio.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-sdukstudio-discovery": {
      "url": "https://sdukstudio.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-sdukstudio-discovery": {
      "type": "http",
      "url": "https://sdukstudio.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-sdukstudio-discovery]
url = "https://sdukstudio.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sdukstudio-discovery": {
      "type": "remote",
      "url": "https://sdukstudio.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-sdukstudio-discovery --url 'https://sdukstudio.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-sdukstudio-discovery:
    url: "https://sdukstudio.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-sdukstudio-discovery": {
      "Transport": "http",
      "Url": "https://sdukstudio.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-sdukstudio-discovery -t streamable-http -u 'https://sdukstudio.com/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 59, 0)

- [security regression] A breaking change shipped without a version bump: still 1
- [security regression] 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
- [functional regression] Schema quality: 136 → 267
- [functional improvement] Tool coverage: 0% → 47%
- [functional] Schema quality: good → excellent
- [functional] New tool “request-discovery-call”

### 2026-09-22 (score 59, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 159 → 136
- [functional] New tool “public-capabilities”

### 2026-09-14 (score 58, −2)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 1
- [security regression] Tool “endpoint-book-discovery-call” was removed
- [security regression] Tool “endpoint-public-post” was removed
- [security regression] Tool “endpoint-public-posts” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional] New tool “book-discovery-call”
- [functional] New tool “public-post”
- [functional] New tool “public-posts”

### 2026-09-13 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-12 (score 59)

First indexed and scored.

## MCP tools (4)

### `public-capabilities` (~76 tokens)

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-post` (~60 tokens)

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.

Input parameters:

- `slug` (string, required)

### `public-posts` (~71 tokens)

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-call` (~659 tokens)

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.

Input parameters:

- `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.
- `email` (string, required)
- `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, required)
- `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, required)
- `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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-sdukstudio-discovery/api-mcp#diagnostics

## Score history

- 2026-10-01: 59
- 2026-09-30: 59
- 2026-09-29: 59
- 2026-09-28: 59
- 2026-09-27: 59
- 2026-09-26: 59
- 2026-09-25: 59
- 2026-09-24: 59
- 2026-09-23: 59
- 2026-09-22: 59
- 2026-09-21: 58
- 2026-09-20: 58
- 2026-09-19: 58
- 2026-09-18: 58
- 2026-09-17: 58
- 2026-09-16: 58
- 2026-09-15: 58
- 2026-09-14: 58
- 2026-09-13: 60
- 2026-09-12: 59

## Common questions

### 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.

## Links

- Remote endpoint: https://sdukstudio.com/api/mcp
- Website: https://sdukstudio.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-sdukstudio-discovery/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-sdukstudio-discovery/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-sdukstudio-discovery/api-mcp