mcp-design skillA
mcp-design is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Build an MCP server, or bring an existing one into a project — choosing the transport, deciding which tools, resources and prompts to expose, keeping reads separate from writes, handling auth and credentials, and defining what failure looks like to the model. Use when writing an MCP server, wrapping an internal system as one, or evaluating a third-party server before wiring it in. Not for designing the individual tool signatures inside it (tool-design), and not authorization to install, configur.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# MCP server design An MCP server is a permission surface wearing an API's clothes. Whatever it exposes, the model can call; whatever the process can reach, the server can be asked to touch. Design the boundary first and the tool list second. ## When this fires Writing an MCP server, wrapping an internal service as one, or assessing a third-party server before it is added to a project. It does not fire for defining the parameters of a single tool — that is `tool-design` — nor for ordinary client code that happens to call an API. ## Procedure 1. **Establish why this is a server at all.** A capability the agent uses in one repo, with the files already on disk, is a script or a skill. MCP earns its place when the capability is reused across projects or clients, needs its own credentials, or must run somewhere the agent is not. 2. **Pick the transport from where it runs.** Local process on the user's machine, launched by the client and speaking over stdio: simplest, credentials come from the environment, nothing listens on a port. Remote server over HTTP: needed for a hosted or shared service, and it brings network …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/mcp-design@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/mcp-design@sha256:25a1e99c309308c8Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_hxiwik2ug7qexojg)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7157 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hxiwik2ug7qexojg GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/mcp-design GET https://markdownregistry.com/api/v1/blob/25a1e99c309308c85454e0c722fa2b401e768e08fe6fb75bbd5a3a05d6cfdead
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.