mcp-ezpay-einvoice: Instructions file for Claude Code

CLAUDE.md

mcp-ezpay-einvoice CLAUDE.md is an instructions file for Claude Code from asgard-ai-platform/mcp-ezpay-einvoice. It costs 641 tokens per session, scanned A, original, MIT.

A local connection to Taiwan’s ezPay electronic-invoice service. It provides tools for issuing, activating, cancelling, and checking invoices and related allowances.

In plain words
What is it for?
Managing the electronic-invoice lifecycle through an AI agent, after configuring the merchant credentials.
Why use it?
It removes the need to manually construct ezPay requests and handle their required encryption and credentials.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is asgard-ai-platform/mcp-ezpay-einvoice's own configuration. It tells Claude Code how to work on mcp-ezpay-einvoice itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-ezpay-einvoice configures →

Reuse

Borrowing it

Nothing to install: this file belongs to asgard-ai-platform/mcp-ezpay-einvoice. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/asgard-ai-platform/mcp-ezpay-einvoice/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/asgard-ai-platform/mcp-ezpay-einvoice

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-ezpay-einvoice CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/asgard-ai-platform/mcp-ezpay-einvoice/claude-md/github.svg)](https://agentmods.dev/instructions/asgard-ai-platform/mcp-ezpay-einvoice/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/asgard-ai-platform/mcp-ezpay-einvoice/claude-md"><img src="https://agentmods.dev/badge/instructions/asgard-ai-platform/mcp-ezpay-einvoice/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcp-ezpay-einvoice CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/asgard-ai-platform/mcp-ezpay-einvoice/claude-md"><img src="https://agentmods.dev/badge/instructions/asgard-ai-platform/mcp-ezpay-einvoice/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 641 This file is loaded in full into every session.
When invoked 641 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00641 $0.00641
Opus 5 $0.00320 $0.00320
Sonnet 5 $0.00128 $0.00128
Haiku 4.5 $0.00064 $0.00064

Measured 9d ago against content hash b438595b9c75, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

mcp-ezpay-einvoice CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

mcp-ezpay-einvoice

Overview

MCP server for Taiwan's ezPay e-invoice API. Exposes 7 AI-callable tools covering the full invoice lifecycle (issue, trigger, void) and allowance lifecycle (issue, trigger, void), plus querying. Uses AES-256-CBC encryption for the ezPay form POST protocol.

Setup

uv venv && source .venv/bin/activate
uv pip install -e .
cp .env.example .env
# Set EZPAY_MERCHANT_ID, EZPAY_HASH_KEY, EZPAY_HASH_IV in .env

Run

python mcp_server.py

Test

# Validate credentials and connectivity
python scripts/auth/test_connection.py

# Run all 7 tool E2E tests
python tests/test_all_tools.py

Architecture

stdio (JSON-RPC 2.0)
  -> mcp_server.py (entry point, imports tools/invoice_tools.py to trigger registration)
    -> app.py (FastMCP("mcp-ezpay-einvoice") singleton)
      -> tools/invoice_tools.py (7 @mcp.tool() decorated functions)
        -> connectors/ezpay_client.py (encrypted form POST: inject fields, AES encrypt, HTTP POST)
          -> auth/ezpay_crypto.py (AES-256-CBC encrypt, PKCS7 pad, CheckCode SHA-256)
            -> config/settings.py (endpoints, URL builder, env var credentials)

Key Patterns

  • Singleton: app.py creates the FastMCP instance, imported by tools and server
  • Decorator registration: @mcp.tool() with Pydantic Field() for typed parameters
  • Side-effect import: mcp_server.py imports tools.invoice_tools to trigger registration
  • Encrypted protocol: All API params are URL-encoded, PKCS7-padded, AES-256-CBC encrypted, hex-encoded
  • Dual environment: EZPAY_IS_PRODUCTION switches between test and production base URLs

Adding a New Tool

  1. Add the function in tools/invoice_tools.py (or create a new tools/*_tools.py module)
  2. Use the connector: from connectors.ezpay_client import ezpay_post
  3. Decorate with @mcp.tool() and use Field() for parameter descriptions
  4. If new module, add import tools.{module} # noqa: F401 in mcp_server.py
  5. Add a test case in tests/test_all_tools.py

Read the full file on GitHub · 60 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 60 lines · 641 tokens per session scan A b438595b9c75

Subscribe to this mod's changes

mcp-ezpay-einvoice CLAUDE.md is an instructions file published in the GitHub repository asgard-ai-platform/mcp-ezpay-einvoice (1 stars, last pushed 5mo ago), licensed MIT. It adds 641 tokens to every session, about $0.0032 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

vibetags com-example-service-OrderService.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for orderservice, rules for method calculatetax, rules for method processpayment, rules for method validateorder and context & focus.

PIsberg/vibetags · 553 tokens

vibetags com-example-service-EvidenceBasedShowcase.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for evidencebasedshowcase, generated — edit the source, rules for field settledorderids, rules for method totalwithtax and rules for method refreshcartbadge.

PIsberg/vibetags · 443 tokens

vibetags com-example-strategy-impl-CreditCardStrategy.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for creditcardstrategy, rules for method executepayment, rules for method validatepaymentmethod, pii / privacy guardrails and rules for field cardnumber.

PIsberg/vibetags · 236 tokens

vibetags com-example-payment-PaymentProcessor.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for paymentprocessor, locked status, implementation tasks and performance constraints.

PIsberg/vibetags · 138 tokens

vibetags com-example-service-TransactionalPaymentService.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for transactionalpaymentservice and strict exception handling.

PIsberg/vibetags · 104 tokens

vibetags com-example-payment-PaymentDetails.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for paymentdetails and strict type safety.

PIsberg/vibetags · 105 tokens