# MCP OAuth Capability Checker (`junipr/mcp-oauth-capability-checker`) Actor

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.

- **URL**: https://apify.com/junipr/mcp-oauth-capability-checker.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 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.

# Actor input Schema

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

Server Metadata controls MCP OAuth Capability Checker processing for the supplied inputs; keep values conservative for first runs.

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

Tool Manifests controls MCP OAuth Capability Checker processing for the supplied inputs; keep values conservative for first runs.

## `docsUrls` (type: `array`):

Public docs URLs to fetch or inspect for MCP OAuth Capability Checker.

## `rawDocsText` (type: `array`):

Supplied docs text to analyze directly without a network fetch.

## `oauthDiscoveryUrls` (type: `array`):

Public OAuth discovery URLs to fetch or inspect for MCP OAuth Capability Checker.

## `oauthMetadataJson` (type: `array`):

Inline OAuth metadata JSON object used by MCP OAuth Capability Checker.

## `expectedScopes` (type: `array`):

Expected scopes used for comparison and validation.

## `requiredFlows` (type: `array`):

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

## `requirePkce` (type: `boolean`):

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

## `includeEvidence` (type: `boolean`):

Include evidence in output rows or reports when available.

## `maxPages` (type: `number`):

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

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

Maximum time in milliseconds allowed for the MCP OAuth Capability Checker 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
{
  "serverMetadata": {
    "name": "Google OAuth metadata review"
  },
  "toolManifests": [],
  "docsUrls": [],
  "rawDocsText": [],
  "oauthDiscoveryUrls": [
    "https://accounts.google.com/.well-known/openid-configuration"
  ],
  "oauthMetadataJson": [],
  "expectedScopes": [
    "openid"
  ],
  "requiredFlows": [
    "authorization_code"
  ],
  "requirePkce": false,
  "includeEvidence": true,
  "maxPages": 1,
  "timeoutMs": 10000,
  "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-oauth-capability-checker").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-oauth-capability-checker").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-oauth-capability-checker --silent --output-dataset

```

## MCP server setup

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

```

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/U8V98Ho4VAnfZmwSp/builds/DvcfVVZgkMpG3zgfk/openapi.json