Fawtar
REMOTE · FAWTAR.APP
ZATCA-compliant Saudi invoicing. Free 24h sandbox key, no signup; 1,000 API writes for 99 SAR.
Available components
Last scanned (18 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1309 tokens (~218/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.23 ▲ functional
- 12 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://fawtar.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fawtar.app | CN=YR1,O=Let's Encrypt,C=US | 7 Nov 2026 | 5 Feb 2027 | RSA 2048 | SHA256-RSA | 52dbf24f1ac46f21c47789b80bcde66c025 |
| SANs: fawtar.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fawtar.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| fawtar.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://fawtar.app/.well-known/oauth-protected-resource/api/mcp", error="invalid_token"
Bearer resource_metadata="https://fawtar.app/.well-known/oauth-protected-resource/api/mcp", error="invalid_token" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://fawtar.app/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://fawtar.app/api/mcp |
| Authorisation server | https://fawtar.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fawtar.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://fawtar.app/api/mcp | HTTPS enforced | 308 | https://fawtar.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fawtar_create Create a record ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The record's fields. |
| resource | string | yes | Which kind of record to create. |
No output schema declared.
No examples provided.
fawtar_create_invoice Issue an invoice ~331
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).
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | object | – | Who the invoice is for. Required for a standard (B2B) invoice, where name and vatNumber must both be present. |
| dueDate | string | – | YYYY-MM-DD |
| lines | array | yes | The invoice lines. At least one. Amounts are in Saudi riyals unless the org bills in another currency. |
| notes | string | – | Free text printed on the invoice, visible to the buyer. |
| pricesIncludeVat | boolean | – | True when each line unitPrice already contains VAT, so it is divided out rather than added on. |
| taxTreatment | string | yes | "tax" for a VAT invoice from a VAT-registered seller, "ordinary" when the seller is not VAT registered. An ordinary invoice carries no VAT and no QR code. |
| type | string | yes | ZATCA document type: "simplified" for a sale to an individual (B2C), "standard" for a sale to a business (B2B), which requires the buyer's name and VAT number. |
No output schema declared.
No examples provided.
fawtar_get Fetch one record ~55
Fetch a single record by id. For invoices this also returns the line items and the public share link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The record's uuid. |
| resource | string | yes | Which resource the id belongs to. |
No output schema declared.
No examples provided.
fawtar_list List records ~551
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Ransack-style filters, e.g. {"status_eq":"issued"}. |
| limit | integer | – | How many records to return, 1 to 100. |
| page | integer | – | 1-based page number. |
| resource | string | yes | Which resource to list. |
| sort | string | – | Sort as "field asc" or "field desc". |
No output schema declared.
No examples provided.
fawtar_outstanding What is owed to this business ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many invoices to return, 1 to 100. |
| overdueOnly | boolean | – | Only invoices past their due date. |
No output schema declared.
No examples provided.
fawtar_vat_summary VAT for a period ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | YYYY-MM-DD, inclusive. |
| to | string | yes | YYYY-MM-DD, inclusive. |
No output schema declared.
No examples provided.
How do I install the Fawtar MCP server?
Fawtar is a hosted endpoint at https://fawtar.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · fawtar.app
claude mcp add --transport http app-fawtar-fawtar 'https://fawtar.app/api/mcp'
What is the Fawtar MCP server?
Fawtar is an MCP server listed in the public MCP registry as app.fawtar/fawtar. ZATCA-compliant Saudi invoicing. Free 24h sandbox key, no signup; 1,000 API writes for 99 SAR. This page covers its hosted endpoint (https://fawtar.app/api/mcp).
Is the Fawtar MCP server safe to use?
Fawtar scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Fawtar MCP server expose?
Fawtar exposes 6 tools: fawtar_list, fawtar_get, fawtar_create, fawtar_create_invoice, fawtar_outstanding, fawtar_vat_summary. Their descriptions and schemas cost roughly 1,218 tokens of context every time the server is loaded.
Does the Fawtar MCP server require authentication?
Yes. Fawtar asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Fawtar MCP server still maintained?
Fawtar is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Fawtar MCP server?
VerifyMCP ran 13 checks on Fawtar, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.