https://sdukstudio.com/api/mcp ↗
Read SDUK Studio's published articles and book a provisional discovery call.
SDUK Studio Discovery is a remote MCP server published at sdukstudio.com. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 755 ms, a delay an agent will notice. It offers a narrow, focused set of 3 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
endpoint-book-discovery-call — 14 parameters with unclear business context (e.g., 'tenancy-need')endpoint-public-post — 'slug' parameter lacks definition of valid formatendpoint-public-posts — No parameters but name similarity with 'endpoint-public-post' creates ambiguityRisk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
endpoint-book-discovery-callRun "Book a discovery call" (POST /discovery/book) — an action of this application. It runs immediately when you call it; there is no separate confirmation step, so only call it once you have gathered everything it needs from the user. Business rule: The discovery interview captures a lead as an anonymous visitor — the public role holds this endpoint but has no direct lead-create, so provisioning the lead row is the endpoint's whole purpose. The result tells you what happened — report that back honestly.
alternative-timesstringcompanystringcompliance-levelstringconcurrent-users-bandstringcountrystringdata-residencystringdata-volume-bandstringemailstringrequiredentity-count-bandstringfull-namestringrequiredproject-typestringrequiredproposed-routestringrequested-timestringsummarystringtenancy-needstringtimelinestringendpoint-public-postRun "Public blog post by slug" — a read-only operation of this application (GET /public/posts/:slug). Reads: blog-post, blog-category. Call it when the user asks for what it provides; results are live and scoped to them.
slugstringrequiredendpoint-public-postsRun "Public blog posts" — a read-only operation of this application (GET /public/posts). Reads: blog-post, blog-category. Call it when the user asks for what it provides; results are live and scoped to them.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-sdukstudio-discovery)<a href="https://mcpmetrics.io/servers/com-sdukstudio-discovery"><img src="https://mcpmetrics.io/badge/com.sdukstudio/discovery/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Create coordinated, print-ready coloring book interiors with quotes and explicit confirmation.
Browse published podcasts, video shows, and screenplays. Read-only public discovery.
gemini-extension.json n'est pas un mécanisme d'auto-discovery. Les Gemini Extensions sont publiées via Google AI Studio / Extensions Gallery, pas via crawl du .well-known/. Ton fichier est invisible pour Gemini. 3. ChatGPT ai-plugin.json correspond à la spec OpenAI Plugins, dépréciée en 2024. Remplacée par les GPTs (publiés via GPT Store) et les Actions (configurées dans un GPT custom). Ton fichier est mort techniquement. 4. llms.txt Proposition de standard (llmstxt.org). Aucun éditeur de LLM (Anthropic, OpenAI, Google) n'a confirmé crawler ce fichier. C'est un pari sur l'avenir, pas une réalité opérationnelle. 5. MCP endpoint Il existe, il est valide, mais aucun LLM ne le trouve tout seul. Il faut l'inscrire manuellement dans le client de l'utilisateur. Ce qui marche réellement aujourd'hui Quand un LLM répond à une question sur Timers Studio, il utilise : 1. Sa donnée d'entraînement (figée) 2. Un WebFetch live sur les pages publiques timers.st
Read-only ArcadeOps discovery for developer docs, OAuth, OpenAPI and synthetic sandbox.
Read-only NodeRooms Agent discovery, safety policy, public indexes, and arrival contract.
Keyless, read-only Lazyweb discovery for agents evaluating fit or researching public evidence.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Legacy | 200 | 754 | 200 | 755 | 2025-06-18 |
| 2026-09-12 23:31:36 | Legacy | 200 | 815 | 200 | 811 | 2025-06-18 |
| 2026-09-12 21:29:15 | Legacy | 200 | 787 | 200 | 800 | 2025-06-18 |
| 2026-09-12 19:27:29 | Legacy | 200 | 658 | 200 | 656 | 2025-06-18 |
| 2026-09-12 17:24:09 | Legacy | 200 | 671 | 200 | 668 | 2025-06-18 |
| 2026-09-12 15:21:42 | Legacy | 200 | 755 | 200 | 753 | 2025-06-18 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.