Remote MCP · Endpoint

Rafid Intelligence Network MCP server

No. Rafid Intelligence Network answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.rafidsystem.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.iabdullahm/rafid-agent-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
66 ms
Tools exposed
74 tools
Uptime, last 30 days
77.8% from 18 checks
Described by its publisher as
Paid intelligence tools for AI agents across risk, finance, property, logistics and more.
Website
https://api.rafidsystem.com/tools?utm_source=official_mcp_registry&utm_medium=agent_directory&utm_campaign=rafid_agent_distribution&distribution_experiment_id=dist_2026_mcp_registry_01
Repository
https://github.com/iabdullahm/rafid-agent-api
Listing
From the official MCP registry (active).
Recent checks of Rafid Intelligence Network
CheckedResultHandshake
1 hour agoHandshake completed66 ms
1 day agoHandshake completed73 ms
2 days agoHandshake completed343 ms
3 days agoHandshake completed98 ms
4 days agoHandshake completed140 ms
5 days agoHandshake completed63 ms
7 days agoHandshake completed46 ms
10 days agoHandshake completed80 ms
12 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed73 ms
17 days agoHandshake completed99 ms
19 days agoHandshake completed110 ms
21 days agoHandshake completed72 ms
23 days agoHandshake completed66 ms
25 days agoHandshake completed317 ms
26 days agoFailed - the server returned an HTTP error—
28 days agoFailed - the server returned an HTTP error—
29 days agoFailed - the server returned an HTTP error—

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

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 Rafid Intelligence Network and makes no claim about it beyond what these checks measured.