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.