mcp-migration SKILL.md skillA

mcp-migration from alpayc/mcp-migration-check is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add alpayc/mcp-migration-check/mcp-migration@git:20260904.9c01ea0

Pins git:20260904.9c01ea0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
alpayc/mcp-migration-check
Path
skill/mcp-migration/SKILL.md
Versions recorded
5
Latest version
git:20260904.9c01ea0, committed Sep 4, 2026
First version recorded
Aug 27, 2026
Size
10,653 bytes
Repository stars
5
License
MIT

Diagnose and carry out the migration of an MCP server to the 2026-07-28 specification — the revision that made the transport stateless, formalized OAuth 2.1, and deprecated the logging, sampling, and roots capabilities. Use this skill whenever someone mentions migrating, upgrading, or checking an MCP server against the 2026-07-28 spec; asks whether their MCP server still works, is "ready", or will break; mentions the stateless transport model, Mcp-Session-Id, or OAuth 2.1 for MCP; or is…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# MCP 2026-07-28 migration

The 2026-07-28 revision is a refactor, not a version bump. Six things this
checker looks for break existing servers:

1. **The transport is stateless.** The `initialize`/`notifications/initialized`
   handshake and the `Mcp-Session-Id` header are gone from *this* revision.
   Every request carries its own protocol version and client capabilities in
   `_meta`. **This does not mean deleting the handshake.** A server "wishing to
   support both legacy clients … and modern clients **MAY** implement both
   behaviors" and picks its semantics from how each request opens — so the goal
   is to *add* the modern path, and retire the legacy one on the schedule your
   own clients dictate. Removing it for compliance breaks every v1 client for
   no gain.
2. **OAuth 2.1 is formalized** for remote servers: a protected MCP server acts
   as an OAuth 2.1 resource server and **MUST** implement RFC 9728
   protected-resource metadata.
3. **`logging`, `sampling`, and `roots` are deprecated** — still functional, with
   a twelve-month minimum window, but new implementations should not adopt them.
4. **The TypeScript SDK moved to v2 under new package names.**
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add alpayc/mcp-migration-check/mcp-migration@sha256:5e95efa95fc2d249

The line at the top of this page pins the label git:20260904.9c01ea0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_veghtwi2mnalfuri.svg)](https://markdownregistry.com/a/art_veghtwi2mnalfuri)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Aug 27, 2026 and Sep 4, 2026, about one every 2 days.

versioncommittedcommitsizeaudit
git:20260904.9c01ea0 latest2026-09-04 9c01ea0 10,653 BA view · diff
git:20260904.e1a432a2026-09-04 e1a432a 10,504 BA view · diff
git:20260828.08a3e252026-08-28 08a3e25 9,531 BA view · diff
git:20260828.6270b852026-08-28 6270b85 9,462 BA view · diff
git:20260827.5de427e2026-08-27 5de427e 9,356 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (10653 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

GitHub

alpayc/mcp-migration-check · 5 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_veghtwi2mnalfuri
GET https://markdownregistry.com/api/v1/resolve?ref=alpayc/mcp-migration-check/mcp-migration
GET https://markdownregistry.com/api/v1/blob/5e95efa95fc2d249c019500a5214e3343027905266fa7f29a94e3e1ff27ae4fa

Your AI assistant 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.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from alpayc/mcp-migration-check

AGENTS.md AGENTS.md file
alpayc/mcp-migration-check · AGENTS.md
git:20260904.aa323d3 · audit A · 5 stars

Every file in alpayc/mcp-migration-check

Browse by kind, by grade A, or by owner.