Remote MCP · Endpoint

Torque MCP server

No. Torque answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.torque.fi/api/mcp

The last check completed an MCP handshake.

Registry name
fi.torque.app/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Unified book, desk, calendar, prices, and rates for agents. Sign up, pay, pull.
Listing
From the official MCP registry (active).
Recent checks of Torque
CheckedResultHandshake
1 hour agoHandshake completed97 ms
2 days agoHandshake completed96 ms
4 days agoHandshake completed84 ms
5 days agoHandshake completed123 ms
7 days agoHandshake completed542 ms
8 days agoHandshake completed71 ms
9 days agoHandshake completed73 ms
12 days agoHandshake completed83 ms
13 days agoHandshake completed194 ms
15 days agoHandshake completed145 ms
16 days agoHandshake completed76 ms
18 days agoHandshake completed94 ms
19 days agoHandshake completed112 ms
20 days agoHandshake completed87 ms
20 days agoHandshake completed72 ms
21 days agoHandshake completed624 ms
22 days agoHandshake completed145 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.

Listing data comes from the official MCP registry. Glide is not affiliated with Torque and makes no claim about it beyond what these checks measured.