Skip to content
ProtocolProbe
Explore

MCP servers › io.usefulapi › kiotviet

MCP server · registry snapshot 2026-10-27 · last tested 2026-10-27

io.usefulapi/kiotviet

KiotViet MCP by usefulapi — the publisher's title

by usefulapi.io · domain (the registry's namespace rule)repository owner on GitHub: m190 (personal account)Source ↗Website ↗

Read KiotViet products, customers, invoices, orders and stock; create customers and orders. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-27version 1.1.0JavaScriptstreamable HTTP29 tools

Summary

io.usefulapi/kiotviet is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain usefulapi.io. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. On 2026-10-27 ProtocolProbe connected to it in read-only mode and read its inventory: 29 tools, 0 resources and 1 prompt.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
29
Last tested
2026-10-27

Tool list size

12,798 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (29 tools). Counted with Anthropic's token counter on 2026-10-27, from the tool list we read on 2026-10-27. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-27 (kiotviet.usefulapi.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.1.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (kiotviet_create_customer, kiotviet_create_order). That is our reading of the names; we did not call them. Source: our connection, 2026-10-27.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-27
Mode
read-only (no tool calls)
Latest version
1.1.0, published 2026-10-27 (registry, as of the 2026-10-27 snapshot)
First listed version
2026-10-26 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-10-26 to 2026-10-27; 2 in the 90 days before the 2026-10-27 snapshot.
Most recent 2 versions
  • 1.1.0 · 2026-10-27
  • 1.0.0 · 2026-10-26
(versions still listed in the registry only)
Registry data
snapshot 2026-10-27
Package and repository
checked 2026-10-27
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.0 (published 2026-10-26) → 1.1.0 (published 2026-10-27), between the registry lists of 2026-10-26 and 2026-10-27.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27; release notes from the GitHub Releases API, checked 2026-10-27.

What it is

What does this server offer?

Observed inventory
29tools
0resources
1prompts

None of its 29 tools are described as changing anything. For 29 the reading was uncertain, so no mark is shown.

  • kiotviet_list_products

    “List products (code, barcode, name, category, base price, units, attributes).”

    Publisher declares: read-only yes · destructive no · open-world yes

    11 inputs
    • namestring“Filter by product name.”
    • category_idinteger“Only products in this category (see kiotviet_list_categories).”
    • branch_idsarray“Only these branches (see kiotviet_list_branches).”
    • is_activeboolean“Only active (true) or inactive (false) products.”
    • include_inventoryboolean“Include the stock on hand per branch.”
    • include_pricebookboolean“Include the price-book prices.”
    • last_modified_fromstring“Only records changed at or after this date-time (shop local time).”
    • order_bystring“Sort field.”
    • order_directionstring“Sort direction.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_product

    “One product by id: code, barcode, name, category, base price, units, attributes, images, stock per branch and price books.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • product_idintegerrequired“KiotViet product id.”
  • kiotviet_get_product_by_code

    “One product by its product code (SKU).”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • codestringrequired“KiotViet product code.”
  • kiotviet_list_categories

    “List product categories (id, name, parent, whether it has children).”

    Publisher declares: read-only yes · destructive no · open-world yes

    6 inputs
    • hierarchicalboolean“Return the nested tree (ignores last_modified_from).”
    • last_modified_fromstring“Only records changed at or after this date-time (shop local time).”
    • order_bystring“Sort field.”
    • order_directionstring“Sort direction.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_category

    “One product category by id (name, parent, children).”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • category_idintegerrequired“KiotViet category id.”
  • kiotviet_list_customers

    “List customers (code, name, phone, email, address, debt, total invoiced, reward points, groups).”

    Publisher declares: read-only yes · destructive no · open-world yes

    11 inputs
    • codestring“Customer code.”
    • namestring“Filter by customer name.”
    • contact_numberstring“Filter by phone number.”
    • group_idinteger“Only customers in this customer group.”
    • include_customer_groupboolean“Include each customer's groups.”
    • include_totalboolean“Include financial totals (debt, total invoiced, points).”
    • last_modified_fromstring“Only records changed at or after this date-time (shop local time).”
    • order_bystring“Sort field.”
    • order_directionstring“Sort direction.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_customer

    “One customer by id: contact data, debt, total invoiced, reward points, groups.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • customer_idintegerrequired“KiotViet customer id.”
  • kiotviet_get_customer_by_code

    “One customer by customer code.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • codestringrequired“KiotViet customer code.”
  • kiotviet_create_customer

    “WRITE: create a new customer in the shop (name required; code is generated by KiotViet if omitted).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    10 inputs, 1 required
    • namestringrequired“Customer name.”
    • codestring“Customer code (optional; KiotViet generates one).”
    • contact_numberstring“Phone number.”
    • emailstring“Email address.”
    • addressstring“Street address.”
    • birth_datestring“Date 2026-10-01 or date-time 2026-10-01T08:00:00 (shop local time).”
    • commentsstring“Note on the customer.”
    • group_idsarray“Customer group ids.”
    • organizationstring“Company name.”
    • tax_codestring“Tax code (ma so thue).”
  • kiotviet_list_invoices

    “List sales invoices (code, date, branch, customer, total, amount paid, status, lines).”

    Publisher declares: read-only yes · destructive no · open-world yes

    13 inputs
    • branch_idsarray“Only these branches (see kiotviet_list_branches).”
    • customer_idsarray“Only invoices of these customers.”
    • customer_codestring“Only invoices of the customer with this code.”
    • statusarray“KiotViet status code(s) to include.”
    • order_idinteger“Only the invoice created from this sales order.”
    • from_purchase_datestring“Date 2026-10-01 or date-time 2026-10-01T08:00:00 (shop local time).”
    • to_purchase_datestring“Date 2026-10-01 or date-time 2026-10-01T08:00:00 (shop local time).”
    • include_paymentboolean“Include the payments.”
    • last_modified_fromstring“Only records changed at or after this date-time (shop local time).”
    • order_bystring“Sort field.”
    • order_directionstring“Sort direction.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_invoice

    “One invoice by id with its lines, payments and delivery.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • invoice_idintegerrequired“KiotViet invoice id.”
  • kiotviet_get_invoice_by_code

    “One invoice by invoice code (for example HD000123).”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • codestringrequired“KiotViet invoice code.”
Show 17 more tools
  • kiotviet_list_orders

    “List sales orders (code, date, branch, customer, total, status, lines, delivery).”

    Publisher declares: read-only yes · destructive no · open-world yes

    14 inputs
    • branch_idsarray“Only these branches (see kiotviet_list_branches).”
    • customer_idsarray“Only orders of these customers.”
    • customer_codestring“Only orders of the customer with this code.”
    • statusarray“KiotViet status code(s) to include.”
    • sale_channel_idinteger“Only orders from this sales channel.”
    • created_datestring“Only orders created at or after this date.”
    • last_modified_tostring“Only orders last changed up to this date-time (KiotViet toDate is a bound on the modification time, not the creation time).”
    • include_paymentboolean“Include the payments.”
    • include_order_deliveryboolean“Include the delivery details.”
    • last_modified_fromstring“Only records changed at or after this date-time (shop local time).”
    • order_bystring“Sort field.”
    • order_directionstring“Sort direction.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_order

    “One sales order by id with its lines, payments and delivery.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • order_idintegerrequired“KiotViet order id.”
  • kiotviet_get_order_by_code

    “One sales order by order code (for example DH000123).”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • codestringrequired“KiotViet order code.”
  • kiotviet_create_order

    “WRITE: create a sales order (an order, not an invoice: no invoice is made and no payment is recorded) with lines of existing products in a branch, for an existing customer or none.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    7 inputs, 2 required
    • branch_idintegerrequired“Branch the order is for (see kiotviet_list_branches).”
    • customer_idinteger“Existing customer id (see kiotviet_list_customers).”
    • descriptionstring“Note on the order.”
    • discountnumber“Order discount amount.”
    • sold_by_idinteger“Salesperson user id (see kiotviet_list_users).”
    • sale_channel_idinteger“Sales channel id.”
    • itemsarrayrequired“The order lines.”
  • kiotviet_list_branches

    “List the shop's branches (id, name, code, phone, address).”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_list_stock

    “Stock on hand and reserved quantity per product and branch.”

    Publisher declares: read-only yes · destructive no · open-world yes

    6 inputs
    • branch_idsarray“Only these branches (see kiotviet_list_branches).”
    • last_modified_fromstring“Only records changed at or after this date-time (shop local time).”
    • order_bystring“Sort field.”
    • order_directionstring“Sort direction.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_list_suppliers

    “List suppliers (code, name, phone, email, address, debt, total invoiced).”

    Publisher declares: read-only yes · destructive no · open-world yes

    8 inputs
    • codestring“Supplier code.”
    • namestring“Filter by supplier name.”
    • contact_numberstring“Filter by phone number.”
    • include_totalboolean“Include financial totals (debt, total invoiced).”
    • last_modified_fromstring“Only records changed at or after this date-time (shop local time).”
    • order_directionstring“Sort direction.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_supplier

    “One supplier by id.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • supplier_idintegerrequired“KiotViet supplier id.”
  • kiotviet_list_purchase_orders

    “List goods receipts from suppliers (nhap hang: code, date, branch, supplier, total, lines).”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs
    • branch_idsarray“Only these branches (see kiotviet_list_branches).”
    • statusarray“KiotViet status code(s) to include.”
    • from_purchase_datestring“Date 2026-10-01 or date-time 2026-10-01T08:00:00 (shop local time).”
    • to_purchase_datestring“Date 2026-10-01 or date-time 2026-10-01T08:00:00 (shop local time).”
    • include_paymentboolean“Include the payments.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_purchase_order

    “One goods receipt (nhap hang) by id with its lines.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • purchase_order_idintegerrequired“KiotViet goods receipt id.”
  • kiotviet_list_supplier_orders

    “List orders placed with suppliers (dat hang nhap: code, date, branch, supplier, status, lines, amount paid).”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs
    • branch_idinteger“Only this branch.”
    • statusinteger“KiotViet status code.”
    • supplier_keystring“Supplier code, name or phone.”
    • product_keystring“Product code or name.”
    • code_keystring“Order code.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_list_returns

    “List customer returns (code, date, branch, customer, invoice, return total, lines).”

    Publisher declares: read-only yes · destructive no · open-world yes

    6 inputs
    • include_paymentboolean“Include the payments.”
    • last_modified_fromstring“Only records changed at or after this date-time (shop local time).”
    • order_bystring“Sort field.”
    • order_directionstring“Sort direction.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_return

    “One customer return by id with its lines.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • return_idintegerrequired“KiotViet return id.”
  • kiotviet_list_cashflow

    “List cash-book entries (receipts and payments: code, branch, method, partner, amount, date, status).”

    Publisher declares: read-only yes · destructive no · open-world yes

    8 inputs
    • branch_idsarray“Only these branches (see kiotviet_list_branches).”
    • is_receiptboolean“true = receipts (money in), false = payments (money out).”
    • start_datestring“Date 2026-10-01 or date-time 2026-10-01T08:00:00 (shop local time).”
    • end_datestring“Date 2026-10-01 or date-time 2026-10-01T08:00:00 (shop local time).”
    • codestring“Voucher code.”
    • partner_namestring“Customer, supplier or other partner name.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_list_users

    “List the shop's staff users (id, username, name, phone, email).”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_list_price_books

    “List price books (bang gia: name, active flag, validity dates, branches, customer groups).”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs
    • include_branchesboolean“Include the branches each price book applies to.”
    • include_customer_groupsboolean“Include the customer groups each price book applies to.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”
  • kiotviet_get_price_book

    “The product prices of one price book (product id, code, price), paged.”

    Publisher declares: read-only yes · destructive no · open-world yes

    3 inputs, 1 required
    • price_book_idintegerrequired“KiotViet price book id.”
    • current_iteminteger“Record offset to start from (0 = first record).”
    • page_sizeinteger“Records per page, 1-100 (default 20).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 137
Tools with a description
100% of 29
Typical description length
123 characters

The tool set

Counted from the listing

Tools
29
Size of the list
about 7,795 tokens for an agent to load (characters ÷ 4)
Naming
29 of 29 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 29 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-27 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://kiotviet.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "kiotviet": {
      "url": "https://kiotviet.usefulapi.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "kiotviet": {
      "type": "http",
      "url": "https://kiotviet.usefulapi.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"kiotviet","type":"http","url":"https://kiotviet.usefulapi.io/mcp"}'
Claude Code
claude mcp add --transport http kiotviet https://kiotviet.usefulapi.io/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "kiotviet": {
      "type": "streamableHttp",
      "url": "https://kiotviet.usefulapi.io/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "kiotviet": {
      "httpUrl": "https://kiotviet.usefulapi.io/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.kiotviet]
url = "https://kiotviet.usefulapi.io/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "kiotviet": {
      "url": "https://kiotviet.usefulapi.io/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://kiotviet.usefulapi.io/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint kiotviet.usefulapi.io/mcpSession openedmatchesour test · 2026-10-27
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-27
Repository github.com/m190/usefulapi-mcpOpens publiclymatchesapi.github.com · 2026-10-27

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.usefulapi · 462 servers
GitHub owner
a personal account (m190)
Repository
github.com/m190/usefulapi-mcp
Stars
0
Repository age
91–180 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-27.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint kiotviet.usefulapi.io/mcp

No change in the tool list across 2 reads (2026-10-26 to 2026-10-27; versions 1.0.0 to 1.1.0).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-10-27 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/kiotviet

Answered from the data above

Who publishes io.usefulapi/kiotviet?

The registry ties the namespace io.usefulapi to the domain usefulapi.io; only its owner can publish under it. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. These are facts from the registry and GitHub, not a rating.

Is io.usefulapi/kiotviet safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/kiotviet need an API key or sign-in?

It opened a session without any credential on 2026-10-27. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/kiotviet been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.usefulapi/kiotviet?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-27
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not run · an error was returned
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 13
  • 3Real execution
    real-execution    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
  • 16Sign-in redirect
    open-redirect    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-27, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 214 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 29 tools, 0 resources, 1 prompt.
  4. 901 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-27; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
JavaScript
api.github.com · 2026-10-27
Hosting type
remote (hosted by the publisher)
registry · 2026-10-27
MCP capability
prompts, tools
our test · 2026-10-27
Transport
streamable HTTP
registry · 2026-10-27
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-27
Lifecycle status
active
registry · 2026-10-27
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-10-27
Maintenance
active
api.github.com · 2026-10-27
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/kiotviet: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/io.usefulapi/kiotviet

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/kiotviet)](https://protocolprobe.com/mcp/servers/io.usefulapi/kiotviet)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology