Home / MCP registry index / io.github.mcp-dir/omie-mcp

Omie

io.github.mcp-dir/omie-mcp in the official MCP registry. Endpoint https://api.mcp.ai/p_omie. Source: github.com/mcp-dir/omie-mcp.

The registry describes it as: Financial & accounting management on Omie (Brazil's leading cloud ERP), payables/receivables, financ

We read its 59 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http omie-mcp https://api.mcp.ai/p_omie

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "omie-mcp": {
      "url": "https://api.mcp.ai/p_omie"
    }
  }
}

VS Code

code --add-mcp '{"name":"omie-mcp","type":"http","url":"https://api.mcp.ai/p_omie"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

omie_list_accounts omie_list_payables omie_get_payable omie_create_payable omie_update_payable omie_settle_payable omie_delete_payable omie_list_receivables omie_get_receivable omie_create_receivable omie_update_receivable omie_settle_receivable omie_delete_receivable omie_list_financial_movements omie_list_checking_accounts omie_get_checking_account_balance omie_create_checking_account omie_update_checking_account omie_delete_checking_account_entry omie_list_customers omie_get_customer omie_create_customer omie_update_customer omie_list_categories omie_list_departments omie_list_projects omie_list_document_types omie_list_invoices omie_transfer_between_accounts omie_create_checking_account_entry omie_update_checking_account_entry omie_get_checking_account_entry omie_list_checking_account_entries omie_cancel_payment omie_cancel_receipt omie_reconcile_receipt omie_unreconcile_receipt omie_upsert_payables_batch omie_upsert_receivables_batch omie_get_invoice omie_get_invoice_xml omie_upload_attachment omie_list_attachments omie_get_attachment omie_delete_attachment omie_settle_payables_batch omie_settle_receivables_batch omie_list_category_types omie_get_category omie_create_category omie_update_category omie_cadastrar omie_lancar show_version report_bug connect toolkit_info marketplace authenticate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-omie-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-omie-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Finance and markets MCP servers