Remote MCP · Endpoint

Linkora Source MCP server

No. Linkora Source answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://linkorasource.com/mcp

The last check completed an MCP handshake.

Registry name
com.linkorasource/sourcing
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
607 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
China sourcing, inspection and supplier verification: published rates, scope and fee estimates.
Listing
From the official MCP registry (active).
Recent checks of Linkora Source
CheckedResultHandshake
5 hours agoHandshake completed607 ms
9 days agoHandshake completed124 ms
10 days agoHandshake completed679 ms
11 days agoHandshake completed775 ms
12 days agoHandshake completed382 ms
14 days agoHandshake completed412 ms
14 days agoHandshake completed466 ms
15 days agoHandshake completed1.07 s
17 days agoHandshake completed899 ms
19 days agoHandshake completed372 ms
21 days agoHandshake completed948 ms
24 days agoHandshake completed754 ms
26 days agoHandshake completed60 ms
28 days agoHandshake completed423 ms

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

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