AI 开票助手 · 电子发票开具
REMOTE · E-INVOICE-MCP.601096790.WORKERS.DEV · SCANNED SEP 20
对话式开具电子发票（数电票）：第一步免费生成发票草稿（自动校验税号、税率并算税），第二步确认开票（需 App Key，按张计费），支持开票记录查询。
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 388 tokens (~97/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the AI 开票助手 · 电子发票开具 MCP server?
AI 开票助手 · 电子发票开具 is a hosted endpoint at https://e-invoice-mcp.601096790.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · e-invoice-mcp.601096790.workers.dev
claude mcp add --transport http imoldyoung-e-invoice 'https://e-invoice-mcp.601096790.workers.dev/mcp'
{
"mcpServers": {
"imoldyoung-e-invoice": {
"url": "https://e-invoice-mcp.601096790.workers.dev/mcp"
}
}
} {
"servers": {
"imoldyoung-e-invoice": {
"type": "http",
"url": "https://e-invoice-mcp.601096790.workers.dev/mcp"
}
}
} [mcp_servers.imoldyoung-e-invoice] url = "https://e-invoice-mcp.601096790.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"imoldyoung-e-invoice": {
"type": "remote",
"url": "https://e-invoice-mcp.601096790.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add imoldyoung-e-invoice --url 'https://e-invoice-mcp.601096790.workers.dev/mcp' --transport streamable-http
mcp_servers:
imoldyoung-e-invoice:
url: "https://e-invoice-mcp.601096790.workers.dev/mcp" {
"McpServers": {
"imoldyoung-e-invoice": {
"Transport": "http",
"Url": "https://e-invoice-mcp.601096790.workers.dev/mcp"
}
}
} assistant mcp add imoldyoung-e-invoice -t streamable-http -u 'https://e-invoice-mcp.601096790.workers.dev/mcp'
{
"mcpServers": {
"imoldyoung-e-invoice": {
"type": "http",
"url": "https://e-invoice-mcp.601096790.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://e-invoice-mcp.601096790.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=601096790.workers.dev | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 80e2bdd14125eef80efec68efeb7a5d1 |
| SANs: 601096790.workers.dev, *.601096790.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of e-invoice-mcp.601096790.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://e-invoice-mcp.601096790.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://e-invoice-mcp.601096790.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
invoice_confirm_issue ~93
第 2 步：确认开具草稿。传入 invoice_create_draft 返回的 draft_id，正式提交开票（需 App Key，按张计费）。开票后生成发票号码与交付信息。
| Name | Type | Req | Description |
|---|---|---|---|
| draft_id | string | yes | 草稿 ID（invoice_create_draft 返回） |
| payer_email | string | – | 接收发票文件的邮箱（可选） |
No output schema declared.
No examples provided.
invoice_create_draft ~174
第 1 步：把订单信息（文字描述或结构化明细）生成发票草稿。自动校验购方税号格式、税率合法性、金额上限，并自动计算税额与价税合计。草稿免费生成，24 小时内有效。
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_name | string | yes | 购方名称（企业/个人抬头） |
| buyer_tax_id | string | – | 购方税号（统一社会信用代码，15/18/20 位）；个人开票传空 |
| invoice_type | string | – | 发票类型，默认普通发票（数电普票） |
| items | array | yes | 商品/服务明细 |
| remark | string | – | 发票备注（如订单号、项目名） |
No output schema declared.
No examples provided.
invoice_query ~97
查询当前 App Key 名下的发票草稿与开票记录（需 App Key）。可按状态筛选：draft（草稿）/ issued（已开具）/ all。
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | 起始日期 YYYY-MM-DD（可选） |
| date_to | string | – | 结束日期 YYYY-MM-DD（可选） |
| status | string | – | 筛选状态，默认 all |
No output schema declared.
No examples provided.
service_info ~24
查看服务介绍、计费方式与联系方式（无需 App Key，免费）。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the AI 开票助手 · 电子发票开具 MCP server?
AI 开票助手 · 电子发票开具 is an MCP server listed in the public MCP registry as io.github.imoldyoung/e-invoice. 对话式开具电子发票（数电票）：第一步免费生成发票草稿（自动校验税号、税率并算税），第二步确认开票（需 App Key，按张计费），支持开票记录查询。 This page covers its hosted endpoint (https://e-invoice-mcp.601096790.workers.dev/mcp).
Is the AI 开票助手 · 电子发票开具 MCP server safe to use?
AI 开票助手 · 电子发票开具 scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI 开票助手 · 电子发票开具 MCP server expose?
AI 开票助手 · 电子发票开具 exposes 4 tools: service_info, invoice_create_draft, invoice_confirm_issue, invoice_query. Their descriptions and schemas cost roughly 388 tokens of context every time the server is loaded.
Does the AI 开票助手 · 电子发票开具 MCP server require authentication?
No. We connected to AI 开票助手 · 电子发票开具 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI 开票助手 · 电子发票开具 MCP server still maintained?
AI 开票助手 · 电子发票开具 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.