Remote MCP · Endpoint

Agent safety checks: prompt-injection scan, honeypot check, x402 preflight + crypto data (USDC/x402) MCP server

No. Agent safety checks: prompt-injection scan, honeypot check, x402 preflight + crypto data (USDC/x402) answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://angel.oroboros-design.com/agenten/signal/mcp

The last check completed an MCP handshake.

Registry name
com.oroboros-design.angel/tradesignal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
915 ms
Tools exposed
7 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Checks before an agent acts: prompt-injection scan, honeypot check, x402 preflight. 3 free calls.
Listing
From the official MCP registry (active).
Recent checks of Agent safety checks: prompt-injection scan, honeypot check, x402 preflight + crypto data (USDC/x402)
CheckedResultHandshake
10 hours agoHandshake completed915 ms
4 days agoHandshake completed759 ms
7 days agoHandshake completed516 ms

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

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 Agent safety checks: prompt-injection scan, honeypot check, x402 preflight + crypto data (USDC/x402) and makes no claim about it beyond what these checks measured.