Fawtar MCP server
app.fawtar/fawtarfawtar.appstreamable-httpv1.3.0Scanned
ZATCA-compliant Saudi invoicing. Free 24h sandbox key, no signup; 1,000 API writes for 99 SAR.
6 tools: 1 do something that can't be undone, 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- 1 finding
Tools listed without sign-in. 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 Fawtar MCP server can do
The Fawtar MCP server is published by fawtar.app, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (fawtar_vat_summary) and create or change data (3 tools: fawtar_create, fawtar_create_invoice and fawtar_outstanding), but cannot delete data. 2 tools only read.
2 tools can send data out of your system (fawtar_create_invoice and fawtar_vat_summary).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.3.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.
6 tools
Can't be undone 1Claude Code: ask
fawtar_vat_summaryOutput VAT charged on sales, input VAT paid on expenses, and the net payable for a date range — the figures a VAT return is built from.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "fawtar_vat_summary" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Output VAT charged on sales, input VAT paid on expenses, and the net payable for a date range — the figures a VAT return is built from. Recoverable input VAT only; expenses marked non-recoverable are excluded, as they must be.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
Changes things 3Claude Code: ask
fawtar_createCreate a customer, product, vendor, employee, asset or other simple record.No findings
Why it is in this group
- The name "fawtar_create" says "create": a word for a change.
Description, as the server wrote it Create a customer, product, vendor, employee, asset or other simple record. Use fawtar_create_invoice for invoices — issuing one claims a sequential number, computes VAT, writes the QR and posts to the ledger, none of which a generic insert does. Creatable resources: orders, customers, products, categories, product_unit_types, vendors, inventories, accounts, pos_tables.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
fawtar_create_invoiceIssue a tax or ordinary invoice.Can send data outNo findings
Why it is in this group
- The name "fawtar_create_invoice" says "create": a word for a change.
What it can reach
- outboundThe input takes a destination (input.buyer.phone): what the tool writes goes there.
Description, as the server wrote it Issue a tax or ordinary invoice. This is a real financial document: it takes the next sequential number, computes VAT, generates the ZATCA QR code and posts to the general ledger. It cannot be edited afterwards — correct it with a credit note. Confirm the amounts with the user before calling. Use taxTreatment "tax" for a VAT-registered business, "ordinary" for one that is not registered. Use type "simplified" for individuals, "standard" for businesses (which requires the buyer's VAT number).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
fawtar_outstandingEvery unpaid issued invoice with its remaining balance and how many days it is overdue, newest due first, plus the totals.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Every unpaid issued invoice with its remaining balance and how many days it is overdue, newest due first, plus the totals. This is the answer to 'who owes me money' without composing filters by hand.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
Only reads 2Show 2 read-only tools
fawtar_getFetch a single record by id.No findings
Why it is in this group
- The name "fawtar_get" says "get": a word for reading.
Description, as the server wrote it Fetch a single record by id. For invoices this also returns the line items and the public share link.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
fawtar_listList records from any Fawtar resource, with filtering, sorting and paging.No findings
Why it is in this group
- The name "fawtar_list" says "list": a word for reading.
Description, as the server wrote it List records from any Fawtar resource, with filtering, sorting and paging. Resources: - invoices: إصدار الفواتير الضريبية وقراءتها. - credit_notes: تصحيح فاتورة صادرة بالخصم. - debit_notes: تصحيح فاتورة صادرة بالزيادة. - quotes: عروض الأسعار قبل تحوّلها إلى فواتير. - orders: طلبات المتجر قبل الفوترة. - customers: بيانات العملاء وأرقامهم الضريبية والعنوان الوطني. - products: المنتجات والخدمات وأسعارها. - categories: تصنيفات المنتجات. - product_unit_types: وحدات بيع المنتجات. - vendors: بيانات الموردين. - bills: فواتير الموردين ببنودها. - simple_bills: مصروف بمبلغ واحد دون بنود. - bill_payments: سداد فواتير الموردين. - inventories: المستودعات والفروع. - inventory_levels: الكميات المتاحة لكل منتج في كل مستودع. - inventory_adjustments: زيادة أو إنقاص كمية بسبب جرد أو تلف. - inventory_transfers: نقل كمية بين مستودعين. - invoice_payments: تسجيل دفعة على فاتورة. - receipts: الدفعات نفسها بصيغة سند القبض. - accounts: شجرة الحسابات وأنواعها. - journal_entries: القيود المرحّلة إلى دفتر الأستاذ. - recurring_journals: جدولة القيود التي تتكرر كل فترة. - employees: بيانات الموظفين ورواتبهم وبدلاتهم. - payroll_runs: المسيّرات الشهرية وإجمالياتها. - payslips: قسيمة كل موظف داخل المسيّر. - assets: سجل الأصول وإهلاكها. - pos_tables: طاولات صالة المطعم. - pos_orders: طلبات نقاط البيع المفتوحة والمحصّلة. Filters use the form {"field_predicate": "value"} — for example {"status_eq": "issued"} or {"issued_at_gteq": "2026-01-01"}. Predicates: eq, not_eq, cont, start, end, gt, gteq, lt, lteq, in, null. Only fields the resource allows are honoured; anything else is ignored.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
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 private-data or untrusted-input.
- Reads private data0
- 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 out2
- 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, 18:29 UTC, unchanged since Nov 13, 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
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://fawtar.app/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://fawtar.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://fawtar.app/api/mcp: tools/list returned 6 tools to an anonymous client, including fawtar_vat_summary (irreversible), fawtar_create (write), fawtar_create_invoice (write), fawtar_outstanding (write)
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 4
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://fawtar.app/.well-known/oauth-protected-resource/api/mcp to none
Findings
Matches of fixed checks, with the text they matched.
The server marks "fawtar_vat_summary" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 4 (and 3 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 4
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://fawtar.app/.well-known/oauth-protected-resource/api/mcp to none
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fawtar https://fawtar.app/api/mcpclaude mcp add --transport http fawtar https://fawtar.app/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__fawtar__fawtar_list",
"mcp__fawtar__fawtar_get"
],
"ask": [
"mcp__fawtar__fawtar_create",
"mcp__fawtar__fawtar_create_invoice",
"mcp__fawtar__fawtar_outstanding",
"mcp__fawtar__fawtar_vat_summary"
],
"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 fawtar. Review it before you use it.
Capability tags behind 2 rules
- mcp__fawtar__fawtar_create_invoice outbound
- mcp__fawtar__fawtar_vat_summary outbound
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/app.fawtar/fawtar/verify?hash=6f340f013cd8a71ff220b9b3a69222b9908f30754720cc2a9a67cc0ff809d236" | jq -e '.changed == false'Pinned hash 6f340f013cd8, from Nov 20, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.fawtar/fawtar/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.fawtar/fawtar)Source: MCP Registry. Synced Nov 6, 2026, 18:17 UTC.
Fawtar MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fawtar MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Fawtar MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Fawtar MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: fawtar_vat_summary.
What tools does the Fawtar MCP server have?
- 6 tools: 1 irreversible, 3 write, 2 read. fawtar_vat_summary, fawtar_create, fawtar_create_invoice, fawtar_outstanding, fawtar_list and fawtar_get.
Does the Fawtar MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Fawtar MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): fawtar_create_invoice and fawtar_vat_summary.
Has the Fawtar MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.