Verto Education · OAuth Scopes

Verto Education OAuth Scopes

OAuth 2.0 probed

Verto Education 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.

CompanyEducationHigher EducationStudy AbroadCollege AdmissionsStudentsTravelModel Context ProtocolOAuthAgents
Scopes: 0 Flows: Method: probed

Scopes (0)

Verto Education 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.

📄 Provider scope reference:

Source

OAuth Scopes

verto-education-scopes.yml Raw ↑ 
generated: '2026-09-02'
method: probed
source: https://vertoeducation.org/.well-known/oauth-authorization-server
name: Verto Education OAuth Scopes
description: >-
  The complete scope surface Verto Education's authorization server advertises. Both
  discovery documents agree and both list exactly one scope. There is no published
  scopes or permissions reference page to enrich this from - the metadata document is
  the only source, and it is the authoritative one.
authorization_server: https://vertoeducation.org
scope_count: 1
scopes:
- name: mcp
  description: >-
    Grants access to the Model Context Protocol endpoint at
    https://vertoeducation.org/wp-json/mcp/mcp-oauth-server. The server declares no
    finer-grained read/write split - a token either carries `mcp` or it reaches nothing.
  resource: https://vertoeducation.org/wp-json/mcp/mcp-oauth-server
  source: scopes_supported in RFC 8414 metadata and RFC 9728 protected-resource metadata
  documented_by_provider: false
docs: null
docs_note: >-
  No human-readable scopes/permissions reference is published. Searched the site and
  its llms.txt page inventory; the developer surface is entirely undocumented in prose.
granularity_note: >-
  A single coarse scope over a whole MCP tool surface means a consenting user cannot
  grant an agent partial access. What `mcp` actually authorises cannot be established
  anonymously because tools/list is itself gated (HTTP 401).
x-evidence:
- url: https://vertoeducation.org/.well-known/oauth-authorization-server
  http_status: 200
- url: https://vertoeducation.org/.well-known/oauth-protected-resource
  http_status: 200
checked: '2026-09-02'

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/verto-education-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.