Handshake passed
- Endpoint
https://uk-places-mcp.donniertf.workers.dev/mcp- Category
- Travel & Local
- Authentication
- Open
- Maintainer
- donniertf-hub
- Last checked
- 2026-11-02 16:43 UTC
Connect with Claude Code
claude mcp add --transport http uk-places 'https://uk-places-mcp.donniertf.workers.dev/mcp'Connect with Cursor
Paste into .cursor/mcp.json.
{
"mcpServers": {
"uk-places": {
"url": "https://uk-places-mcp.donniertf.workers.dev/mcp"
}
}
}Tools (6)
local_amenities_discoverlocal_amenities_packlocal_context_packwhats_on_discoverwhats_on_packredeem_pack
Source: public submission #1146 by donniertf-hub. Submitted metadata is attributed to its source; Appside independently checks connectivity.
Your agent can submit and claim this for you
{"name":"create_account","arguments":{"agent":"My assistant","purpose":"mcp-directory"}}How we check servers
Each published entry passed a dated HTTPS Streamable HTTP check using the initialize-based MCP lifecycle (2024-11-05 through 2025-11-25): MCP initialize, followed by tools/list for open servers. For protected endpoints, a 401 response with an authentication challenge establishes reachability only. We never invoke tools. Failed checks stay in our source data and are excluded from the directory.
Checks are point-in-time observations, not continuous uptime monitoring. An authentication challenge does not prove tools are available. Appside does not endorse or audit listed servers. Review the maintainer’s permissions and policies before connecting.
What does the check verify?
We send an MCP initialize request over HTTPS. Open servers must return a valid tools/list response. Protected servers may qualify with an authentication challenge. A listing is not an endorsement or a security audit.
How can I update or remove a listing?
Sign in to a free Appside account, claim the listing with a token on its server or maintainer domain, then edit or remove it. You can also request removal at privacy@appside.build.