Webz.io · OAuth Scopes

Webz.io OAuth Scopes

OAuth 2.0 probed

Webz.io publishes 1 OAuth 2.0 scope via the authorization_code and client_credentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Webz.io 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.

News DataWeb DataWeb ScrapingDark Webdeep-webCybersecurityThreat IntelligenceData Breachpii-monitoringOSINTreviews-dataAI Training DataMedia Monitoring

Scopes: 1 Flows: authorization_code, client_credentials Method: probed

Scopes (1)

Scope	Description	Flows
mcp	The only scope the News Search MCP authorization server advertises in scopes_supported. It grants access to the single protected resource https://news-search-mcp.webz.io/mcp; the server publishes no finer-grained or per-tool scopes.

📄 Provider scope reference: https://docs.webz.io/docs/webz/news-search-api-mcp

Source

OAuth Scopes

generated: '2026-08-27'
method: probed
source: https://news-search-mcp.webz.io/.well-known/oauth-authorization-server
docs: https://docs.webz.io/docs/webz/news-search-api-mcp
note: >-
  Webz.io's REST APIs use a single opaque API token with no scopes; entitlement is a per-product
  permission on the account, not an OAuth scope. The only OAuth surface is the authorization server
  in front of the News Search MCP endpoint, and it advertises exactly one scope. Recorded from the
  live RFC 8414 metadata document, not inferred.
authorization_server: https://news-search-mcp.webz.io/
resource: https://news-search-mcp.webz.io/mcp
scope_count: 1
scopes:
- name: mcp
  description: >-
    The only scope the News Search MCP authorization server advertises in scopes_supported. It grants
    access to the single protected resource https://news-search-mcp.webz.io/mcp; the server publishes
    no finer-grained or per-tool scopes.
  source: scopes_supported in the RFC 8414 metadata
flows:
  authorization_code:
    supported: true
    pkce: S256
  refresh_token:
    supported: true
  client_credentials:
    supported: false
token_endpoint_auth_methods_supported:
- client_secret_post
- client_secret_basic
dynamic_client_registration: https://news-search-mcp.webz.io/register
non_oauth_entitlements:
  note: >-
    These are account permissions, not scopes. They are listed here because they are what actually
    gates access on the REST surface, and an agent planning a call needs to know them.
  permissions:
  - api_news
  products_requiring_separate_entitlement:
  - News / Blogs / Forums
  - Reviews
  - Cyber
  - Data Breaches
  - Archive
  - Firehose
  - view-password (Data Breaches — returns unmasked passwords)
  - per-domain authorization (Data Breaches)

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/webz-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.