app.fawtar/fawtar
REMOTE · FAWTAR.APP · SCANNED OCT 3
ZATCA-compliant Saudi invoicing and accounting: invoices, receivables, VAT, ledger, payroll.
Available components
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
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the app.fawtar/fawtar MCP server?
app.fawtar/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'
{
"mcpServers": {
"app-fawtar-fawtar": {
"url": "https://fawtar.app/api/mcp"
}
}
} {
"servers": {
"app-fawtar-fawtar": {
"type": "http",
"url": "https://fawtar.app/api/mcp"
}
}
} [mcp_servers.app-fawtar-fawtar] url = "https://fawtar.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-fawtar-fawtar": {
"type": "remote",
"url": "https://fawtar.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-fawtar-fawtar --url 'https://fawtar.app/api/mcp' --transport streamable-http
mcp_servers:
app-fawtar-fawtar:
url: "https://fawtar.app/api/mcp" {
"McpServers": {
"app-fawtar-fawtar": {
"Transport": "http",
"Url": "https://fawtar.app/api/mcp"
}
}
} assistant mcp add app-fawtar-fawtar -t streamable-http -u 'https://fawtar.app/api/mcp'
{
"mcpServers": {
"app-fawtar-fawtar": {
"type": "http",
"url": "https://fawtar.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 −34
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.30 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Aug 26 0
First indexed and scored.
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 3 Oct 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 | 5 Sept 2026 | 4 Dec 2026 | RSA 2048 | SHA256-RSA | 62addd032df7eeeea4b9d35f34ee6072e2f |
| 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. | present | 23684 | 8 | Verified |
| fawtar.app. | absent | 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 connection |
| HTTP status | 401 |
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=() |
| www-authenticate | Bearer resource_metadata="https://fawtar.app/.well-known/oauth-protected-resource/api/mcp", error="invalid_token" |
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 | Auth required | 401 | |
| 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 ~136
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: quotes, orders, customers, products, categories, product_unit_types, vendors, bills, simple_bills, bill_payments, inventories, inventory_adjustments, inventory_transfers, invoice_payments, accounts, journal_entries, employees, assets, pos_tables.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The record's fields. |
| resource | string | yes | – |
No output schema declared.
No examples provided.
fawtar_create_invoice Issue an invoice ~173
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 | – | – |
| dueDate | string | – | YYYY-MM-DD |
| lines | array | yes | – |
| notes | string | – | – |
| pricesIncludeVat | boolean | – | – |
| taxTreatment | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
fawtar_get Fetch one record ~49
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 | – |
No output schema declared.
No examples provided.
fawtar_list List records ~535
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 | – | – |
| page | integer | – | – |
| 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 ~73
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 | – | – |
| 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.
What is the app.fawtar/fawtar MCP server?
app.fawtar/fawtar is an MCP server listed in the public MCP registry as app.fawtar/fawtar. ZATCA-compliant Saudi invoicing and accounting: invoices, receivables, VAT, ledger, payroll. This page covers its hosted endpoint (https://fawtar.app/api/mcp).
Is the app.fawtar/fawtar MCP server safe to use?
app.fawtar/fawtar scores 38 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 app.fawtar/fawtar MCP server expose?
app.fawtar/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,052 tokens of context every time the server is loaded.
Does the app.fawtar/fawtar MCP server require authentication?
Yes. app.fawtar/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 app.fawtar/fawtar MCP server still maintained?
app.fawtar/fawtar is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.