M

MCP Migration Check

Deterministic MCP 2026-07-28 migration checker with an agent skill, CLI, GitHub

alpayc/mcp-migration-check · v0.6.0

by AlpayCOwner verified

The Model Context Protocol revision dated 2026-07-28 is the largest breaking change in the protocol's history: it makes the transport stateless, formalizes OAuth 2.1 for remote servers, and deprecates several capabilities. Migrating is a refactor, not a version bump — and a large share of the thousands of public servers aren't actively maintained. mcp-migration-check is a small, deterministic readiness checker. It points at a running MCP endpoint (or scans a repo) and reports, with a letter grade and per-finding fixes, exactly what breaks. No LLM, no API key, nothing stored. It ships as four surfaces over one core: Surface Use it to… Web demo paste a URL, get a graded report — nothing to install CLI npx mcp-migration-check <url> — one command, no install GitHub Action keep a server from regressing, with a grade on every PR Skill hand an agent the diagnosis and the migration procedure The split is deliberate. The demo and the CLI see a server from the outside and answer "am I broken?". The Action asks that question again on every commit. The skill sees the code and answers "fix it" — which is the part that actually takes a week.

Follow0
Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is MCP Migration Check a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

Not declared

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Not declared

Check before relying on it

What is MCP Migration Check?

MCP Migration Check is a published ai agent plugin for AI coding agents, developed by AlpayC and distributed through the HOL AI plugin registry. The Model Context Protocol revision dated 2026-07-28 is the largest breaking change in the protocol's history: it makes the transport stateless, formalizes OAuth 2.1 for remote servers, and deprecates several capabilities. Migrating is a refactor, not a version bump — and a large share of the thousands of public servers aren't actively maintained. mcp-migration-check is a small, deterministic readiness checker. It points at a running MCP endpoint (or scans a repo) and reports, with a letter grade and per-finding fixes, exactly what breaks. No LLM, no API key, nothing stored. It ships as four surfaces over one core: Surface Use it to… Web demo paste a URL, get a graded report — nothing to install CLI npx mcp-migration-check <url> — one command, no install GitHub Action keep a server from regressing, with a grade on every PR Skill hand an agent the diagnosis and the migration procedure The split is deliberate. The demo and the CLI see a server from the outside and answer "am I broken?". The Action asks that question again on every commit. The skill sees the code and answers "fix it" — which is the part that actually takes a week.

Canonical slug
alpayc/mcp-migration-check
Version
v0.6.0 · updated Sep 25, 2026

Registry snapshot

Owner verification
Verified on HOL as @AlpayC
Scanner
Registry pipeline
Security result
Not scanned
Digest verified
No

Trust and security

Provenance

Plugin root
.
Source repo
https://github.com/AlpayC/mcp-migration-check
Source commit
Unpinned
Publisher verified
No
Owner verified
@AlpayC

Continuous scanner CI detected

No action is required. This plugin receives the full trust score.

README badge not detected

Plugin owners can add the HOL badge to the repository README from Guard Plugins. Distribution, not security evidence. It adds a 2% engagement adjustment to the overall trust score and never changes the security result.

Needs review
Security result
80
Security score
0
High findings

Findings

lowsecuritySECURITY_MD_MISSINGReported 2 times

Plugins should publish a SECURITY.md file for responsible disclosure and support guidance.

Add a SECURITY.md file with reporting guidance and supported versions.

lowsecurityLICENSE_MISSINGReported 2 times

Plugins should ship a LICENSE file so consumers can review usage rights.

Add a LICENSE file that matches the manifest license metadata.

lowbest-practicesREADME_MISSING

Plugins should document installation, usage, and security expectations in README.md.

Add a README.md that explains setup, usage, and operational constraints.

infomanifest-validationPLUGIN_JSON_INTERFACE_SHORTDESCRIPTION

The interface object is missing a valid "shortDescription" value.

Add a valid "shortDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_LONGDESCRIPTION

The interface object is missing a valid "longDescription" value.

Add a valid "longDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CATEGORY

The interface object is missing a valid "category" value.

Add a valid "category" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CAPABILITIES

The interface object is missing a valid "capabilities" value.

Add a valid "capabilities" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_WEBSITEURL

The interface field "websiteURL" must use HTTPS or point to a safe in-repo asset.

Update "websiteURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_PRIVACYPOLICYURL

The interface field "privacyPolicyURL" must use HTTPS or point to a safe in-repo asset.

Update "privacyPolicyURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_TERMSOFSERVICEURL

The interface field "termsOfServiceURL" must use HTTPS or point to a safe in-repo asset.

Update "termsOfServiceURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_COMPOSERICON

The interface field "composerIcon" must use HTTPS or point to a safe in-repo asset.

Update "composerIcon" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_LOGO

The interface field "logo" must use HTTPS or point to a safe in-repo asset.

Update "logo" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_SCREENSHOTS

The interface field "screenshots" must use HTTPS or point to a safe in-repo asset.

Update "screenshots" to use HTTPS or an existing relative asset path.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in Manual

No automated install path is registered for this plugin yet. Install it from the source.

Publisher guide
  1. 1

    Clone the source

    shell
  2. 2

    Follow the publisher guide

    Open https://github.com/AlpayC/mcp-migration-check for the official, harness-specific install steps from the publisher.

Did setup work in Manual?

No setup reports for Manual yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W46, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Screenshot
1 / 1

Screenshot

Full size
Loading reviews

Plugin manifest

{
  "name": "mcp-migration-check",
  "version": "v0.6.0",
  "description": "The Model Context Protocol revision dated 2026-07-28 is the largest breaking change in the protocol's history: it makes the transport stateless, formalizes OAuth 2.1 for remote servers, and deprecates several capabilities. Migrating is a refactor, not a version bump — and a large share of the thousands of public servers aren't actively maintained. mcp-migration-check is a small, deterministic readiness checker. It points at a running MCP endpoint (or scans a repo) and reports, with a letter grade and per-finding fixes, exactly what breaks. No LLM, no API key, nothing stored. It ships as four surfaces over one core: Surface Use it to… Web demo paste a URL, get a graded report — nothing to install CLI npx mcp-migration-check <url> — one command, no install GitHub Action keep a server from regressing, with a grade on every PR Skill hand an agent the diagnosis and the migration procedure The split is deliberate. The demo and the CLI see a server from the outside and answer \"am I broken?\". The Action asks that question again on every commit. The skill sees the code and answers \"fix it\" — which is the part that actually takes a week.",
  "repository": "https://github.com/AlpayC/mcp-migration-check",
  "homepage": "https://github.com/AlpayC/mcp-migration-check",
  "interface": {
    "displayName": "MCP Migration Check",
    "developerName": "AlpayC"
  }
}

File inventory

File inventory is unavailable for this plugin right now.

MCP Migration Check — Frequently asked questions

What is MCP Migration Check?
MCP Migration Check is an AI plugin in the HOL registry. The Model Context Protocol revision dated 2026-07-28 is the largest breaking change in the protocol's history: it makes the transport stateless, formalizes OAuth 2.1 for remote servers, and deprecates several capabilities. Migrating is a refactor, not a version…
How do I install MCP Migration Check?
Install MCP Migration Check in your harness: Manual — git clone https://github.com/AlpayC/mcp-migration-check. Full step-by-step guidance is on the HOL plugin page.
Is MCP Migration Check free?
MCP Migration Check is listed as free on HOL.
Who publishes MCP Migration Check?
MCP Migration Check is published by AlpayC and listed on HOL.
Is MCP Migration Check available now?
MCP Migration Check is currently available according to its latest public launch.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W46. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.
New GitHub stars
<5
From HOL's GitHub snapshots of the repository, 2026-10-23 to 2026-11-20.

History, reviews, and similar plugins

Latest launch