Talandor
Public MCP report

SDUK Studio Discovery

https://sdukstudio.com/api/mcp

Official Registry

Official Registry · com.sdukstudio/discovery · Publisher namespace: com.sdukstudio

Server checked today at 21:00 UTC

Catalog verified today at 11:34 UTC

4 public tools observed. Tools were not executed.

Reachable · public catalog

What Talandor observed

The server answered

Add the endpoint to a compatible client below. A Watch can alert you if this public catalog changes.

This is a public protocol and tools/list check, not a functional validation.

https://sdukstudio.com/api/mcp
AvailabilityReachablemeasured
Tools4 public tools observedmeasured
CompatibilityEstimated from published client rules · not a hands-on testestimated
Recent changeEarlier tool removal recordedHistorical

Configure your assistant · Check details

How to use this MCP

Talandor checks the server; it does not connect the server to your assistant.

Choose your assistant, then copy the configuration shown for that client. Authentication is completed with the MCP provider, never inside Talandor.

    Open the official client guide (opens in a new tab)
    Compatibility evidence by assistant

    Compatibility is estimated from published configuration rules and is not a hands-on test in each client.

    Claude
    Observed 2025-11-25.
    Likely compatible · inferred
    Cursor
    Streamable HTTP and public HTTPS were observed.
    Likely compatible · inferred
    ChatGPT
    Public tool names, descriptions and schemas were observed. Plan and workspace access still apply.
    Likely compatible · inferred
    VS Code
    Public remote HTTP configuration can be assessed.
    Likely compatible · inferred
    Generic MCP
    Observed 2025-11-25.
    Likely compatible · inferred

    Rule evidence: Remote HTTPS rule v0.2 · reviewed 2026-09-12 · Remote HTTP rule v0.2 · reviewed 2026-09-12 · Remote app rule v0.2 · reviewed 2026-09-12 · Protocol and transport rule v0.2 · reviewed 2026-09-12

    Check details

    What changed

    Public contract stable since
    Last check · No semantic contract change since the previous complete snapshot.
    Info
    book-discovery-call was removed
    Historical change · critical · high confidence · book-discovery-call · Rule: tool-removed
    Critical

    A Watch would alert only if this change may affect uses of the selected client that depend on the changed tools.

    This public timeline shows the latest check, the last 24 hours, and the most recent important change. Watch keeps 30 days.

    See earlier changes
    public-capabilities changed its title or description
    Historical change · info · high confidence · public-capabilities · Rule: documentation-changed
    Info
    public-post changed its title or description
    Historical change · info · high confidence · public-post · Rule: documentation-changed
    Info
    public-posts changed its title or description
    Historical change · info · high confidence · public-posts · Rule: documentation-changed
    Info
    request-discovery-call added an optional input field contact-preference
    Historical change · info · high confidence · request-discovery-call · Rule: optional-input-added
    Info
    request-discovery-call added an optional input field phone
    Historical change · info · high confidence · request-discovery-call · Rule: optional-input-added
    Info
    request-discovery-call was added
    Historical change · info · high confidence · request-discovery-call · Rule: tool-added
    Info

    The notes above are for this connector.

    Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
    Tools and declared exposure

    Server annotations are declarations, not verified behavior.

    Show 4 of 4 server-provided tool definitions
    public-capabilities
    No effect details provided
    Show server-provided details
    Server description (copied; language not verified)
    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 (server-provided preview — do not copy)
    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    public-post
    No effect details provided
    Show server-provided details
    Server description (copied; language not verified)
    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 schema (server-provided preview — do not copy)
    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 200
        }
      },
      "additionalProperties": false
    }
    public-posts
    No effect details provided
    Show server-provided details
    Server description (copied; language not verified)
    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 (server-provided preview — do not copy)
    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    request-discovery-call
    No effect details provided
    Show server-provided details
    Server description (copied; language not verified)
    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 schema (server-provided preview — do not copy)
    {
      "type": "object",
      "required": [
        "email",
        "full-name",
        "project-type"
      ],
      "properties": {
        "email": {
          "type": "string"
        },
        "phone": {
          "type": "string",
          "maxLength": 40,
          "description": "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."
        },
        "company": {
          "type": "string"
        },
        "country": {
          "type": "string"
        },
        "summary": {
          "type": "string"
        },
        "timeline": {
          "enum": [
            "exploring",
            "under-3-months",
            "3-to-6-months",
            "6-months-plus",
            "unsure"
          ],
          "type": "string"
        },
        "full-name": {
          "type": "string"
        },
        "project-type": {
          "enum": [
            "web-data-app",
            "mobile-app",
            "3d-cad",
            "internal-tool",
            "other",
            "unsure"
          ],
          "type": "string"
        },
        "tenancy-need": {
          "enum": [
            "single-org",
            "multi-tenant",
            "unsure"
          ],
          "type": "string",
          "description": "Whether many separate customer organisations will use the system ('multi-tenant') or just one ('single-org')."
        },
        "data-residency": {
          "enum": [
            "uk",
            "eu",
            "us",
            "other",
            "unsure"
          ],
          "type": "string"
        },
        "proposed-route": {
          "enum": [
            "studio",
            "bespoke-sduk-team",
            "either"
          ],
          "type": "string",
          "description": "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 for work outside that shape, such as mobile or 3D/CAD — not a refusal. 'either' means both could fit. Leave unset if unclear; the call settles it."
        },
        "requested-time": {
          "type": "string",
          "description": "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."
        },
        "compliance-level": {
          "enum": [
            "standard-gdpr",
            "nhs-dspt",
            "fca",
            "other-regulated",
            "unsure"
          ],
          "type": "string",
          "description": "Which regime the system must satisfy: ordinary UK GDPR, NHS DSPT, FCA, another regulated regime, or unsure."
        },
        "data-volume-band": {
          "enum": [
            "low",
            "medium",
            "high",
            "unsure"
          ],
          "type": "string",
          "description": "A rough sense of how much data the system will hold — a judgement, not a measurement. Use 'unsure' rather than guessing."
        },
        "alternative-times": {
          "type": "string",
          "description": "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."
        },
        "entity-count-band": {
          "enum": [
            "small-1-10",
            "medium-11-30",
            "large-30-plus",
            "unsure"
          ],
          "type": "string",
          "description": "Roughly how many distinct kinds of record the system needs (customers, jobs, invoices and so on), not how many rows."
        },
        "contact-preference": {
          "enum": [
            "email",
            "phone",
            "either"
          ],
          "type": "string",
          "description": "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."
        },
        "concurrent-users-band": {
          "enum": [
            "under-50",
            "50-to-500",
            "500-plus",
            "unsure"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    Evidence and limitations

    Method: anonymous Streamable HTTP probe. We never invoke a tool.

    Attempted protocols: 2026-07-28, 2025-11-25

    Protocol2025-11-25
    TransportStreamable HTTP
    AuthNo authentication challenge observed
    EvidencePublic contract observed
    Total latency6276 ms
    Response bytes5215

    No diagnostic errors.

    Observation history
    Operational
    · stable since
    2025-11-25 · 4 tools · no change · 9 checks
    Operational
    2025-11-25 · 4 tools
    Operational
    · stable since
    2025-11-25 · 4 tools · no change · 11 checks
    Operational
    · stable since
    2025-11-25 · 3 tools · no change · 34 checks
    Operational
    2025-11-25 · 3 tools
    Complete public contract · 2025-11-25 · 4 tools
    63750b5e7ed5
    Complete public contract · 2025-11-25 · 4 tools
    3edddee4256a
    Complete public contract · 2025-11-25 · 4 tools
    942568d5f737
    Complete public contract · 2025-11-25 · 3 tools
    9d5e4d551613
    Complete public contract · 2025-11-25 · 3 tools
    9d5e4d551613

    Deep monitoring eligibility

    Eligible for deep monitoring

    A complete public tools/list contract was observed, so a future deep-monitoring baseline can be compared safely.

    Personal Watch is not open yet. This report does not start a Watch or a payment.

    See public monitoring

    Automatic monitoring later

    Saving this connector does not start a Watch. Watch is a future offer; subscriptions and alerts are not available yet.

    Full Watch. Availability, protocol, auth and public tool contract changes can be compared.