InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server
com.run402.invoiceguard-ai/mcpinvoiceguard-ai.run402.comstreamable-httpv4.0.0Scanned
Cross-Border B2B Invoice Generator, W-8BEN / EU VAT Verifier & Fraud Scanner ($1 USDC, $950 Buyout).
4 tools: 1 do something that can't be undone, 2 change things and 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
With Anlyon
1 tool here does something that can't be undone. Govern it.
- 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 InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server can do
The InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server is published by invoiceguard-ai.run402.com, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (verify_payment_and_unlock) and create or change data (2 tools: audit_domain and submit_buyer_offer), but cannot delete data. 1 tool only reads.
1 tool reads private data (get_package_manifest).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 17, 2026, version 4.0.0.
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.
4 tools
Can't be undone 1Claude Code: ask
verify_payment_and_unlockVerifies a Base USDC/USDT or Tonkeeper TON/USDT-TON payment (by tx_hash, wallet address, or order reference) and returns the full unredacted Pro deliverables and 6-file download pa…No findings
Why it is in this group
- The name "verify_payment_and_unlock" says "payment": a word that usually means money moves, which cannot be taken back.
- The name "verify_payment_and_unlock" also says "unlock": a word for a change.
Description, as the server wrote it Verifies a Base USDC/USDT or Tonkeeper TON/USDT-TON payment (by tx_hash, wallet address, or order reference) and returns the full unredacted Pro deliverables and 6-file download pack.
Changes things 2Claude Code: ask
audit_domain6-Agent SaaS Contract, GDPR Art.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 6-Agent SaaS Contract, GDPR Art. 28 DPA & EU AI Act Auditor — scans any public HTTPS domain and returns deterministic readiness scores and remediation artifacts.
submit_buyer_offerCreates an instant $1 Flash Trial or custom buyout settlement link (Tonkeeper TON / Base USDC).No findings
Why it is in this group
- The name "submit_buyer_offer" says "submit": a word for a change.
Description, as the server wrote it Creates an instant $1 Flash Trial or custom buyout settlement link (Tonkeeper TON / Base USDC).
Only reads 1Show 1 read-only tool
get_package_manifestReturns SHA-256 checksums, byte sizes, and file trees for all turnkey SaaS source .ZIP archives and Executive Digital Pack documents.Reads private dataNo findings
Why it is in this group
- The name "get_package_manifest" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "file": it reads files.
Description, as the server wrote it Returns SHA-256 checksums, byte sizes, and file trees for all turnkey SaaS source .ZIP archives and Executive Digital Pack documents.
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 20, 2026, 19:25 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 503
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: initialize answered HTTP 503.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 503
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2024-11-05 to none
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.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 503
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2024-11-05 to none
Install
Pinned to version 4.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http invoiceguard-ai https://invoiceguard-ai.run402.com/api/mcpclaude mcp add --transport http invoiceguard-ai https://invoiceguard-ai.run402.com/api/mcpRun 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__invoiceguard-ai__get_package_manifest"
],
"ask": [
"mcp__invoiceguard-ai__audit_domain",
"mcp__invoiceguard-ai__verify_payment_and_unlock",
"mcp__invoiceguard-ai__submit_buyer_offer"
],
"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 invoiceguard-ai. Review it before you use it.
Capability tags behind 1 rule
- mcp__invoiceguard-ai__get_package_manifest 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/com.run402.invoiceguard-ai/mcp/verify?hash=d69e4d6257878ac5ac893f28c8b0db10e121dc73a44de1ef328e00c2a23e28f3" | jq -e '.changed == false'Pinned hash d69e4d625787, from Nov 17, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.run402.invoiceguard-ai/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.run402.invoiceguard-ai/mcp)Source: MCP Registry. Synced Oct 21, 2026, 18:02 UTC.
InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: verify_payment_and_unlock.
What tools does the InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server have?
- 4 tools: 1 irreversible, 2 write, 1 read. verify_payment_and_unlock, audit_domain, submit_buyer_offer and get_package_manifest.
Does the InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the InvoiceGuard AI v4.0 — B2B Invoice & Tax Compliance Verifier MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.