autofi-mcp-oauth-server
AutoFi serves a live, OAuth-protected Model Context Protocol server from the WordPress installation that runs autofi.com. It was discovered through the RFC 9728 protected-resource metadata document at https://www.autofi.com/.well-known/oauth-protected-resource/, which names the MCP endpoint, and the RFC 8414 authorization-server document at https://www.autofi.com/.well-known/oauth-authorization-server/, which publishes the authorization-code + PKCE flow that guards it. Anonymous `tools/list` returns HTTP 401 `mcp_unauthorized`, so the live tool schemas could not be read without credentials.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.