Remote MCP · Endpoint

io.github.yukihamada/tokkyo-maru MCP server

No. io.github.yukihamada/tokkyo-maru answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tokkyo-maru.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.yukihamada/tokkyo-maru
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
275 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
特許まる — 発明を入れるだけで特許性の事前診断・明細書骨子・新規性喪失(特許法30条)判定。本人/弁理士の出願支援(代理しない)。
Listing
From the official MCP registry (active).
Recent checks of io.github.yukihamada/tokkyo-maru
CheckedResultHandshake
1 hour agoHandshake completed275 ms
9 days agoHandshake completed226 ms
10 days agoHandshake completed202 ms
11 days agoHandshake completed202 ms
12 days agoHandshake completed208 ms
14 days agoHandshake completed212 ms
14 days agoHandshake completed195 ms
15 days agoHandshake completed187 ms
17 days agoHandshake completed5.03 s
19 days agoHandshake completed4.92 s
21 days agoHandshake completed204 ms
24 days agoHandshake completed197 ms
26 days agoHandshake completed200 ms
28 days agoHandshake completed207 ms

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

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 io.github.yukihamada/tokkyo-maru and makes no claim about it beyond what these checks measured.