Federated Wireless MCP Server

A remote Model Context Protocol server published on federatedwireless.ai, advertised through RFC 8414 OAuth authorization-server metadata and RFC 9728 protected-resource metadata. It is not announced in any Federated Wireless documentation or MCP registry — it was found by probing /.well-known/*. The server fronts the Federated Wireless WordPress content estate (marketing site, product pages, blog, press releases), not the Spectrum Controller or the spectrum platform. Authorization is OAuth 2.1 authorization-code with PKCE (S256), a single `mcp` scope, public clients (token_endpoint_auth_method none) and client-ID metadata documents. tools/list is authenticated — an anonymous JSON-RPC call returns 401 mcp_unauthorized with a spec-correct RFC 9728 challenge — so the live tool schemas require an authorized session.

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

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

API entry from apis.yml

apis.yml Raw ↑
aid: federated-wireless:mcp-server
name: Federated Wireless MCP Server
description: A remote Model Context Protocol server published on federatedwireless.ai, advertised through
  RFC 8414 OAuth authorization-server metadata and RFC 9728 protected-resource metadata. It is not announced
  in any Federated Wireless documentation or MCP registry — it was found by probing /.well-known/*. The
  server fronts the Federated Wireless WordPress content estate (marketing site, product pages, blog,
  press releases), not the Spectrum Controller or the spectrum platform. Authorization is OAuth 2.1 authorization-code
  with PKCE (S256), a single `mcp` scope, public clients (token_endpoint_auth_method none) and client-ID
  metadata documents. tools/list is authenticated — an anonymous JSON-RPC call returns 401 mcp_unauthorized
  with a spec-correct RFC 9728 challenge — so the live tool schemas require an authorized session.
humanURL: https://federatedwireless.ai/
baseURL: https://federatedwireless.ai/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agents
- Content
properties:
- type: MCPServer
  url: mcp/federated-wireless-mcp.yml
- type: OAuthScopes
  url: scopes/federated-wireless-scopes.yml
- type: Authentication
  url: authentication/federated-wireless-authentication.yml
x-evidence:
  protected_resource: https://federatedwireless.ai/.well-known/oauth-protected-resource
  authorization_server: https://federatedwireless.ai/.well-known/oauth-authorization-server
  http_status: 200
  tools_list_status: 401
  fetched: '2026-08-12'