Organizze
REMOTE · API.MCP.AI
Your Organizze finances in natural language: consolidated balances, monthly overview, transaction se
Available components
Last scanned (14 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 7613 tokens (~111/item across 68 items; 68 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 69 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.460 → 0.9.467 functional
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.459 → 0.9.460 functional
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.454 → 0.9.459 functional
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.452 → 0.9.454 functional
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.450 → 0.9.452 functional
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.449 → 0.9.450 functional
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.442 → 0.9.449 functional
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.429 → 0.9.442 functional
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 21 Nov 2026 · Probed https://api.mcp.ai/p_organizze
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. | DS published | 1814 | 8 | Verified |
| mcp.ai. | No DS | 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_organizze | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_organizze | Inconclusive | 406 |
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 →
organizze_mass_update_transactions ~296
Atualiza VÁRIAS transações por FILTRO de busca (máx. 200) — prefira isto a montar listas de IDs quando a mesma alteração vale para todas as linhas. Antes, valide com list_transactions/search_transactions os mesmos filtros. Informe ao menos um filtro e um campo a alterar. Prefira new_category por NOME. Conjunto vazio ou >200 devolve validation (refine filtros). Para mapa linha-a-linha use update_transactions_categories / descriptions. Irreversível em lote. Bulk support: accepts category_ids, account_ids, credit_card_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | number | – | – |
| account_ids | array | – | – |
| activity_type | string | – | – |
| category_id | number | – | – |
| category_ids | array | – | – |
| credit_card_id | number | – | – |
| credit_card_ids | array | – | – |
| description_find | string | – | – |
| description_replace | string | – | – |
| end_date | string | – | – |
| new_category | string | – | – |
| new_description | string | – | – |
| new_observation | string | – | – |
| new_paid | boolean | – | – |
| new_tags | string | – | – |
| paid_filter | boolean | – | – |
| query | string | – | – |
| start_date | string | – | – |
| tag_action | string | – | – |
| tag_filter | string | – | – |
No output schema declared.
No examples provided.
organizze_register_invoice_payment ~147
Registra o pagamento de uma fatura de cartão MANUAL como lançamento, vinculado à fatura. Para cartões automáticos use inform_invoice_payment. Prefira NOMES de cartão/conta. Liste faturas com get_credit_card_invoices e passe invoice_date_or_id (id ou YYYY-MM) — nunca invente. Bulk support: accepts invoice_date_or_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| credit_card | string | yes | – |
| date | string | yes | – |
| invoice_date_or_id | string | – | – |
| invoice_date_or_ids | array | – | – |
| observation | string | – | – |
| source_account | string | – | – |
No output schema declared.
No examples provided.
organizze_resolve_entity ~66
Resolve um nome aproximado para o id/uuid real de conta, cartão ou categoria. Use ANTES de uma escrita para evitar ids inventados. Quando ambíguo, retorna as correspondências.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
organizze_search_transactions ~125
Busca transações por texto na descrição, observação ou tags (ex.: "iFood", "Uber", "salário"). Paginação via page/per_page; sem datas, o padrão são os últimos 6 meses.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_type | string | – | – |
| end_date | string | – | – |
| max_amount | number | – | – |
| min_amount | number | – | – |
| page | number | – | – |
| per_page | number | – | – |
| query | string | yes | – |
| start_date | string | – | – |
| tags_only | boolean | – | – |
No output schema declared.
No examples provided.
organizze_set_transaction_paid ~98
Marca uma transação como paga/recebida (paid=true) ou não paga (paid=false) em conta MANUAL ("já paguei o aluguel"). Idempotente. Transações automáticas são sempre pagas. Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| paid | boolean | yes | – |
| transaction_id | number | – | – |
| transaction_ids | array | – | – |
| transaction_uuid | string | – | – |
No output schema declared.
No examples provided.
organizze_suggest_categories ~80
Sugere categorias para uma ou mais descrições de transação, usando as edições anteriores do próprio usuário, o histórico já categorizado e padrões globais. Use ANTES de create_transaction ao classificar um lote de descrições. Cada item retorna confidence e semantic_strength para decidir entre aplicar ou confirmar.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
organizze_transactions_list_results ~163
Totais financeiros de um período (receitas, despesas, resultado, saldo, previstos) sem paginar transação por transação. Ideal para "quanto gastei esse mês?", "qual meu saldo?". Padrão: mês atual. Base caixa por padrão (inclui pagamentos de fatura, não compras de cartão); com category_id muda para base por lançamento. Não reconcilie bases diferentes. Bulk support: accepts account_ids, category_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | number | – | – |
| account_ids | array | – | – |
| category_id | number | – | – |
| category_ids | array | – | – |
| end_date | string | – | – |
| list_mode | string | – | – |
| start_date | string | – | – |
No output schema declared.
No examples provided.
organizze_uninform_invoice_payment ~91
Desfaz um "Informar Pagamento" em cartão AUTOMÁTICO (marcador aguardando Open Finance). Não remove pagamentos reais já confirmados. invoice_date_or_id é obrigatório. Bulk support: accepts invoice_date_or_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| credit_card | string | yes | – |
| invoice_date_or_id | string | yes | – |
| invoice_date_or_ids | array | – | – |
No output schema declared.
No examples provided.
organizze_update_account ~107
Atualiza uma conta (nome, descrição, instituição, arquivar). Contas automáticas só permitem nome e archived. Prefira NOME (não invente id). Bulk support: accepts institution_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
| archived | boolean | – | – |
| description | string | – | – |
| hide_balance | boolean | – | – |
| institution_id | string | – | – |
| institution_ids | array | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
organizze_update_budget ~61
Atualiza o valor de um orçamento existente. amount = 0 remove o orçamento. Bulk support: accepts budget_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| budget_id | number | yes | – |
| budget_ids | array | – | – |
No output schema declared.
No examples provided.
organizze_update_category ~90
Atualiza uma categoria (nome, cor, pai, arquivar). Categorias padrão não podem ser excluídas, mas podem ser renomeadas/arquivadas. Prefira NOME (não invente id).
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| category | string | yes | – |
| color | string | – | – |
| name | string | – | – |
| parent | string | – | – |
No output schema declared.
No examples provided.
organizze_update_credit_card ~137
Atualiza um cartão de crédito (nome, bandeira, dias de fatura, limite, arquivar). Cartões automáticos só permitem nome e archived. Prefira NOME (não invente id). Bulk support: accepts payment_account_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| billing_cycle_day | number | – | – |
| billing_due_day | number | – | – |
| credit_card | string | yes | – |
| flag | string | – | – |
| limit | number | – | – |
| name | string | – | – |
| payment_account_id | number | – | – |
| payment_account_ids | array | – | – |
No output schema declared.
No examples provided.
organizze_update_transaction ~198
Atualiza uma transação existente (informe só os campos a alterar). Em transações automáticas só descrição, categoria, observação e tags podem mudar. Prefira NOMES de conta/categoria (não invente ids). O transaction_id/uuid DEVE ser copiado de list_transactions, search_transactions ou get_transaction nesta conexão — nunca invente nem sequencie IDs. Para várias linhas, use mass_update_transactions com filtros. Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| amount | number | – | – |
| category | string | – | – |
| date | string | – | – |
| description | string | – | – |
| observation | string | – | – |
| paid | boolean | – | – |
| tags | string | – | – |
| transaction_id | number | – | – |
| transaction_ids | array | – | – |
| transaction_uuid | string | – | – |
| update_recurrence | string | – | – |
No output schema declared.
No examples provided.
organizze_update_transactions_categories ~91
Define a categoria de VÁRIAS transações em uma chamada, com destino por linha (máx. 200). Ideal após suggest_categories quando cada linha tem categoria diferente. Prefira category (NOME) e IDs só de list/suggest deste turno — nunca invente. Se a mesma categoria vale para todas, prefira mass_update_transactions com filtro.
| Name | Type | Req | Description |
|---|---|---|---|
| updates | array | yes | – |
No output schema declared.
No examples provided.
organizze_update_transactions_descriptions ~99
Substitui a descrição de VÁRIAS transações em uma chamada (máx. 200). Cada item: transaction_id (ou id) OU transaction_uuid (ou uuid) + description (ou new_description). IDs só de list_transactions/search deste turno. Aceita um único objeto em vez de array. Se a mesma descrição/regra vale para todas, prefira mass_update_transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| updates | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| conversation | string | – | – |
| message | string | yes | – |
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.
How do I install the Organizze MCP server?
Organizze is a hosted endpoint at https://api.mcp.ai/p_organizze, 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
claude mcp add --transport http mcp-dir-organizze-mcp 'https://api.mcp.ai/p_organizze'
What is the Organizze MCP server?
Organizze is an MCP server listed in the public MCP registry as io.github.mcp-dir/organizze-mcp. Your Organizze finances in natural language: consolidated balances, monthly overview, transaction se. This page covers its hosted endpoint (https://api.mcp.ai/p_organizze).
Is the Organizze MCP server safe to use?
Organizze scores 78 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 Organizze MCP server expose?
Organizze exposes 68 tools: organizze_list_accounts, organizze_list_credit_cards, organizze_list_categories, organizze_list_transactions, organizze_list_transferences, and 63 more. Their descriptions and schemas cost roughly 7,487 tokens of context every time the server is loaded.
Does the Organizze MCP server require authentication?
No. We connected to Organizze without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Organizze MCP server still maintained?
Organizze is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Organizze MCP server?
VerifyMCP ran 12 checks on Organizze, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Organizze: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.