Remote MCP · Endpoint

MUJ428 Trust Layer — Bind Approved Intent to Verified Effect MCP server

No. MUJ428 Trust Layer — Bind Approved Intent to Verified Effect answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://agents.muj428.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.wmujahid428-web/muj428-trust-layer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
134 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Payment-rail-independent intent-to-effect integrity for consequential agent actions.
Repository
https://github.com/wmujahid428-web/muj428-a2a-revenue-engine
Listing
From the official MCP registry (active).
Recent checks of MUJ428 Trust Layer — Bind Approved Intent to Verified Effect
CheckedResultHandshake
5 hours agoHandshake completed134 ms
2 days agoHandshake completed349 ms
4 days agoHandshake completed327 ms
5 days agoHandshake completed162 ms
7 days agoHandshake completed152 ms
8 days agoHandshake completed280 ms
9 days agoHandshake completed256 ms
12 days agoHandshake completed144 ms
13 days agoHandshake completed138 ms
15 days agoHandshake completed144 ms
16 days agoHandshake completed126 ms
17 days agoHandshake completed271 ms
18 days agoHandshake completed168 ms
19 days agoHandshake completed129 ms
20 days agoHandshake completed167 ms
21 days agoHandshake completed151 ms
22 days agoHandshake completed138 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 MUJ428 Trust Layer — Bind Approved Intent to Verified Effect and makes no claim about it beyond what these checks measured.