Omie
REMOTE · API.MCP.AI · SCANNED SEP 27
Financial & accounting management on Omie (Brazil's leading cloud ERP), payables/receivables, financ
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 8760 tokens (~148/item across 59 items; 59 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 60 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
How do I install the Omie MCP server?
Omie is a hosted endpoint at https://api.mcp.ai/p_omie, 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-omie-mcp 'https://api.mcp.ai/p_omie'
{
"mcpServers": {
"mcp-dir-omie-mcp": {
"url": "https://api.mcp.ai/p_omie"
}
}
} {
"servers": {
"mcp-dir-omie-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_omie"
}
}
} [mcp_servers.mcp-dir-omie-mcp] url = "https://api.mcp.ai/p_omie"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcp-dir-omie-mcp": {
"type": "remote",
"url": "https://api.mcp.ai/p_omie",
"enabled": true
}
}
} openclaw mcp add mcp-dir-omie-mcp --url 'https://api.mcp.ai/p_omie' --transport streamable-http
mcp_servers:
mcp-dir-omie-mcp:
url: "https://api.mcp.ai/p_omie" {
"McpServers": {
"mcp-dir-omie-mcp": {
"Transport": "http",
"Url": "https://api.mcp.ai/p_omie"
}
}
} assistant mcp add mcp-dir-omie-mcp -t streamable-http -u 'https://api.mcp.ai/p_omie'
{
"mcpServers": {
"mcp-dir-omie-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_omie"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 −1
- Stability: pass → 0.97 functional
- 14 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “omie_lancar” rewrote its description, which is the text the model reads security
- Tool “omie_list_financial_movements” rewrote its description, which is the text the model reads security
- Schema quality: 7223 → 8760 ▼ functional
- Server version: 0.9.346 → 0.9.351 functional
- New tool “omie_cadastrar” functional
- New tool “omie_create_category” functional
- New tool “omie_get_category” functional
- New tool “omie_list_category_types” functional
- New tool “omie_settle_payables_batch” functional
- New tool “omie_settle_receivables_batch” functional
- New tool “omie_update_category” functional
- “omie_get_checking_account_balance” added an optional parameter “apenas_nao_conciliados” cosmetic
- “omie_lancar” added an optional parameter “categorias” cosmetic
- “omie_lancar” added an optional parameter “departamentos” cosmetic
- “omie_lancar” added an optional parameter “ignorar_duplicidade” cosmetic
- “omie_lancar” added an optional parameter “parcelamento” cosmetic
- “omie_lancar” added an optional parameter “projeto” cosmetic
- “omie_list_financial_movements” added an optional parameter “apenas_nao_conciliados” cosmetic
- “omie_lancar” made “categoria” optional cosmetic
- 10 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.345 → 0.9.346 functional
- 9 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.343 → 0.9.345 functional
- 7 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.342 → 0.9.343 functional
- 6 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.340 → 0.9.342 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 27 Sept 2026 · Probed https://api.mcp.ai/p_omie
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 | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 796a3b1f576e3f2e133c5d19d8f7be3b |
| 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_omie | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_omie | 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 →
omie_update_customer ~95
Edita um cliente/fornecedor existente (AlterarCliente). `data` é um JSON string que DEVE conter a chave do cadastro (codigo_cliente_omie id Omie OU codigo_cliente_integracao) + os campos a alterar (ex.: razao_social, email, telefone1_numero, endereco). Consulte antes com omie_get_customer.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | yes | – |
No output schema declared.
No examples provided.
omie_update_payable ~101
Edita uma conta a pagar existente (AlterarContaPagar). `data` é um JSON string que DEVE conter a chave do lançamento (codigo_lancamento_omie OU codigo_lancamento_integracao) + os campos a alterar (ex.: data_vencimento, valor_documento, codigo_categoria, observacao). Consulte antes com omie_get_payable.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | yes | – |
No output schema declared.
No examples provided.
omie_update_receivable ~101
Edita uma conta a receber existente (AlterarContaReceber). `data` é um JSON string que DEVE conter a chave do lançamento (codigo_lancamento_omie OU codigo_lancamento_integracao) + os campos a alterar (ex.: data_vencimento, valor_documento, codigo_categoria, observacao). Consulte antes com omie_get_receivable.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | yes | – |
No output schema declared.
No examples provided.
omie_upload_attachment ~485
Anexa um arquivo (comprovante, boleto, NF em PDF/PNG…) a um documento da Omie — IncluirAnexo. É o par de omie_lancar/omie_settle_payable: lançou ou deu baixa, anexa o comprovante sem abrir a tela web. - tabela: onde o documento vive (ex.: "conta-pagar", "conta-receber"). - id: o id do documento NAQUELA tabela (conta a pagar/receber = codigo_lancamento_omie, veja omie_get_payable). - arquivo: informe UMA forma — file_url (a plataforma baixa da URL, precisa ser acessível publicamente), upload_id (arquivo já enviado, veja abaixo) ou file_base64 (só arquivo pequeno cujos bytes você REALMENTE tem; NUNCA pra anexo da conversa). file_name é obrigatório em file_url/file_base64 e a Omie NÃO aceita nome com mais de um ponto ("nota.fiscal.pdf"). - Arquivo ANEXADO na conversa ou no computador do usuário: NÃO tente ler o conteúdo nem montar file_base64 (você recebe o texto extraído, não os bytes do arquivo, e o upload sairia corrompido). Chame esta tool SEM arquivo, passando file_path se souber o caminho do anexo: ela devolve um comando pronto de upload. Execute esse comando no seu sandbox de execução de código (ou peça pro usuário rodar no terminal) e chame de novo com o `upload_id` E o `file_name` que ela devolveu. O arquivo é compactado e enviado pela plataforma; você não precisa zipar nada. Depois de anexar, a cópia temporária do arquivo é apagada do nosso lado, ela existe só pra intermediar o upload. Bulk support: accepts ids, upload_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| codigo_integracao | string | – | – |
| file_base64 | string | – | – |
| file_name | string | – | – |
| file_path | string | – | – |
| file_url | string | – | – |
| id | – | yes | – |
| ids | array | – | – |
| tabela | string | yes | – |
| upload_code | string | – | – |
| upload_id | string | – | – |
| upload_ids | array | – | – |
No output schema declared.
No examples provided.
omie_upsert_payables_batch ~230
Cria OU atualiza VÁRIAS contas a pagar numa chamada (UpsertContaPagarPorLote). É o caminho pra mexer em massa (trocar categoria, conta corrente etc.) sem uma chamada por título. ⚠️ É UPSERT, não patch: o registro é gravado com o que você mandar, então inclua os campos que quer PRESERVAR, não só os que quer mudar — leia antes com omie_list_payables/omie_get_payable. A chave de cada item é `codigo_lancamento_integracao` (ou `codigo_lancamento_omie`). ✅ Funciona em título JÁ BAIXADO/PAGO: dá pra corrigir categoria, cliente/fornecedor etc. em massa SEM cancelar a baixa (a baixa é preservada e o status continua PAGO). `data` é um JSON string: `{"lote": 1, "conta_pagar_cadastro": [ {…}, {…} ]}`.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | yes | – |
No output schema declared.
No examples provided.
omie_upsert_receivables_batch ~115
Cria OU atualiza VÁRIAS contas a receber numa chamada (UpsertContaReceberPorLote). Mesmas regras do omie_upsert_payables_batch: é UPSERT (mande os campos a preservar) e a chave de cada item é `codigo_lancamento_integracao`. `data`: `{"lote": 1, "conta_receber_cadastro": [ {…} ]}`.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | 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.
What is the Omie MCP server?
Omie is an MCP server listed in the public MCP registry as io.github.mcp-dir/omie-mcp. Financial & accounting management on Omie (Brazil's leading cloud ERP), payables/receivables, financ. This page covers its hosted endpoint (https://api.mcp.ai/p_omie).
Is the Omie MCP server safe to use?
Omie scores 73 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 Omie MCP server expose?
Omie exposes 59 tools: omie_list_accounts, omie_list_payables, omie_get_payable, omie_create_payable, omie_update_payable, and 54 more. Their descriptions and schemas cost roughly 8,631 tokens of context every time the server is loaded.
Does the Omie MCP server require authentication?
No. We connected to Omie without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Omie MCP server still maintained?
Omie is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.