Is the Imoldyoung E Invoice MCP server down?

mcp-registry/io.github.imoldyoung/e-invoice · v0.2.0

healthy
Last checked 2026-10-26 19:33 UTC · handshake 151ms

As of 2026-10-26 19:33 UTC, the Imoldyoung E Invoice MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,884
outages (90d)
0
tools
4

对话式开具电子发票(数电票):第一步免费生成发票草稿(自动校验税号、税率并算税),第二步确认开票(需 App Key,按张计费),支持开票记录查询。

Point your MCP client at this streamable-http endpoint: https://e-invoice-mcp.601096790.workers.dev/mcp

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 2 warning(s) across 4 tool(s); ~486 tokens of tool definitions.
Scores higher than 33% of 15,762 MCP servers Glimind has audited.
Its tool list costs an agent ~486 tokens per session — lighter than 90% of servers.
81 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: invoice_confirm_issue, invoice_create_draft, invoice_query, service_info

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: invoice_create_draft

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.imoldyoung%2Fe-invoice/fixes

invoice_create_draft 1 change
{
  "name": "invoice_create_draft",
  "description": "第 1 步:把订单信息(文字描述或结构化明细)生成发票草稿。自动校验购方税号格式、税率合法性、金额上限,并自动计算税额与价税合计。草稿免费生成,24 小时内有效。",
  "inputSchema": {
    "type": "object",
    "required": [
      "buyer_name",
      "items"
    ],
    "properties": {
      "items": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "name",
            "amount"
          ],
          "properties": {
            "name": {
              "type": "string",
              "description": "项目名称,如 *餐饮服务*餐费"
            },
            "unit": {
              "type": "string",
              "description": "单位,如 份/次"
            },
            "amount": {
              "type": "number",
              "description": "不含税金额(元)"
            },
            "quantity": {
              "type": "number",
              "description": "数量,默认 1"
            },
            "tax_rate": {
              "type": "number",
              "description": "税率,如 0.01、0.06、0.13"
            }
          }
        },
        "description": "商品/服务明细"
      },
      "remark": {
        "type": "string",
        "description": "发票备注(如订单号、项目名)"
      },
      "buyer_name": {
        "type": "string",
        "description": "购方名称(企业/个人抬头)"
      },
      "buyer_tax_id": {
        "type": "string",
        "description": "购方税号(统一社会信用代码,15/18/20 位);个人开票传空"
      },
      "invoice_type": {
        "enum": [
          "普通发票",
          "专用发票"
        ],
        "type": "string",
        "description": "发票类型,默认普通发票(数电普票)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
invoice_query 1 change
{
  "name": "invoice_query",
  "description": "查询当前 App Key 名下的发票草稿与开票记录(需 App Key)。可按状态筛选:draft(草稿)/ issued(已开具)/ all。",
  "inputSchema": {
    "type": "object",
    "properties": {
      "status": {
        "enum": [
          "draft",
          "issued",
          "all"
        ],
        "type": "string",
        "description": "筛选状态,默认 all"
      },
      "date_to": {
        "type": "string",
        "description": "结束日期 YYYY-MM-DD(可选)"
      },
      "date_from": {
        "type": "string",
        "description": "起始日期 YYYY-MM-DD(可选)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
service_info 1 change
{
  "name": "service_info",
  "description": "查看服务介绍、计费方式与联系方式(无需 App Key,免费)。",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.imoldyoung/e-invoice"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.imoldyoung/e-invoice"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imoldyoung%2Fe-invoice.svg)](https://glimind.com/server/mcp-registry%2Fio.github.imoldyoung%2Fe-invoice?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.imoldyoung%2Fe-invoice?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imoldyoung%2Fe-invoice.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imoldyoung%2Fe-invoice.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.imoldyoung%2Fe-invoice?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8d8473a259f8fd96…, first seen 2026-10-17, included at leaf 13269 of 75,060. Version history · verify what your client received.

Tools (4)

Compare: most reliable finance servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Imoldyoung E Invoice MCP server down right now?

As of 2026-10-26 19:33 UTC, the Imoldyoung E Invoice MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Imoldyoung E Invoice MCP server provide?

Imoldyoung E Invoice MCP server advertises 4 tools, including invoice_confirm_issue, invoice_create_draft, invoice_query, service_info.

How do I install Imoldyoung E Invoice MCP server?

Point your MCP client at this streamable-http endpoint: https://e-invoice-mcp.601096790.workers.dev/mcp

Is the Imoldyoung E Invoice MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Imoldyoung E Invoice MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve