MCP OAuth Capability Checker

Store Positioning

Store title: MCP OAuth Capability Checker

Short description: Check supplied MCP server docs, manifests, metadata, or endpoint descriptions for OAuth capability signals, supported flows, scopes, token handling notes, PKCE support, and auth compatibility warnings.

SEO title: MCP OAuth Capability Checker — API, schema, and developer QA

SEO description: Check supplied MCP server docs, manifests, metadata, or endpoint descriptions for OAuth capability signals, supported flows, scopes, token handling notes, PKCE support, and auth compatibility 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, oauth, capability, checker, 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 Oauth Capability Checker: 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 Oauth Capability Checker: 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 Oauth Capability Checker: 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 Oauth Capability Checker: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

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

Audit MCP server documentation, discovery metadata, and supplied OAuth configuration for supported grant flows, scopes, PKCE coverage, token endpoints, and client-registration hints. The actor is designed for MCP teams, agent-tool integrators, and platform reviewers who need a structured OAuth capability matrix before connecting an agent to a remote MCP server.

Inputs

Provide serverMetadata, toolManifests, docsUrls, rawDocsText, oauthDiscoveryUrls, oauthMetadataJson, expectedScopes, requiredFlows, requirePkce, includeEvidence, maxPages, and timeoutMs. Start with supplied metadata or raw docs text, then add bounded discovery URLs only when you want live fetch checks.

Output

Rows include sourceUrl, serverName, authSupported, authType, authorizationEndpoint, tokenEndpoint, grantType, scope, pkceSupported, refreshTokenSupported, clientRegistrationMode, capabilityStatus, issueCode, confidence, evidenceText, and recommendation. KVS reports include an OAuth capability report, scope summary, metadata diagnostics, and missing-field exports.

Public source provenance

The default boundary is Google’s public OpenID Connect discovery document at https://accounts.google.com/.well-known/openid-configuration. It is used as real OAuth metadata that an MCP authorization review can evaluate; the actor does not claim Google is the target MCP server.

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.