Mcpoauthscopegate MCP

What mcpoauthscopegate-mcp does

mcpoauthscopegate-mcp MCP server provides a hosted review layer for OAuth scopes used by remote MCP servers. It is designed to assess requested access before issuing tokens, collect an approval decision, produce a consent receipt, check a server’s scope policy, and export audit information.

The service is paid and hosted at https://mcpoauthscopegate.clauxel.com/mcp. The repository is a public documentation and directory-submission reference; it does not include the private production implementation. The service’s registry name is com.clauxel.mcpoauthscopegate/mcpoauthscopegate-mcp.

How it works

A compatible MCP client connects to the hosted endpoint using Streamable HTTP. Calls are sent as JSON-RPC requests, and production requests must include a bearer token in the authorization header. The token is issued through the product website after selecting a plan and creating or requesting API access.

The available workflow is divided across five tools:

• inspect_oauth_scope_risk reviews the risk associated with requested OAuth scopes.
• request_scope_approval starts or records an approval request.
• issue_consent_receipt creates a receipt for granted consent.
• validate_server_scope_policy checks a remote server’s scope policy.
• export_scope_audit exports scope-related audit data.

The provided material does not specify each tool’s input schema, output schema, approval rules, risk scoring method, or export format. Those details should be confirmed through the product documentation or service interface before implementation.

Setup and configuration

mcpoauthscopegate-mcp MCP server does not require installing local source code according to the supplied documentation. Setup consists of opening the product website, choosing a plan, obtaining an API token, adding the remote endpoint to an MCP client that supports Streamable HTTP remote servers, and sending authenticated JSON-RPC requests.

Use this endpoint for MCP connections:

https://mcpoauthscopegate.clauxel.com/mcp

Authenticate requests with:

Authorization: Bearer <token>

An unauthenticated browser request to the endpoint returns a JSON error rather than internal service details. The documentation does not define environment variable names or a local configuration file format, so token storage must be handled according to the selected MCP client’s configuration model.

Limitations and notes

mcpoauthscopegate-mcp MCP server is a hosted paid service, so it is not suitable for deployments that require an entirely local implementation based on the repository contents. The repository does not contain the production source code. The README also does not name specific MCP clients; compatibility depends on whether a client supports remote Streamable HTTP servers and bearer-token configuration.

The available material confirms the endpoint, access model, and tool names, but not detailed behavior for scope analysis, approval routing, receipt contents, policy validation, or audit exports. Review those contracts before relying on the service for automated authorization decisions or compliance records.