Virtual Incision · OAuth Scopes

Virtual Incision OAuth Scopes

OAuth 2.0 probed

Virtual Incision uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyMedical DevicesSurgical RoboticsRoboticsHealthcareHealthLife SciencesMedical TechnologyContentNewsCareersEventsModel Context Protocol
Scopes: 0 Flows: Method: probed

Scopes (0)

Virtual Incision implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Scopes are read verbatim from the RFC 8414 authorization-server metadata the host serves. They govern the MCP endpoint only; the wp/v2 REST surface uses WordPress Application Passwords / cookie+nonce and has no scope model.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-04'
method: probed
source: https://virtualincision.com/.well-known/oauth-authorization-server
note: Scopes are read verbatim from the RFC 8414 authorization-server metadata the host serves. They govern the
  MCP endpoint only; the wp/v2 REST surface uses WordPress Application Passwords / cookie+nonce and has no scope
  model.
flows:
  authorization_code:
    authorization_endpoint: https://virtualincision.com/oauth/authorize
    token_endpoint: https://virtualincision.com/oauth/token
    revocation_endpoint: https://virtualincision.com/oauth/revoke
    pkce:
    - S256
    grant_types:
    - authorization_code
    - refresh_token
    token_endpoint_auth_methods:
    - none
    client_id_metadata_document_supported: true
scopes:
- name: mcp
  description: The single scope advertised in scopes_supported. Grants a client access to the Model Context Protocol
    endpoint at /wp-json/mcp/mcp-oauth-server. The provider publishes no scope reference page, so no finer-grained
    meaning is asserted here.
  source: https://virtualincision.com/.well-known/oauth-authorization-server
scope_count: 1
docs: null
docs_note: No scopes/permissions reference page is published; the discovery document is the only source.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/virtual-incision-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.