MCP servers › io.usefulapi › defontana
MCP server · registry snapshot 2026-11-03 · last tested 2026-11-03
io.usefulapi/defontana
Defontana 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 sales, purchases, stock, receivables and accounting vouchers in Defontana. — the publisher's description
Summary
io.usefulapi/defontana 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-11-03 ProtocolProbe connected to it in read-only mode and read its inventory: 28 tools, 0 resources and 1 prompt.
Record checks
4 of 5 record checks met · 4 do not apply
- 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 met: 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: 1 star (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself
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
- 28
- Last tested
- 2026-11-03
Tool list size
8,769 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (28 tools). Counted with Anthropic's token counter on 2026-11-03, from the tool list we read on 2026-11-03. Median across 25,738 counted servers: 2,858 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-03 (defontana.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).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-03
- Mode
- read-only (no tool calls)
- Latest version
- 1.1.0, published 2026-11-03 (registry, as of the 2026-11-03 snapshot)
- First listed version
- 2026-11-02 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-11-02 to 2026-11-03; 3 in the 90 days before the 2026-11-03 snapshot.(versions still listed in the registry only)
Most recent 3 versions
1.1.0· 2026-11-031.0.1· 2026-11-031.0.0· 2026-11-02
- Registry data
- snapshot 2026-11-03
- Package and repository
- checked 2026-11-03
- 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
New in the registry: not in the list of 2026-11-02, listed on 2026-11-03 with version 1.1.0 (published 2026-11-03).
Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03.
What it is
What does this server offer?
Observed inventoryNone of its 28 tools are described as changing anything. For 28 the reading was uncertain, so no mark is shown.
- defontana_get_company
“The Defontana company the login belongs to: id, name, tax id (legalCode), website and e-mail.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
- defontana_list_users
“List the users of the Defontana company (name, phone, e-mail, tax id, user id).”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
filterstring“Filter by name, tax id, e-mail or user id.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_list_clients
“List the company's clients (customers): tax id (legalCode), name, address, e-mail, payment condition, price list, seller, active flag.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
legal_codestring“Client tax id (RUT), exactly as stored, e.g.”descriptionstring“Client name or part of it.”statusstring“Filter by state: all (default), active or inactive.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_search_client_by_legal_code
“Look up one client by tax id (RUT): name, taxpayer type, business line, region, province and commune.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
legal_codestringrequired“Client tax id (RUT), e.g.”
- defontana_get_client_credit
“A client's credit position: credit amount, pending balance and the overdue-amount limit.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
legal_codestringrequired“Client tax id (RUT), e.g.”file_idstring“Client file id as stored in Defontana (see list_clients).”
- defontana_list_products
“List the company's products (articles): code, name, unit, currency, sell price and stock.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
codestring“Product code.”descriptionstring“Product name or part of it.”statusstring“Filter by state: all (default), active or inactive.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_list_services
“List the company's service items: code, description, sell price, unit and unit cost.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
codestring“Service code.”descriptionstring“Service description or part of it.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_list_sellers
“List the sales people (vendedores): code and name.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
codestring“Seller code.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_list_shops
“List the points of sale (locales): code, description, address, business code and default storage.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
codestring“Shop code.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_list_storages
“List the storages (bodegas): code, description, whether sales are allowed and the active flag.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
codestring“Storage code.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_get_storage_stock
“Stock per product in one storage (bodega), with the price-list prices.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
storage_idstringrequired“Storage code.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_list_payment_conditions
“The payment conditions (condiciones de pago): code, name, type, number of dues and days between payments.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
Show 16 more tools
- defontana_list_taxes
“The taxes the company uses (for example IVA): code, name, value and type.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
- defontana_list_sales
“Sales documents (invoices, receipts, credit notes) issued between two dates, with client, seller, lines, net/exempt totals, tax and total.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs, 2 required
from_datestringrequired“First emission date, yyyy-mm-dd.”to_datestringrequired“Last emission date, yyyy-mm-dd.”document_typestring“Document type id, e.g.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_get_sale
“One sales document by document type and folio number: client, lines, totals, tax, attached documents and accounting voucher.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
document_typestringrequired“Document type id, e.g.”numberintegerrequired“Document folio number.”
- defontana_list_orders
“Customer orders (pedidos) created between two dates: number, creation date and client.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs, 2 required
from_datestringrequired“First creation date, yyyy-mm-dd.”to_datestringrequired“Last creation date, yyyy-mm-dd.”from_numberinteger“Only orders with this number or higher.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_get_order
“One customer order by number: client, seller, shop, lines, discounts and totals.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
numberintegerrequired“Order number.”
- defontana_list_purchases
“Purchase documents (supplier invoices) between two dates: provider, document type and number, total, emission date, SII status and whether it is integrated.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs, 2 required
from_datestringrequired“First date, yyyy-mm-dd.”to_datestringrequired“Last date, yyyy-mm-dd.”sii_document_codestring“SII document code, e.g.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_get_purchase
“One purchase document by provider code, document type and number, with lines and totals.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 3 required
providerstringrequired“Provider code (the provider's tax id as stored).”document_typestringrequired“Document type code.”numberintegerrequired“Document number.”
- defontana_list_purchase_orders
“Purchase orders (órdenes de compra) between two dates: provider, status, emission date, totals, series and number.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs, 2 required
from_datestringrequired“First date, yyyy-mm-dd.”to_datestringrequired“Last date, yyyy-mm-dd.”providerstring“Provider tax id or name.”statusstring“Order status (default all).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_get_purchase_order
“One purchase order by number (and series, if the company uses series): provider, lines, taxes and totals.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
numberintegerrequired“Purchase order number.”seriesstring“Purchase order series.”
- defontana_list_providers
“List the company's providers (suppliers): tax id, name, address, contact data and the active flag.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
legal_codestring“Provider tax id (RUT).”descriptionstring“Provider name or part of it.”statusstring“Filter by state: all (default), active or inactive.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_get_account_plan
“The chart of accounts (plan de cuentas) as a tree: account code, description and the related IFRS account.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
- defontana_list_vouchers
“Accounting vouchers (comprobantes) with type, fiscal year, date, entry date, user and number.”
Publisher declares: read-only yes · destructive no · open-world yes
9 inputs
voucher_typestring“Voucher type id, e.g.”fiscal_yearinteger“Fiscal year, e.g.”from_datestring“Vouchers dated on or after this day, yyyy-mm-dd.”to_datestring“Vouchers dated on or before this day, yyyy-mm-dd.”userstring“Only vouchers entered by this user.”from_numberinteger“Voucher number from.”to_numberinteger“Voucher number to.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_get_voucher
“One accounting voucher with its header and every line (account, debit, credit, file id, document, business center, classifiers).”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 3 required
voucher_typestringrequired“Voucher type id, e.g.”numberintegerrequired“Voucher number.”fiscal_yearintegerrequired“Fiscal year of the voucher.”
- defontana_get_business_center
“One business center (centro de negocio) by code: description, active and postable flags.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
codestringrequired“Business center code.”
- defontana_list_receivables
“Open (unpaid) sales documents of one client: document type, series, number, due date and amount.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
file_idstringrequired“Client file id (tax id as stored).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
- defontana_list_payables
“Open (unpaid) purchase documents of one provider: document type, series, number, due date and amount.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
file_idstringrequired“Provider file id (tax id as stored).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-100 (default 25).”
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-11-03.
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 85
- Tools with a description
- 100% of 28
- Typical description length
- 142 characters
The tool set
Counted from the listing
- Tools
- 28
- Size of the list
- about 5,778 tokens for an agent to load (characters ÷ 4)
- Naming
- 28 of 28 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 28 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-11-03 (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://defontana.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"defontana": {
"url": "https://defontana.usefulapi.io/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"defontana": {
"type": "http",
"url": "https://defontana.usefulapi.io/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"defontana","type":"http","url":"https://defontana.usefulapi.io/mcp"}'Claude Code
claude mcp add --transport http defontana https://defontana.usefulapi.io/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"defontana": {
"type": "streamableHttp",
"url": "https://defontana.usefulapi.io/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"defontana": {
"httpUrl": "https://defontana.usefulapi.io/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.defontana] url = "https://defontana.usefulapi.io/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"defontana": {
"url": "https://defontana.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://defontana.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 #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint defontana.usefulapi.io/mcp | Session opened | matches | our test · 2026-11-03 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-03 |
| Repository github.com/m190/usefulapi-mcp | Opens publicly | matches | api.github.com · 2026-11-03 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.usefulapi · 748 servers
- GitHub owner
- a personal account (m190)
- Repository
- github.com/m190/usefulapi-mcp
- Stars
- 1
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-03; security policy read from GitHub · 2026-11-03.
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.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 1 star (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 metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a 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-11-03 (security policy 2026-11-03). 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, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.usefulapi/defontana
Answered from the data aboveWho publishes io.usefulapi/defontana?
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/defontana safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 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/defontana need an API key or sign-in?
It opened a session without any credential on 2026-11-03. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.usefulapi/defontana been security tested?
Partly. 3 of the 16 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Does io.usefulapi/defontana publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of io.usefulapi/defontana?
In github.com/m190/usefulapi-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA 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
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not run · an error was returned
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- 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.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls 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-leakPlants 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
ssrfChecks 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-confirmationChecks 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-handlingSends 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
samplingChecks 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-dataChecks 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-boundaryChecks 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-channelChecks 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-hidingChecks 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-turnChecks 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-redirectChecks 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-deputyChecks 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
- 14Token passthrough
token-passthroughChecks 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-validationChecks 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-11-03, 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.
- 0 msStarted a read-only session with the server's remote endpoint
- 488 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 28 tools, 0 resources, 1 prompt.
- 1,461 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.
“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/defontana: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/io.usefulapi/defontana
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
[](https://protocolprobe.com/mcp/servers/io.usefulapi/defontana)
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