Scimar MCP Server (WordPress MCP Adapter)

Two Model Context Protocol endpoints advertised in the scimar.ca WordPress REST route index under the "mcp" namespace — /wp-json/mcp/mcp-oauth-server and /wp-json/mcp/mcp-adapter-default-server. Both are live and authentication-gated: an anonymous JSON-RPC tools/list returns HTTP 401, so the published tool set could not be enumerated. Unusually for this class of surface, the OAuth server endpoint answers with a WWW-Authenticate Bearer challenge naming an RFC 9728 protected-resource metadata document, and scimar.ca serves both /.well-known/oauth-authorization-server (RFC 8414) and /.well-known/oauth-protected-resource anonymously with HTTP 200.

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/mcp"
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 email required.

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

API entry from apis.yml

apis.yml Raw ↑
aid: scimar:mcp
name: Scimar MCP Server (WordPress MCP Adapter)
description: 'Two Model Context Protocol endpoints advertised in the scimar.ca WordPress REST route index
  under the "mcp" namespace — /wp-json/mcp/mcp-oauth-server and /wp-json/mcp/mcp-adapter-default-server.
  Both are live and authentication-gated: an anonymous JSON-RPC tools/list returns HTTP 401, so the published
  tool set could not be enumerated. Unusually for this class of surface, the OAuth server endpoint answers
  with a WWW-Authenticate Bearer challenge naming an RFC 9728 protected-resource metadata document, and
  scimar.ca serves both /.well-known/oauth-authorization-server (RFC 8414) and /.well-known/oauth-protected-resource
  anonymously with HTTP 200.'
humanURL: https://scimar.ca/wp-json/mcp
baseURL: https://scimar.ca/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agents
properties:
- type: MCPServer
  url: mcp/scimar-mcp.yml
- type: ToolCrosswalk
  url: mcp/scimar-tool-crosswalk.yml
- type: OAuthScopes
  url: scopes/scimar-scopes.yml
- type: WellKnown
  url: well-known/scimar-well-known.yml