# MCP 2026 Compatibility & Migration Auditor (`obliging_persimmon_cki/mcp-2026-compatibility-migration-auditor`) Actor

Bounded, explainable audits of public MCP endpoint compatibility against a pinned official specification.

- **URL**: https://apify.com/obliging\_persimmon\_cki/mcp-2026-compatibility-migration-auditor.md
- **Developed by:** [Dung Huynh](https://apify.com/obliging_persimmon_cki) (community)
- **Categories:** MCP servers, Developer tools, Other
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does this Actor do?

MCP 2026 Compatibility & Migration Auditor checks public, unauthenticated MCP HTTP endpoints against the released Model Context Protocol specification 2026-07-28. It performs bounded read-only live discovery, evaluates a versioned ruleset, and returns one explainable report per canonical endpoint. Each report includes a compatibility status, a normalized 0–100 score, confidence and coverage, stable check IDs, official references, evidence, warnings, and prioritized migration actions.

The Actor only sends safe protocol discovery and capability-list requests. It never calls tools, reads resources, sends prompts, uses cookies or credentials, or follows a redirect without validating the destination again. Private, loopback, link-local, metadata, multicast, reserved, and unspecified destinations are rejected before any request.

### Why use it?

Use this Actor when you need a repeatable migration inventory across several remote MCP servers. The output is structured for API consumers and AI workflows: stable `serverKey` values support deduplication, `checkIds` support remediation tracking, and official references make each result auditable. Unknown evidence stays unknown and lowers coverage/confidence instead of being presented as a definite compatibility failure.

### How to use it

1. Add one to ten public MCP endpoint URLs in `mcpServers`.
2. Optionally add positional public GitHub repositories and enable `includeRepositoryAnalysis` for secondary static evidence.
3. Choose a timeout between 3 and 60 seconds.
4. Run the Actor and inspect the Dataset output. Start with `compatibility.status`, `compatibility.score`, `dataQuality`, then follow `migrationActions` and their linked check IDs.

Example input:

```json
{
  "mcpServers": ["https://mcp.apify.com/?tools=docs"],
  "githubRepositories": [],
  "timeoutSecs": 15,
  "includeRepositoryAnalysis": false
}
```

### Input

`mcpServers` accepts one to ten endpoint strings. Valid public HTTP(S) URLs are audited; malformed, unsupported, credential-bearing, or private entries produce isolated reports without an outbound request. Credentials, sensitive headers, unknown fields, and unbounded values are rejected. `githubRepositories` is optional and positionally associated with the server list. Repository inspection is unauthenticated, bounded, opt-in, and never overrides live protocol evidence.

### Output

The Dataset contains one report per canonical endpoint. The main fields are `serverKey`, `server`, `compatibility`, `capabilities`, `checks`, `migrationActions`, `warnings`, and `dataQuality`.

Simplified output:

```json
{
  "serverKey": "https://example.com/mcp",
  "compatibility": { "status": "partial", "score": 75, "targetSpecification": "2026-07-28" },
  "checks": [{ "id": "discovery.server-discover.required", "status": "pass" }],
  "migrationActions": [],
  "dataQuality": { "coverage": "complete", "unknownChecks": [] }
}
```

Download the Dataset as JSON, CSV, Excel, or HTML from Apify. JSON preserves the complete nested evidence and provenance contract; CSV and Excel are convenient for inventories and remediation tracking, while HTML is useful for sharing a readable snapshot.

### Cost

This Actor does not set or change pricing automatically. Apify run cost depends on allocated compute, runtime, request volume, and optional repository analysis. The Actor itself caps endpoint count, requests, response bytes, redirects, retries, repository files, and concurrency.

### Tips and limitations

- Use public endpoints that do not require authentication.
- Treat `unknown` and `partial` as data-quality signals, not automatic failures.
- Keep repository analysis disabled unless static evidence is useful.
- The audit is intentionally read-only and does not prove that tools are safe to invoke.

### FAQ

**Does it call MCP tools?** No. Tool calls, resource reads, prompt retrieval, and other side-effecting methods are outside the audit boundary.

**Why is a reachable server unknown?** The server may not expose the bounded discovery shape, may return malformed data, or may exceed a safety limit. Inspect `warnings` and `dataQuality`.

**Can it audit private network endpoints?** No. This is a deliberate SSRF and privacy boundary.

### API, support, and disclaimer

Use the Apify API to start a run and retrieve its default Dataset. The input and output schemas in `.actor/` are the machine-readable contract. Report issues with a reproducible public endpoint, sanitized input, Actor run ID, and relevant warning/check IDs; never include credentials or tokens.

This tool provides bounded compatibility evidence, not certification, security approval, or legal advice. Always review the official [MCP 2026-07-28 specification](https://modelcontextprotocol.io/specification/2026-07-28), [server discovery](https://modelcontextprotocol.io/specification/2026-07-28/server/discover), [Streamable HTTP transport](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports), and [changelog](https://modelcontextprotocol.io/specification/2026-07-28/changelog).

### Development

```bash
npm test
npm run build
npm run lint
apify validate-schema
npm run benchmark:fixtures
```

The fixture benchmark disables network access and reports runtime, memory, requests, retries, response bytes, endpoint count, and output count. Publishing and pricing remain manual operations.

# Actor input Schema

## `mcpServers` (type: `array`):

One to ten endpoint strings. Valid public HTTP(S) URLs are audited; malformed, unsupported, credential-bearing, or private entries produce isolated reports without an outbound request. Duplicate canonical endpoints are audited once in first-occurrence order.

## `githubRepositories` (type: `array`):

Zero to ten public owner/repository identifiers associated positionally with mcpServers.

## `timeoutSecs` (type: `integer`):

Bounded timeout for one safe protocol request, from 3 through 60 seconds.

## `includeRepositoryAnalysis` (type: `boolean`):

Whether to request bounded unauthenticated public GitHub evidence as a secondary source.

## Actor input object example

```json
{
  "mcpServers": [
    "https://mcp.apify.com/?tools=docs"
  ],
  "githubRepositories": [],
  "timeoutSecs": 15,
  "includeRepositoryAnalysis": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

One structured report per canonical serverKey. See dataset\_schema.json for the full record contract.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("obliging_persimmon_cki/mcp-2026-compatibility-migration-auditor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("obliging_persimmon_cki/mcp-2026-compatibility-migration-auditor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call obliging_persimmon_cki/mcp-2026-compatibility-migration-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,obliging_persimmon_cki/mcp-2026-compatibility-migration-auditor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/jZNT1S3C6iwLOgyFm/builds/Ixe2vGsDXRHIbNLig/openapi.json