Invoice reading

io.github.ladanyin/invoice-readingladanyinstreamable-httpv1.0.0Scanned 2 hours ago

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

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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 1Looks things up and changes nothing.Show 1 read-only tool

parse_invoiceRead an invoice into structured fields: seller, tax id, date, 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 an invoice into structured fields: seller, tax id, date, amounts. Costs 0.15 credit. Key: https://firm.bestsmartgoods.com/signup

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.; parse_invoice
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.

Sign-in required, no OAuth metadata

Looked at Nov 3, 2026, 01:21 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 401
tools/list served without credentials: no
Tools that change things, listed without credentials: 0
Protocol version: not observed
WWW-Authenticate on 401: yes
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

WarnThe whole server
The endpoint asks for credentials (HTTP 401) but publishes no RFC 9728 protected resource metadata: no resource_metadata in WWW-Authenticate and no document at /.well-known/oauth-protected-resource.
Matched text
https://bill.bestsmartgoods.com/mcp: initialize answered HTTP 401, with a WWW-Authenticate header
What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. 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.

.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

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://anlyon.dev/api/v1/servers/io.github.ladanyin/invoice-reading/verify?hash=8c9eecf26d3d6b889428176d0b5abefc4975cf1291192b5e7837ed8514961524" | jq -e '.changed == false'

Pinned hash 8c9eecf26d3d, from Nov 2, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.ladanyin/invoice-reading/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/io.github.ladanyin/invoice-reading.svg)](https://anlyon.dev/servers/io.github.ladanyin/invoice-reading)

Source: MCP Registry · repository. Synced Nov 2, 2026, 23:17 UTC.