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.

AdvBox

REMOTE · API.MCP.AI · SCANNED OCT 4

Wrapper for the official AdvBox API (legal practice management): cases (with history, movements, pub

Available components

+2 this week 75 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2173 tokens (~83/item across 26 items; 26 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the AdvBox MCP server?

AdvBox is a hosted endpoint at https://api.mcp.ai/p_advbox, 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 · api.mcp.ai

# add to Claude Code
claude mcp add --transport http mcp-dir-advbox-mcp 'https://api.mcp.ai/p_advbox'
// .cursor/mcp.json
{
  "mcpServers": {
    "mcp-dir-advbox-mcp": {
      "url": "https://api.mcp.ai/p_advbox"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mcp-dir-advbox-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_advbox"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.mcp-dir-advbox-mcp]
url = "https://api.mcp.ai/p_advbox"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcp-dir-advbox-mcp": {
      "type": "remote",
      "url": "https://api.mcp.ai/p_advbox",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mcp-dir-advbox-mcp --url 'https://api.mcp.ai/p_advbox' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mcp-dir-advbox-mcp:
    url: "https://api.mcp.ai/p_advbox"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mcp-dir-advbox-mcp": {
      "Transport": "http",
      "Url": "https://api.mcp.ai/p_advbox"
    }
  }
}
# add to Vellum
assistant mcp add mcp-dir-advbox-mcp -t streamable-http -u 'https://api.mcp.ai/p_advbox'
// mcp.json
{
  "mcpServers": {
    "mcp-dir-advbox-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_advbox"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 4 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.356 → 0.9.358 functional
  • 3 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.353 → 0.9.356 functional
  • 2 Oct 26 0
    • Stability: 0.97 → pass security
  • 1 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.351 → 0.9.353 functional
  • 29 Sept 26 +1

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

  • 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
  • 27 Sept 26 +1

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

  • 25 Sept 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 6 Oct 2026 · Probed https://api.mcp.ai/p_advbox

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ai CN=WE1,O=Google Trust Services,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 1bf4d405299e078a0e62ff16cded599b
SANs: mcp.ai, *.mcp.ai
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 api.mcp.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
mcp.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.mcp.ai/p_advbox Verified 200
http (plaintext) http://api.mcp.ai/p_advbox Inconclusive 406
MCP tools · 26 exposed · ~2,048 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
advbox_create_customer ~82

Cria um novo contato/cliente. Campos conforme a API oficial (ex.: name, type, cpf/cnpj, email, phone) — envie o restante via `extra`.

NameTypeReqDescription
cnpjstring––
cpfstring––
emailstring––
extraobject––
namestring––

No output schema declared.

No examples provided.

advbox_create_lawsuit ~59

Cria um processo. Campos conforme a API oficial (use advbox_settings para descobrir IDs de tipo/responsável); envie via campos nomeados + `extra`.

NameTypeReqDescription
extraobject––
numberstring––

No output schema declared.

No examples provided.

advbox_create_movement ~56

Adiciona uma movimentação manual a um processo. Vincule ao processo (campo conforme a API oficial) + descrição; demais campos via `extra`.

NameTypeReqDescription
descriptionstring––
extraobject––

No output schema declared.

No examples provided.

advbox_create_post ~46

Cria um novo post/anotação. Campos conforme a API oficial via campos nomeados + `extra`.

NameTypeReqDescription
extraobject––
textstring––

No output schema declared.

No examples provided.

advbox_create_transaction ~72

Cria um lançamento financeiro (receita ou despesa). Campos conforme a API oficial (ex.: type, value, due_date) via campos nomeados + `extra`.

NameTypeReqDescription
due_datestring––
extraobject––
typestring––
value–––

No output schema declared.

No examples provided.

advbox_customers_birthdays ~44

Lista aniversariantes (para campanhas de relacionamento).

NameTypeReqDescription
pagenumber––
page_sizenumber––
queryobject––

No output schema declared.

No examples provided.

advbox_get_customer ~49

Busca os dados completos de um contato por ID. Bulk support: accepts ids for batched execution.

NameTypeReqDescription
id–yes–
idsarray––
queryobject––

No output schema declared.

No examples provided.

advbox_get_lawsuit ~50

Busca um processo por ID (dados completos). Bulk support: accepts ids for batched execution.

NameTypeReqDescription
id–yes–
idsarray––
queryobject––

No output schema declared.

No examples provided.

advbox_get_transaction ~48

Detalha uma transação por ID. Bulk support: accepts ids for batched execution.

NameTypeReqDescription
id–yes–
idsarray––
queryobject––

No output schema declared.

No examples provided.

advbox_last_movements ~44

Última atualização de cada processo (resumo recente).

NameTypeReqDescription
pagenumber––
page_sizenumber––
queryobject––

No output schema declared.

No examples provided.

advbox_lawsuit_history ~65

Histórico completo de um processo. Bulk support: accepts lawsuit_ids for batched execution.

NameTypeReqDescription
lawsuit_id–yes–
lawsuit_idsarray––
pagenumber––
page_sizenumber––
queryobject––

No output schema declared.

No examples provided.

advbox_lawsuit_movements ~69

Lista todas as movimentações de um processo. Bulk support: accepts lawsuit_ids for batched execution.

NameTypeReqDescription
lawsuit_id–yes–
lawsuit_idsarray––
pagenumber––
page_sizenumber––
queryobject––

No output schema declared.

No examples provided.

advbox_list_customers ~88

Lista clientes/contatos com filtros avançados (nome, cpf, cnpj, e-mail etc. via `query`).

NameTypeReqDescription
cnpjstring––
cpfstring––
emailstring––
namestring––
pagenumber––
page_sizenumber––
queryobject––

No output schema declared.

No examples provided.

advbox_list_lawsuits ~101

Lista/busca processos (22+ filtros). Filtros comuns via `query`: numero, parte, cpf, cnpj, responsavel, status, comarca, uf, datas.

NameTypeReqDescription
cnpjstring––
cpfstring––
numberstring––
pagenumber––
page_sizenumber––
queryobject––
statusstring––

No output schema declared.

No examples provided.

advbox_list_posts ~44

Lista posts e anotações (tarefas/notas).

NameTypeReqDescription
pagenumber––
page_sizenumber––
queryobject––

No output schema declared.

No examples provided.

advbox_list_transactions ~79

Lista transações financeiras com filtros de data/tipo/status (via `query`).

NameTypeReqDescription
end_datestring––
pagenumber––
page_sizenumber––
queryobject––
start_datestring––
statusstring––
typestring––

No output schema declared.

No examples provided.

advbox_publications ~66

Lista as publicações oficiais de um processo. Bulk support: accepts lawsuit_ids for batched execution.

NameTypeReqDescription
lawsuit_id–yes–
lawsuit_idsarray––
pagenumber––
page_sizenumber––
queryobject––

No output schema declared.

No examples provided.

advbox_settings ~54

Obtém todos os IDs e configurações da conta (usuários, origens, tipos de tarefa, fases, tipos de processo). Use para descobrir os IDs exigidos por create/update.

NameTypeReqDescription
queryobject––

No output schema declared.

No examples provided.

advbox_update_lawsuit ~64

Atualiza um processo existente por ID. Envie só os campos a alterar (nomeados + `extra`). Bulk support: accepts ids for batched execution.

NameTypeReqDescription
extraobject––
id–yes–
idsarray––

No output schema declared.

No examples provided.

advbox_update_transaction ~91

Atualiza valor, vencimento ou status de pagamento de uma transação por ID. Envie só os campos a alterar (nomeados + `extra`). Bulk support: accepts ids for batched execution.

NameTypeReqDescription
due_datestring––
extraobject––
id–yes–
idsarray––
statusstring––
value–––

No output schema declared.

No examples provided.

authenticate ~99

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

connect ~42

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

marketplace ~532

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

NameTypeReqDescription
actionstring––
argumentsstring––
cancel_commentstring––
cancel_reasonstring––
conversationstring––
immediateboolean––
limitnumber––
mcp_idstring––
messagestring––
prompt_bodystring––
prompt_categorystring––
prompt_descriptionstring––
prompt_slugstring––
prompt_targetsarray––
prompt_titlestring––
prompt_toolstring––
prompt_varsstring––
querystring––
report_contextstring––
request_detailsstring––
request_namestring––
tier_slugstring––
tool_idstring––

No output schema declared.

No examples provided.

report_bug ~50

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

NameTypeReqDescription
contextstring––
conversationstring––
messagestringyes–

No output schema declared.

No examples provided.

show_version ~17

Show the current MCP platform and adapter versions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

toolkit_info ~37

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the AdvBox MCP server?

AdvBox is an MCP server listed in the public MCP registry as io.github.mcp-dir/advbox-mcp. Wrapper for the official AdvBox API (legal practice management): cases (with history, movements, pub. This page covers its hosted endpoint (https://api.mcp.ai/p_advbox).

Is the AdvBox MCP server safe to use?

AdvBox scores 75 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 AdvBox MCP server expose?

AdvBox exposes 26 tools: advbox_settings, advbox_list_customers, advbox_get_customer, advbox_customers_birthdays, advbox_create_customer, and 21 more. Their descriptions and schemas cost roughly 2,048 tokens of context every time the server is loaded.

Does the AdvBox MCP server require authentication?

No. We connected to AdvBox without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AdvBox MCP server still maintained?

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