Federated Wireless MCP Server

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'