How do I install the MCP Spec And Servers Foundation skill?

Run npx skillmds@latest add ryan-brosas/mcp-spec-and-servers-foundation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is MCP Spec And Servers Foundation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with MCP Spec And Servers Foundation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is MCP Spec And Servers Foundation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published MCP Spec And Servers Foundation?

ryan-brosas (@ryan-brosas) published this skill. Their other Agent Skills are listed on their SkillMD profile.

MCP Spec And Servers Foundation by ryan-brosas

Name: MCP Spec And Servers Foundation
Author: ryan-brosas

MCP Spec And Servers Foundation

Use when building MCP servers or clients: modern-era stateless lifecycle, per-request _meta, Streamable HTTP + stdio transports, MRTR, subscriptions, OAuth 2.1 authorization, resource/prompt/completion surfaces, client features (elicitation/sampling/roots), dual-era dispatch, the Tasks extension plus task-based tool authoring and bidirectional task clients, cancellation/progress/ping patterns, structured tool outputs, URL-elicitation error paths, bounded fetches, and canonical reference-server patterns.

ryan-brosas Updated Sep 17, 2026

File contents

MCP Spec & Servers Foundation

Foundation contract

This is a cold, source-specific foundation, not an operational procedure. It is historical, revision-pinned evidence rather than timeless guidance. Current project source, tests, requirements, and runtime behavior outrank this projection and decide what ships.

Provenance and revision

Source record: mcp-spec-and-servers; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.
Recorded revision: main@57ac4a2ec742e0cb7622d899b0f5d3bcf769fd69.
Full provenance, coverage caveats, boundaries, and preserved evidence: references/index.md.

Topic map

Representative topics: Protocol core; Error routing & state; Transports; Extension & header surfaces; Interaction patterns; Data surfaces; Authorization (HTTP transports); Server↔client features.
Scope and retrieval questions: references/index.md#use-this-for.
Complete capsule chooser: references/index.md#load-the-matching-source-dump.
Detailed grouped map: references/index.md#capsule-map.
Source limitations and portability boundaries: references/index.md#boundaries.

Retrieval

Open the index, choose one capsule matching the active question, and load only that capsule. Revalidate its cited source and revision before relying on it. Do not bulk-load the inventory, treat historical claims as current truth, or apply this foundation as a procedure.

---name: mcp-spec-and-servers-foundationdescription: Use when building MCP servers or clients: modern-era stateless lifecycle, per-request _meta, Streamable HTTP + stdio transports, MRTR, subscriptions, OAuth 2.1 authorization, resource/prompt/completion surfaces, client features (elicitation/sampling/roots), dual-era dispatch, the Tasks extension plus task-based tool authoring and bidirectional task clients, cancellation/progress/ping patterns, structured tool outputs, URL-elicitation error paths, bounded fetches, and canonical reference-server patterns.---# MCP Spec & Servers Foundation## Foundation contractThis is a cold, source-specific foundation, not an operational procedure. It ishistorical, revision-pinned evidence rather than timeless guidance. Currentproject source, tests, requirements, and runtime behavior outrank thisprojection and decide what ships.## Provenance and revision- Source record: `mcp-spec-and-servers`; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.- Recorded revision: `main@57ac4a2ec742e0cb7622d899b0f5d3bcf769fd69`.- Full provenance, coverage caveats, boundaries, and preserved evidence: `references/index.md`.## Topic map- Representative topics: Protocol core; Error routing & state; Transports; Extension & header surfaces; Interaction patterns; Data surfaces; Authorization (HTTP transports); Server↔client features.- Scope and retrieval questions: `references/index.md#use-this-for`.- Complete capsule chooser: `references/index.md#load-the-matching-source-dump`.- Detailed grouped map: `references/index.md#capsule-map`.- Source limitations and portability boundaries: `references/index.md#boundaries`.## RetrievalOpen the index, choose one capsule matching the active question, and load onlythat capsule. Revalidate its cited source and revision before relying on it. Donot bulk-load the inventory, treat historical claims as current truth, or applythis foundation as a procedure.

Frequently asked questions