What is a remote MCP server?
A remote MCP server runs over HTTP/SSE instead of a local process — you point your client at a URL instead of installing and running anything on your own machine.
Discover hosted MCP endpoints. Check the provider, authentication and setup instructions before connecting.
Parallel Search
Real-time web search and content extraction
Open Targets
Drug target discovery data
tldraw
Diagrams and whiteboards
lastminute.com
Flights, hotels, holiday packages
MDN
Web docs, search, and browser compatibility data
Yahoo Finance
Stock data, market news, financials, and price history
B12
AI website generation
Kiwi.com
Flight search and travel
Common questions about hosted and remote MCP servers
A remote MCP server runs over HTTP/SSE instead of a local process — you point your client at a URL instead of installing and running anything on your own machine.
A local server runs on your machine and needs a runtime like Node.js or Python. A remote server is hosted by a third party — you just need a URL (and sometimes an API key) to connect, which is simpler to set up but depends on the provider staying online.
Your data passes through the provider's infrastructure, so stick to servers run by official or well-known teams that document how they handle data, and grant sensitive permissions carefully.
Add the server URL in a client that supports remote MCP, then configure OAuth, an API key, or request headers as required by the provider. Streamable HTTP, SSE, and authentication support vary by client, so follow both the server page and client documentation.
Yes. Calls depend on network access, provider uptime, and rate limits. For important workflows, check the provider's status page, timeout and retry behavior, quotas, and fallback options.
Yes, when the client supports the server's remote transport and authentication method. Newer clients commonly support Streamable HTTP, while older versions may only support SSE or local stdio, so verify version compatibility first.