Remote MCP · Endpoint

KEVAREMESH AI Procurement Gateway MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://kevaremesh-web.vercel.app/api/x402/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.cirralink-stack/kevaremesh-gateway
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
66.7% from 18 checks
Described by its publisher as
AI procurement for web search, news, finance, blockchain, social, enrichment and travel APIs.
Website
https://kevaremesh-web.vercel.app/
Repository
https://github.com/cirralink-stack/cirralink
Listing
From the official MCP registry (active).
Recent checks of KEVAREMESH AI Procurement Gateway
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed304 ms
10 days agoHandshake completed247 ms
12 days agoHandshake completed223 ms
15 days agoHandshake completed242 ms
17 days agoHandshake completed272 ms
19 days agoHandshake completed214 ms
21 days agoHandshake completed210 ms
23 days agoHandshake completed582 ms
25 days agoHandshake completed197 ms
26 days agoHandshake completed307 ms
28 days agoHandshake completed234 ms
29 days agoHandshake completed179 ms

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 KEVAREMESH AI Procurement Gateway and makes no claim about it beyond what these checks measured.