# MCP Connector Compatibility Scanner (`junipr/mcp-connector-compatibility-scanner`) Actor

Scan MCP connector manifests, server metadata, tool schemas, auth metadata, and sample responses for compatibility issues, missing fields, unsupported patterns, schema problems, and client-readiness warnings.

- **URL**: https://apify.com/junipr/mcp-connector-compatibility-scanner.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 schema validateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## 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

## MCP Connector Compatibility Scanner

### Store Positioning

**Store title:** MCP Connector Compatibility Scanner

**Short description:** Scan MCP connector manifests, server metadata, tool schemas, auth metadata, and sample responses for compatibility issues, missing fields, unsupported patterns, schema problems, and client-readiness warnings.

**SEO title:** MCP Connector Compatibility Scanner — API, schema, and developer QA

**SEO description:** Scan MCP connector manifests, server metadata, tool schemas, auth metadata, and sample responses for compatibility issues, missing fields, unsupported patterns, schema problems, and client-readiness warnings. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

**Categories:** SEO\_TOOLS, DEVELOPER\_TOOLS

**Keywords:** mcp, connector, compatibility, scanner, schema, data qa, api/developer qa

### Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: A1 — API/developer QA
- Primary event: `schema-validated` at $0.00650 base
- Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. MCP Connector Compatibility Scanner: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `schema-validated`: base $0.00650, GOLD $0.00520. MCP Connector Compatibility Scanner: charged when schema validated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `contract-rule-checked`: base $0.00390, GOLD $0.00312. MCP Connector Compatibility Scanner: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `report-generated`: base $0.05000, GOLD $0.04000. MCP Connector Compatibility Scanner: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Audit MCP Connector Compatibility controls on a capped public sample
- Find high-priority MCP Connector Compatibility issues before release
- Validate MCP Connector Compatibility evidence from supplied pages
- Prioritize MCP Connector Compatibility fixes with severity and proof
- Export MCP Connector Compatibility QA rows for client review

Scan MCP connector manifests, server metadata, tool schemas, sample responses, and docs text against a target compatibility profile. The actor helps teams find schema mismatches, missing capabilities, response-shape issues, and client-impact risks before shipping a connector to agent workflows.

### Inputs

Use `connectorManifests`, `serverMetadata`, `toolManifests`, `jsonSchemas`, `sampleResponses`, `docsText`, `compatibilityProfile`, `requiredCapabilities`, `strictSchemaValidation`, `includeRemediation`, `maxTools`, and `timeoutMs`. Keep `maxTools` low for trial runs, then widen only after the first matrix looks correct.

### Output

Rows include `connectorName`, `serverName`, `componentType`, `componentName`, `fieldPath`, `compatibilityRuleId`, `severity`, `issueCode`, `expected`, `actual`, `clientImpact`, `remediation`, `evidenceSnippet`, `passed`, and `compatibilityProfile`. KVS artifacts include compatibility summaries and remediation lists suitable for engineering review.

### Billing safety

The actor charges `actor-start` before analysis, charges the primary PPE event before each dataset row, and charges the report event before writing report artifacts. `maxChargeUsd` stops work or output gracefully before the configured cap is exceeded.

# Actor input Schema

## `connectorManifests` (type: `array`):

Connector Manifests controls MCP Connector Compatibility Scanner processing for the supplied inputs; keep values conservative for first runs.

## `serverMetadata` (type: `object`):

Server Metadata controls MCP Connector Compatibility Scanner processing for the supplied inputs; keep values conservative for first runs.

## `toolManifests` (type: `array`):

Tool Manifests controls MCP Connector Compatibility Scanner processing for the supplied inputs; keep values conservative for first runs.

## `jsonSchemas` (type: `array`):

Schemas used by MCP Connector Compatibility Scanner to validate supplied records or responses.

## `sampleResponses` (type: `array`):

Supplied responses for MCP Connector Compatibility Scanner to validate without making live requests.

## `docsText` (type: `array`):

Supplied docs text to analyze directly.

## `compatibilityProfile` (type: `string`):

Compatibility Profile controls MCP Connector Compatibility Scanner processing for the supplied inputs; keep values conservative for first runs.

## `requiredCapabilities` (type: `array`):

Require required capabilities during validation and flag rows that do not meet the rule.

## `strictSchemaValidation` (type: `boolean`):

Enable stricter validation for MCP Connector Compatibility Scanner and flag more edge cases as findings.

## `includeRemediation` (type: `boolean`):

Include remediation in output rows or reports when available.

## `maxTools` (type: `number`):

Maximum tools to process in one run; keep defaults low for safe first runs.

## `timeoutMs` (type: `number`):

Maximum time in milliseconds allowed for the MCP Connector Compatibility Scanner operation before it is treated as timed out.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE charge allowed for the run before the actor stops gracefully.

## Actor input object example

```json
{
  "connectorManifests": [
    {
      "name": "github-mcp-server",
      "version": "public-main-snapshot",
      "serverName": "github",
      "tools": [
        {
          "name": "get_file_contents",
          "inputSchema": {
            "type": "object",
            "required": [
              "owner",
              "repo",
              "path"
            ],
            "properties": {
              "owner": {
                "type": "string",
                "title": "Owner",
                "description": "Owner input value."
              },
              "repo": {
                "type": "string",
                "title": "Repo",
                "description": "Repo input value."
              },
              "path": {
                "type": "string",
                "title": "Path",
                "description": "Path input value."
              },
              "ref": {
                "type": "string",
                "title": "Ref",
                "description": "Ref input value."
              }
            }
          },
          "outputSchema": {
            "type": "object",
            "required": [
              "content",
              "sha"
            ],
            "properties": {
              "content": {
                "type": "string",
                "title": "Content",
                "description": "Content input value."
              },
              "sha": {
                "type": "string",
                "title": "Sha",
                "description": "Sha input value."
              }
            }
          }
        },
        {
          "name": "search_code",
          "inputSchema": {
            "type": "object",
            "required": [
              "query"
            ],
            "properties": {
              "query": {
                "type": "string",
                "title": "Query",
                "description": "Query input value."
              },
              "perPage": {
                "type": "number",
                "title": "Per Page",
                "description": "Per Page input value."
              }
            }
          },
          "outputSchema": {
            "type": "object",
            "required": [
              "items"
            ],
            "properties": {
              "items": {
                "type": "array",
                "title": "Items",
                "description": "Items input value."
              },
              "totalCount": {
                "type": "number",
                "title": "Total Count",
                "description": "Total Count input value."
              }
            }
          }
        }
      ],
      "auth": {
        "type": "bearer"
      }
    }
  ],
  "serverMetadata": {
    "name": "github",
    "version": "public-main-snapshot",
    "auth": {
      "type": "bearer"
    }
  },
  "toolManifests": [],
  "jsonSchemas": [
    {
      "type": "object",
      "required": [
        "content",
        "sha"
      ],
      "properties": {
        "content": {
          "type": "string",
          "title": "Content",
          "description": "Content input value."
        },
        "sha": {
          "type": "string",
          "title": "Sha",
          "description": "Sha input value."
        }
      }
    }
  ],
  "sampleResponses": [
    {
      "content": "# MCP server configuration",
      "sha": "public-spec-snapshot"
    }
  ],
  "docsText": [
    "GitHub MCP Server exposes repository and code-search tools. Tool availability is controlled by toolsets and GitHub authorization."
  ],
  "compatibilityProfile": "mcp-2025-06-18",
  "requiredCapabilities": [
    "tools",
    "auth"
  ],
  "strictSchemaValidation": true,
  "includeRemediation": true,
  "maxTools": 5,
  "timeoutMs": 5000,
  "maxChargeUsd": 1
}
```

# 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("junipr/mcp-connector-compatibility-scanner").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("junipr/mcp-connector-compatibility-scanner").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 junipr/mcp-connector-compatibility-scanner --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/mcp-connector-compatibility-scanner"
        }
    }
}

```

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/zALmm3fTv4bqxOOX5/builds/FlvY9asyrvDFz8PAp/openapi.json