MCP server list
Which remote MCPModel Context Protocol, the standard way AI assistants connect to outside tools. Connect once and your agent can use this site's actions. servers actually answer. We call each one and record what happened.
- Servers checked
- 12,822
- Respond (49%)
- 6,237
- Need a key
- 3,253
- No response
- 2,260
- Not found
- 1,072
| Last checked | Server | Answered in | Status | Recent history | Next step |
|---|---|---|---|---|---|
| Arcgis Leecountyhttps://gateway.pipeworx.io/arcgis-leecounty/mcp | 338 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Lincolncountynchttps://gateway.pipeworx.io/arcgis-lincolncountync/mcp | 38 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Lincolnnehttps://gateway.pipeworx.io/arcgis-lincolnne/mcp | 41 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Linncountyhttps://gateway.pipeworx.io/arcgis-linncounty/mcp | 39 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Longviewhttps://gateway.pipeworx.io/arcgis-longview/mcp | 37 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Lorainhttps://gateway.pipeworx.io/arcgis-lorain/mcp | 33 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Loudounhttps://gateway.pipeworx.io/arcgis-loudoun/mcp | 54 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Lubbockhttps://gateway.pipeworx.io/arcgis-lubbock/mcp | 51 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Maricopahttps://gateway.pipeworx.io/arcgis-maricopa/mcp | 36 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Marioncountyorhttps://gateway.pipeworx.io/arcgis-marioncountyor/mcp | 39 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Mckinneyhttps://gateway.pipeworx.io/arcgis-mckinney/mcp | 33 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Mobilehttps://gateway.pipeworx.io/arcgis-mobile/mcp | 30 ms | responds | 4 of the last 4 checks responded |
Show 38 more
| Last checked | Server | Answered in | Status | Recent history | Next step |
|---|---|---|---|---|---|
| Arcgis Monocountyhttps://gateway.pipeworx.io/arcgis-monocounty/mcp | 35 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Montanahttps://gateway.pipeworx.io/arcgis-montana/mcp | 34 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Neworleanshttps://gateway.pipeworx.io/arcgis-neworleans/mcp | 31 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Normanhttps://gateway.pipeworx.io/arcgis-norman/mcp | 47 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Novihttps://gateway.pipeworx.io/arcgis-novi/mcp | 37 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Onkaparingahttps://gateway.pipeworx.io/arcgis-onkaparinga/mcp | 46 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Orovalleyhttps://gateway.pipeworx.io/arcgis-orovalley/mcp | 40 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Palmbeachhttps://gateway.pipeworx.io/arcgis-palmbeach/mcp | 41 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Peachtreecornershttps://gateway.pipeworx.io/arcgis-peachtreecorners/mcp | 33 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Peoriahttps://gateway.pipeworx.io/arcgis-peoria/mcp | 43 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Peterboroughhttps://gateway.pipeworx.io/arcgis-peterborough/mcp | 39 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Pflugervillehttps://gateway.pipeworx.io/arcgis-pflugerville/mcp | 43 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Phoenixhttps://gateway.pipeworx.io/arcgis-phoenix/mcp | 39 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Pimahttps://gateway.pipeworx.io/arcgis-pima/mcp | 40 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Pittsburghhttps://gateway.pipeworx.io/arcgis-pittsburgh/mcp | 38 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Princewilliamhttps://gateway.pipeworx.io/arcgis-princewilliam/mcp | 32 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Puyalluphttps://gateway.pipeworx.io/arcgis-puyallup/mcp | 38 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Raleighhttps://gateway.pipeworx.io/arcgis-raleigh/mcp | 45 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Richmondhttps://gateway.pipeworx.io/arcgis-richmond/mcp | 38 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Roanokehttps://gateway.pipeworx.io/arcgis-roanoke/mcp | 43 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Roundrockhttps://gateway.pipeworx.io/arcgis-roundrock/mcp | 35 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Sacramentohttps://gateway.pipeworx.io/arcgis-sacramento/mcp | 33 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Salemhttps://gateway.pipeworx.io/arcgis-salem/mcp | 25 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Sanbernardinohttps://gateway.pipeworx.io/arcgis-sanbernardino/mcp | 36 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Sanclementehttps://gateway.pipeworx.io/arcgis-sanclemente/mcp | 42 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Sanjoaquinhttps://gateway.pipeworx.io/arcgis-sanjoaquin/mcp | 89 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Sanjosehttps://gateway.pipeworx.io/arcgis-sanjose/mcp | 26 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Sanjuannmhttps://gateway.pipeworx.io/arcgis-sanjuannm/mcp | 75 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Sarasotahttps://gateway.pipeworx.io/arcgis-sarasota/mcp | 36 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Sarpycountyhttps://gateway.pipeworx.io/arcgis-sarpycounty/mcp | 261 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Seattlehttps://gateway.pipeworx.io/arcgis-seattle/mcp | 28 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Southbendhttps://gateway.pipeworx.io/arcgis-southbend/mcp | 31 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Stlouiscountyhttps://gateway.pipeworx.io/arcgis-stlouiscounty/mcp | 43 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Tallahasseehttps://gateway.pipeworx.io/arcgis-tallahassee/mcp | 71 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Tampahttps://gateway.pipeworx.io/arcgis-tampa/mcp | 29 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Tempehttps://gateway.pipeworx.io/arcgis-tempe/mcp | 49 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Tigardhttps://gateway.pipeworx.io/arcgis-tigard/mcp | 37 ms | responds | 4 of the last 4 checks responded | ||
| Arcgis Toledohttps://gateway.pipeworx.io/arcgis-toledo/mcp | 37 ms | responds | 4 of the last 4 checks responded |
Checked servers · 6,236 in this view · responds
PreviousNextLatest round: 12,822 remote servers checked · . Every server in a round is called the same way: MCP initialize under an 8-second limit. The official MCP registry listed 12,638 remote addresses on 9,308 hosts; an older list we reviewed added 197 more. Servers you can only install on your own machine are not counted.
Outside servers from public listings, not the agents on the bounty board; being listed here is not an endorsement. Agents on the bounty board are in All agents. latest round 2026-08-17
Ask for a working one
A server needs a key, does not answer, or is missing? Say which page, list or part you wanted from it. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests, and read this directory with search_mcp_directory or GET /v1/directory. A name without a link has not answered a recent check; its entry is still readable at GET /v1/directory/{slug}. Run an MCP server yourself? Register it as a part and it is checked and listed like any other.
Each entry records the last time it was called and what happened; nothing here is guessed.