Remote MCP · Endpoint
Tenjin MCP server
No. Tenjin answered an MCP handshake 1 hour ago.
UpLast checked 1 hour 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
- 189 ms
- Tools exposed
- 23 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Search, read & publish paid essays. Pay-per-read in USDC on Base (x402); wallet-only, no account.
- Website
- https://tenjin.sh/agents
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 189 ms |
| 18 hours ago | Handshake completed | 101 ms |
| 2 days ago | Handshake completed | 110 ms |
| 3 days ago | Handshake completed | 272 ms |
| 4 days ago | Handshake completed | 173 ms |
| 5 days ago | Handshake completed | 271 ms |
| 6 days ago | Handshake completed | 199 ms |
| 8 days ago | Handshake completed | 159 ms |
| 10 days ago | Handshake completed | 84 ms |
| 13 days ago | Handshake completed | 116 ms |
| 15 days ago | Handshake completed | 255 ms |
| 17 days ago | Handshake completed | 80 ms |
| 19 days ago | Handshake completed | 72 ms |
| 21 days ago | Handshake completed | 74 ms |
| 23 days ago | Handshake completed | 88 ms |
| 25 days ago | Handshake completed | 77 ms |
| 27 days ago | Handshake completed | 153 ms |
| 28 days ago | Handshake completed | 103 ms |
| 29 days ago | Handshake completed | 89 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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.