Remote MCP · Endpoint

MyPorta MCP server

No. MyPorta answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://www.myporta.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.myporta/myporta
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
147 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find UK homes for sale and to rent, matched to your wishes, with nearby schools and area guides.
Website
https://www.myporta.ai/
Listing
From the official MCP registry (active).
Recent checks of MyPorta
CheckedResultHandshake
59 minutes agoHandshake completed147 ms
1 day agoHandshake completed82 ms
4 days agoHandshake completed640 ms
6 days agoHandshake completed112 ms
9 days agoHandshake completed352 ms
11 days agoHandshake completed394 ms
13 days agoHandshake completed472 ms
15 days agoHandshake completed439 ms
17 days agoHandshake completed88 ms
19 days agoHandshake completed36 ms
21 days agoHandshake completed47 ms
22 days agoHandshake completed42 ms
23 days agoHandshake completed703 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with MyPorta and makes no claim about it beyond what these checks measured.