Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bukku MCP by usefulapi

REMOTE · BUKKU.USEFULAPI.IO

Read Bukku contacts, accounts, invoices, bills and journals; create contacts and sales invoices.

−44 this week 18 Trust /100

Last scanned (7 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 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.

Changelog

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.

  • 2 Nov 26 −49
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “add_a_customer_or_supplier” functional
    • New prompt “browse_accounts_and_journals” functional
    • New prompt “chase_overdue_sales_invoices” functional
    • New prompt “draft_a_sales_invoice” functional
    • New prompt “review_bank_activity” functional
    • New prompt “review_supplier_bills” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.7.0 → 1.9.0 functional
    • Server version: 1.6.0 → 1.7.0 functional
    • Server version: 1.5.2 → 1.6.0 functional
  • 30 Oct 26 +1
    • Server version: 1.5.1 → 1.5.2 functional
    • Server version: 1.5.0 → 1.5.1 functional
  • 29 Oct 26 0
    • Server version: 1.4.0 → 1.5.0 functional
    • Server version: 1.3.0 → 1.4.0 functional
  • 28 Oct 26 +1
    • Server version: 1.1.0 → 1.3.0 functional
  • 27 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.1.0 functional
  • 26 Oct 26 61

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://bukku.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bukku.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bukku.usefulapi.io/mcp Redirected 302 https://usefulapi.io/bukku/
http (plaintext) http://bukku.usefulapi.io/mcp Inconclusive 302 http://bukku.usefulapi.io/mcp
MCP tools · 23 exposed · ~2,980 tokens

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 →

Tool Tokens
bukku_create_contact ~236

WRITE: create a contact (customer, supplier and/or employee) in Bukku. The contact code must be unique (A-Z, 0-9, _ and -, max 15 characters). POST /contacts.

NameTypeReqDescription
contact_codestringyesUnique code, for example C-A0001.
emailstring––
entity_typestringyesEntity type (used for MyInvois).
legal_namestringyesLegal name of the contact.
other_namestring–Trading or display name.
phone_nostring––
reg_nostring–Registration number. Required for MALAYSIAN_COMPANY (with reg_no_type); individuals need it or tax_id_no.
reg_no_typestring–Registration number type; send together with reg_no.
remarksstring––
tax_id_nostring–Malaysian TIN / tax id (11-14 characters). Required for MALAYSIAN_COMPANY; individuals need it or reg_no.
typesarrayyesContact types; a contact can be several.

No output schema declared.

No examples provided.

bukku_create_sales_invoice ~367

WRITE: create a sales invoice for a customer. status defaults to draft (nothing posted to the ledger), status ready finalizes it and affects the books. payment_mode credit needs term_items, cash needs deposit_items. Companies with MyInvois submission switched on must pass myinvois_action when status is ready: NORMAL (not sent), EXTERNAL (already validated elsewhere) or VALIDATE (submits the invoice to LHDN MyInvois, which cannot be taken back). Look up contact, account, term and tax code ids first. POST /sales/invoices.

NameTypeReqDescription
contact_idintegeryesCustomer contact id (bukku_list_contacts type customer).
currency_codestringyesInvoice currency, for example MYR. Use the company's home currency unless invoicing in another one.
datestringyesInvoice date, yyyy-mm-dd.
deposit_itemsarray–Payment received, for payment_mode cash.
descriptionstring––
exchange_ratenumberyesRate from the home currency to currency_code. Use 1 when currency_code is the home currency.
itemsarrayyesInvoice lines.
myinvois_actionstring–MyInvois handling, only with status ready.
numberstring–Invoice number, blank uses the default number format.
number2string–Reference number.
payment_modestring–credit (needs term_items) or cash (needs deposit_items).
remarksstring––
statusstring–draft (default) or ready.
tax_modestringyesWhether unit prices include tax.
term_itemsarray–Payment terms, for payment_mode credit.
titlestring––

No output schema declared.

No examples provided.

bukku_get_account ~34

One ledger account by id. GET /accounts/{id}.

NameTypeReqDescription
account_idintegeryesBukku account id.

No output schema declared.

No examples provided.

bukku_get_bank_transaction ~59

One money in, money out or transfer transaction in full. GET /banking/{incomes|expenses|transfers}/{id}.

NameTypeReqDescription
transaction_idintegeryesBukku transaction id.
typestringyesTransaction type.

No output schema declared.

No examples provided.

bukku_get_contact ~47

One contact with its persons, addresses, tax and registration numbers, default accounts and credit limit. GET /contacts/{id}.

NameTypeReqDescription
contact_idintegeryesBukku contact id.

No output schema declared.

No examples provided.

bukku_get_journal_entry ~45

One journal entry with its debit and credit lines. GET /journal_entries/{id}.

NameTypeReqDescription
transaction_idintegeryesBukku transaction id of the journal entry.

No output schema declared.

No examples provided.

bukku_get_lookup_lists ~90

Reference data needed to fill in documents: tax codes, payment terms, payment methods, currencies, countries, accounts, contact groups, product groups, price levels, tag groups, number formats, custom fields and company settings. Read-only (POST /v2/lists is a read endpoint).

NameTypeReqDescription
listsarrayyesWhich lists to return, for example ["tax_codes", "terms"].

No output schema declared.

No examples provided.

bukku_get_product ~41

One product with its units, prices, accounts and tax settings. GET /products/{id}.

NameTypeReqDescription
product_idintegeryesBukku product id.

No output schema declared.

No examples provided.

bukku_get_purchase_document ~73

One purchase document in full (lines, taxes, terms, payments, status): a bill, order, goods received note, credit note, payment or refund. GET /purchases/{type}/{id}.

NameTypeReqDescription
transaction_idintegeryesBukku transaction id.
typestringyesDocument type.

No output schema declared.

No examples provided.

bukku_get_sales_document ~73

One sales document in full (lines, taxes, terms, payments, status): an invoice, quote, order, delivery order, credit note, payment or refund. GET /sales/{type}/{id}.

NameTypeReqDescription
transaction_idintegeryesBukku transaction id.
typestringyesDocument type.

No output schema declared.

No examples provided.

bukku_list_accounts ~93

List ledger accounts from the chart of accounts, optionally by category. Account ids are used on invoice lines. GET /accounts.

NameTypeReqDescription
categorystring––
is_archivedboolean–true to show deactivated accounts instead of active ones (default false).
searchstring–Keywords to search for in the accounts (max 100 characters).
sort_dirstring–Sort direction.

No output schema declared.

No examples provided.

bukku_list_bank_transactions ~245

List banking transactions: money in (incomes), money out (expenses) or transfers between accounts. contact_id and sort_by do not apply to transfers. GET /banking/{incomes|expenses|transfers}.

NameTypeReqDescription
account_idinteger–Only transactions on this bank/cash account (see bukku_list_accounts).
contact_idinteger–Only this contact (money in / money out).
date_fromstring–A date, yyyy-mm-dd.
date_tostring–A date, yyyy-mm-dd.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 30).
searchstring–Keywords in the number, reference, title, remarks, description or contact.
sort_bystring–Money in / money out only.
sort_dirstring–Sort direction.
statusstring–Only transactions with this status. Without it every status except void is returned.
typestringyesWhich banking transactions to list.

No output schema declared.

No examples provided.

bukku_list_contact_groups ~31

List the contact groups; use their ids to filter bukku_list_contacts. GET /contacts/groups.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bukku_list_contacts ~188

List contacts (customers, suppliers, employees) with name, code, type, receivable and payable balances. Search matches the name, receivable, payable and created date. GET /contacts.

NameTypeReqDescription
group_idinteger–Only contacts in this contact group (see bukku_list_contact_groups).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 30).
searchstring–Keywords in the name, receivable, payable or created date (max 100 characters).
sort_bystring––
sort_dirstring–Sort direction.
statusstring–ACTIVE (default), INACTIVE (archived) or ALL contacts.
typestring–Only this contact type.

No output schema declared.

No examples provided.

bukku_list_journal_entries ~151

List manual journal entries by date, status or keywords. GET /journal_entries.

NameTypeReqDescription
date_fromstring–A date, yyyy-mm-dd.
date_tostring–A date, yyyy-mm-dd.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 30).
searchstring–Keywords in the number, reference, title, remarks or description.
sort_dirstring–Sort direction.
statusstring–Only transactions with this status. Without it every status except void is returned.

No output schema declared.

No examples provided.

bukku_list_product_groups ~21

List the product groups. GET /products/groups.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bukku_list_products ~143

List products and bundles (sales and purchase details, SKU, stock). GET /products.

NameTypeReqDescription
include_archivedboolean–true to include archived products.
modestring–Only products sold or only products purchased.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 30).
searchstring–Keywords in the name, SKU, sale or purchase description or remarks (max 60 characters).
sort_dirstring–Sort direction.
typestring––

No output schema declared.

No examples provided.

bukku_list_purchase_bills ~209

List purchase bills with number, date, supplier, amount, balance and payment status. Filter by date, supplier, payment status (PAID, OUTSTANDING, OVERDUE) or keywords. GET /purchases/bills.

NameTypeReqDescription
contact_idinteger–Only bills of this supplier.
date_fromstring–Bills dated on or after this day, yyyy-mm-dd.
date_tostring–Bills dated on or before this day, yyyy-mm-dd.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 30).
payment_modestring––
payment_statusstring––
searchstring––
sort_dirstring–Sort direction.
statusstring–Only transactions with this status. Without it every status except void is returned.

No output schema declared.

No examples provided.

bukku_list_purchase_documents ~247

List purchase orders, goods received notes, supplier credit notes, supplier payments or refunds (bills have their own tool, bukku_list_purchase_bills). payment_status applies to credit notes, payments and refunds only. GET /purchases/{orders|goods_received_notes|credit_notes|payments|refunds}.

NameTypeReqDescription
contact_idinteger–Only documents of this supplier.
date_fromstring–A date, yyyy-mm-dd.
date_tostring–A date, yyyy-mm-dd.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 30).
payment_statusstring–Credit notes (PAID, OUTSTANDING, OVERDUE), payments and refunds (PAID, OUTSTANDING). Not for the other types.
searchstring––
sort_dirstring–Sort direction.
statusstring–Only transactions with this status. Without it every status except void is returned.
typestringyesWhich purchase document to list.

No output schema declared.

No examples provided.

bukku_list_sales_documents ~247

List quotes, sales orders, delivery orders, credit notes, customer payments or refunds (invoices have their own tool, bukku_list_sales_invoices). payment_status applies to credit notes, payments and refunds only. GET /sales/{quotes|orders|delivery_orders|credit_notes|payments|refunds}.

NameTypeReqDescription
contact_idinteger–Only documents of this customer.
date_fromstring–A date, yyyy-mm-dd.
date_tostring–A date, yyyy-mm-dd.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 30).
payment_statusstring–Credit notes (PAID, OUTSTANDING, OVERDUE), payments and refunds (PAID, OUTSTANDING). Not for the other types.
searchstring––
sort_dirstring–Sort direction.
statusstring–Only transactions with this status. Without it every status except void is returned.
typestringyesWhich sales document to list.

No output schema declared.

No examples provided.

bukku_list_sales_invoices ~237

List sales invoices with number, date, contact, amount, balance and payment status. Filter by date, customer, payment status (PAID, OUTSTANDING, OVERDUE) or keywords. GET /sales/invoices.

NameTypeReqDescription
contact_idinteger–Only invoices of this customer.
date_fromstring–Invoices dated on or after this day, yyyy-mm-dd.
date_tostring–Invoices dated on or before this day, yyyy-mm-dd.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 30).
payment_modestring––
payment_statusstring––
searchstring–Keywords in the number, reference, title, remarks, description, contact or billing/shipping party.
sort_bystring––
sort_dirstring–Sort direction.
statusstring–Only transactions with this status. Without it every status except void is returned.

No output schema declared.

No examples provided.

bukku_list_tags ~27

List the tags (labels) that can be put on transactions. GET /tags.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bukku_set_contact_archived ~76

WRITE: archive (is_archived true) or restore (false) a contact. Archiving hides it from active lists; nothing is deleted. PATCH /contacts/{id}.

NameTypeReqDescription
contact_idintegeryesBukku contact id.
is_archivedbooleanyestrue to archive, false to unarchive.

No output schema declared.

No examples provided.

Install

How do I install the Bukku MCP by usefulapi server?

Bukku MCP by usefulapi is a hosted endpoint at https://bukku.usefulapi.io/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 · bukku.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-bukku 'https://bukku.usefulapi.io/mcp'
Common questions

What is the Bukku MCP by usefulapi server?

Bukku MCP by usefulapi is listed in the public MCP registry as io.usefulapi/bukku. Read Bukku contacts, accounts, invoices, bills and journals; create contacts and sales invoices. This page covers its hosted endpoint (https://bukku.usefulapi.io/mcp).

Is the Bukku MCP by usefulapi server safe to use?

Bukku MCP by usefulapi scores 18 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 Bukku MCP by usefulapi server expose?

Bukku MCP by usefulapi exposes 23 tools: bukku_list_contacts, bukku_get_contact, bukku_list_contact_groups, bukku_list_accounts, bukku_get_account, and 18 more. Their descriptions and schemas cost roughly 2,980 tokens of context every time the server is loaded.

Does the Bukku MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Bukku MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Bukku MCP by usefulapi server still maintained?

Bukku MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.