Remote MCP · Endpoint

Tenjin MCP server

No. Tenjin answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://tenjin.sh/api/mcp

The last check completed an MCP handshake.

Registry name
blog.tenjin/tenjin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search, read & publish paid essays. Pay-per-read in USDC on Base (x402); wallet-only, no account.
Listing
From the official MCP registry (active).
Recent checks of Tenjin
CheckedResultHandshake
1 day agoHandshake completed74 ms
3 days agoHandshake completed88 ms
5 days agoHandshake completed77 ms
7 days agoHandshake completed153 ms
8 days agoHandshake completed103 ms
9 days agoHandshake completed89 ms
11 days agoHandshake completed89 ms
13 days agoHandshake completed91 ms
15 days agoHandshake completed98 ms
17 days agoHandshake completed219 ms
18 days agoHandshake completed111 ms
19 days agoHandshake completed97 ms
20 days agoHandshake completed218 ms
21 days agoHandshake completed228 ms
21 days agoHandshake completed268 ms
23 days agoHandshake completed2.16 s
24 days agoHandshake completed87 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 Tenjin and makes no claim about it beyond what these checks measured.