Tronox Holdings

Tronox MCP Server (WordPress MCP Adapter)

An authenticated Model Context Protocol (MCP) endpoint served from Tronox's own corporate WordPress host, found by probe on 2026-09-17 rather than by documentation. Anonymous discovery works end to end: the 401 carries a WWW-Authenticate resource_metadata pointer, the site publishes RFC 9728 protected-resource metadata and RFC 8414 authorization-server metadata advertising an authorization_code + PKCE (S256) flow with a single "mcp" scope, and the WordPress REST index confirms the mcp and wp-abilities/v1 namespaces. tools/list itself returns 401 mcp_unauthorized without a bearer token, so the live tool schemas could not be introspected. This is the platform-authored content surface of the marketing site, not a Tronox product, order or supply-chain API - Tronox publishes none. The hosts the previous record carried, api.tronox.com and developer.tronox.com, do not exist (NXDOMAIN).

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/tronox-holdings/refs/heads/main/authentication/tronox-holdings-authentication.yml

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/tronox-holdings/refs/heads/main/mcp/tronox-holdings-mcp.yml
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/tronox-holdings/refs/heads/main/scopes/tronox-holdings-scopes.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/tronox-holdings/refs/heads/main/errors/tronox-holdings-problem-types.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/tronox-holdings/refs/heads/main/apis.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/tronox-mcp-server"
All apis 
curl "https://apis.io/api/v1/apis?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.

API entry from apis.yml

apis.yml Raw ↑ 
aid: tronox-holdings:tronox-mcp-server
name: Tronox MCP Server (WordPress MCP Adapter)
tags:
- MCP
- Agents
- WordPress
tags_raw:
- MCP
- Agents
- WordPress
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
baseURL: https://www.tronox.com/wp-json/mcp/mcp-oauth-server
humanURL: https://www.tronox.com/
description: 'An authenticated Model Context Protocol (MCP) endpoint served from Tronox''s own corporate
  WordPress host, found by probe on 2026-09-17 rather than by documentation. Anonymous discovery works
  end to end: the 401 carries a WWW-Authenticate resource_metadata pointer, the site publishes RFC 9728
  protected-resource metadata and RFC 8414 authorization-server metadata advertising an authorization_code
  + PKCE (S256) flow with a single "mcp" scope, and the WordPress REST index confirms the mcp and wp-abilities/v1
  namespaces. tools/list itself returns 401 mcp_unauthorized without a bearer token, so the live tool
  schemas could not be introspected. This is the platform-authored content surface of the marketing site,
  not a Tronox product, order or supply-chain API - Tronox publishes none. The hosts the previous record
  carried, api.tronox.com and developer.tronox.com, do not exist (NXDOMAIN).'
properties:
- type: MCPServer
  url: mcp/tronox-holdings-mcp.yml
- type: Authentication
  url: authentication/tronox-holdings-authentication.yml
- type: OAuthScopes
  url: scopes/tronox-holdings-scopes.yml
- type: ErrorCatalog
  url: errors/tronox-holdings-problem-types.yml