Remote MCP · Endpoint

Loxo MCP Server and API by Cotlet MCP server

No. Loxo MCP Server and API by Cotlet answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://cotlet.dev/mcp/v1/loxo

The last check completed an MCP handshake.

Registry name
dev.cotlet/loxo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
35 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Loxo recruiting CRM platform MCP server: list jobs, read a job pipeline, search people.
Listing
From the official MCP registry (active).
Recent checks of Loxo MCP Server and API by Cotlet
CheckedResultHandshake
5 hours agoHandshake completed151 ms
4 days agoHandshake completed214 ms
7 days agoFailed - the check failed for an unclassified reason—

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 2 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 Loxo MCP Server and API by Cotlet and makes no claim about it beyond what these checks measured.