Remote MCP · Endpoint

NOMOS Cross-Border Broker MCP server

Yes, as of 1 hour ago: the connection was refused or dropped.

DownLast checked 1 hour ago

Server URL

https://tooloracle.io/mcp/nomos

The last check failed: the connection was refused or dropped.

Registry name
io.github.AgentNOMOS/nomos-crossborder-broker
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
23.5% from 17 checks
Described by its publisher as
Cross-border preflight, x402 quote and evidence receipts for A2A/MCP agent workflows.
Repository
https://github.com/AgentNOMOS/nomos-crossborder-broker
Listing
From the official MCP registry (active).
Recent checks of NOMOS Cross-Border Broker
CheckedResultHandshake
1 hour agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—
4 days agoFailed - the connection was refused or dropped—
5 days agoFailed - the connection was refused or dropped—
7 days agoFailed - the connection was refused or dropped—
8 days agoFailed - the connection was refused or dropped—
9 days agoFailed - the connection was refused or dropped—
12 days agoFailed - the connection was refused or dropped—
13 days agoFailed - the connection was refused or dropped—
15 days agoFailed - the connection was refused or dropped—
16 days agoFailed - the connection was refused or dropped—
18 days agoFailed - the connection was refused or dropped—
19 days agoHandshake completed311 ms
20 days agoFailed - the connection was refused or dropped—
20 days agoHandshake completed299 ms
21 days agoHandshake completed327 ms
22 days agoHandshake completed1.49 s

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

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 NOMOS Cross-Border Broker and makes no claim about it beyond what these checks measured.