generated: '2026-08-02'
method: probed
status: published
source: https://colossal.com/wp-json/mcp
server:
  name: mcp-adapter-default-server
  transport: http
  url: https://colossal.com/wp-json/mcp/mcp-adapter-default-server
  namespace_index: https://colossal.com/wp-json/mcp
  methods: [POST, GET, DELETE]
  implementation: WordPress MCP Adapter (mcp namespace registered in the colossal.com WP REST route index)
  first_party: true
authentication:
  gated: true
  observed: 'anonymous JSON-RPC tools/list -> HTTP 401 {"code":"rest_forbidden"}'
  scheme: WordPress Application Passwords (HTTP Basic) / logged-in cookie + X-WP-Nonce
  oauth_discovery:
  - {path: /.well-known/oauth-authorization-server, status: 404}
  - {path: /.well-known/oauth-protected-resource, status: 404}
companion_surface:
  abilities_api: https://colossal.com/wp-json/wp-abilities/v1/abilities
  abilities_status: 401
  note: >-
    The WordPress Abilities API registry backs the MCP Adapter's tool list. It is also gated,
    so the published tool set could not be enumerated anonymously.
tools: []
tools_note: >-
  NOT AN EMPTY TOOL SET — the tool set is unknown. tools/list is authentication-gated and no
  llms.txt is published, so there is no public source for tool names or input schemas. Nothing
  is derived or guessed here. Authenticated introspection would be required to enumerate them.
x-evidence:
  fetched: '2026-08-02'
  url: https://colossal.com/wp-json/mcp/mcp-adapter-default-server
  http_status: 401
  content_type: application/json
  discovery_url: https://colossal.com/wp-json/