Remote MCP · Endpoint

url-oracle — URL Trust Oracle MCP server

No. url-oracle — URL Trust Oracle answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://url-oracle.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.julian-martin89/url-oracle
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
112 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Flags phantom-squatted/typosquatted domains and known-malicious URLs before an agent follows them.
Listing
From the official MCP registry (active).
Recent checks of url-oracle — URL Trust Oracle
CheckedResultHandshake
40 minutes agoHandshake completed112 ms
3 days agoHandshake completed129 ms
13 days agoHandshake completed186 ms
13 days agoHandshake completed110 ms
15 days agoHandshake completed119 ms
16 days agoHandshake completed105 ms
17 days agoHandshake completed112 ms
18 days agoHandshake completed120 ms
18 days agoHandshake completed124 ms
20 days agoHandshake completed109 ms
22 days agoHandshake completed118 ms
25 days agoHandshake completed107 ms
27 days agoHandshake completed119 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with url-oracle — URL Trust Oracle and makes no claim about it beyond what these checks measured.