Invoice reading MCP server
io.github.ladanyin/invoice-readingladanyinstreamable-httpv1.0.1Scanned
Read an invoice into seller, tax id, date, and amounts.
1 tool: 1 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Invoice reading MCP server can do
The Invoice reading MCP server is published by the GitHub account ladanyin. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (parse_invoice).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Only reads 1Show 1 read-only tool
parse_invoiceRead one text invoice into seller, tax ids, date, currency, and net, VAT, and gross amounts.Reads private dataNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- private-dataThe input names a file (input.file_text), and the tool reads: it reads files.
Description, as the server wrote it Read one text invoice into seller, tax ids, date, currency, and net, VAT, and gross amounts. Returns credits_remaining and fields. Amounts are digit strings, not numbers. Costs 0.15 credit only when text is extracted. A missing key, a missing file, or a PDF with no text layer (error no_text_extracted) is not charged. Send file_text when you already have the invoice text, or file_base64 for a text PDF, and set filename so .pdf is read as PDF and .txt as text. Do not send a photo or a scanned image-only PDF. vendor_name is the first line and can be wrong. Key: https://firm.bestsmartgoods.com/signup
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:24 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Posture changes
- Nov 10, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:parse_invoiceOnly readstitledescriptioninputSchemaannotations
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Protocol version: none -> 2025-06-18 (and 1 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http invoice-reading https://bill.bestsmartgoods.com/mcp --header 'X-API-Key: <your-x-api-key>'claude mcp add --transport http invoice-reading https://bill.bestsmartgoods.com/mcp --header 'X-API-Key: <your-x-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__invoice-reading__parse_invoice"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as invoice-reading. Review it before you use it.
Capability tags behind 1 rule
- mcp__invoice-reading__parse_invoice private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ladanyin/invoice-reading/verify?hash=c01401fcd7a95b4e036aacf7cdf3a0503d73f2a73294cec59a465d27331fc780" | jq -e '.changed == false'Pinned hash c01401fcd7a9, from Nov 17, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ladanyin/invoice-reading/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ladanyin/invoice-reading)Source: MCP Registry · repository. Synced Nov 3, 2026, 20:17 UTC.
Invoice reading MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Invoice reading MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Invoice reading MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Invoice reading MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Invoice reading MCP server have?
- 1 tool: 1 read. parse_invoice.
Does the Invoice reading MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Invoice reading MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Invoice reading MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.