TechSee · OAuth Scopes

TechSee OAuth Scopes

OAuth 2.0 probed

TechSee publishes 1 OAuth 2.0 scope. Scopes are the fine-grained permissions an application requests at authorization time to act against the TechSee API on a user’s behalf.

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.

CompanyVisual AssistanceCustomer ExperienceCustomer ServiceContact CenterComputer VisionAugmented RealityArtificial IntelligenceField ServiceRemote SupportVideoTelecommunications

Scopes: 1 Flows: Method: probed

Scopes (1)

Scope	Description	Flows
mcp	The only scope the authorization server advertises. It grants access to the protected resource https://techsee.com/wp-json/mcp/mcp-oauth-server — i.e. the whole MCP surface. No finer-grained scopes (read vs write, per-ability, per content type) are published, so an agent holding this scope holds everything the MCP server exposes. No description text is supplied by the provider; this note is API Evangelist's reading of the two metadata documents, not provider prose.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-29'
method: probed
source: https://techsee.com/.well-known/oauth-authorization-server (200, RFC 8414)
name: TechSee
slug: techsee
docs: null
docs_note: >-
  TechSee publishes no scopes/permissions reference page. The scope list below is
  read verbatim from the live OAuth 2.0 Authorization Server Metadata document and
  is corroborated by the RFC 9728 protected-resource metadata, which advertises the
  same single scope.
authorization_server: https://techsee.com
scope_count: 1
scopes:
- name: mcp
  description: >-
    The only scope the authorization server advertises. It grants access to the
    protected resource https://techsee.com/wp-json/mcp/mcp-oauth-server — i.e. the
    whole MCP surface. No finer-grained scopes (read vs write, per-ability, per
    content type) are published, so an agent holding this scope holds everything the
    MCP server exposes. No description text is supplied by the provider; this note
    is API Evangelist's reading of the two metadata documents, not provider prose.
  source: https://techsee.com/.well-known/oauth-authorization-server

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/techsee-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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