Remote MCP · Endpoint
AI 开票助手 · 电子发票开具 MCP server
No. AI 开票助手 · 电子发票开具 answered an MCP handshake 55 minutes ago.
UpLast checked 55 minutes ago
Server URL
https://e-invoice-mcp.601096790.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.imoldyoung/e-invoice
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 35 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 对话式开具电子发票（数电票）：第一步免费生成发票草稿（自动校验税号、税率并算税），第二步确认开票（需 App Key，按张计费），支持开票记录查询。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 55 minutes ago | Handshake completed | 35 ms |
| 1 day ago | Handshake completed | 47 ms |
| 2 days ago | Handshake completed | 301 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 AI 开票助手 · 电子发票开具 and makes no claim about it beyond what these checks measured.