Remote MCP · Endpoint

Linkora Source MCP server

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

UpLast checked 4 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
754 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
4 hours agoHandshake completed754 ms
2 days agoHandshake completed60 ms
4 days agoHandshake completed423 ms
6 days agoHandshake completed453 ms
8 days agoHandshake completed1.01 s
10 days agoHandshake completed823 ms
12 days agoHandshake completed924 ms
13 days agoHandshake completed489 ms
15 days agoHandshake completed395 ms
16 days agoHandshake completed446 ms
18 days agoHandshake completed432 ms
20 days agoHandshake completed391 ms
21 days agoHandshake completed561 ms
23 days agoHandshake completed732 ms

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

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.