Should my agent depend on the MCP server io.github.mcp-dir/omie-mcp?

Verdict: allow — gateway — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Omie

io.github.mcp-dir/omie-mcp

Financial & accounting management on Omie (Brazil's leading cloud ERP), payables/receivables, financ

— the operator's own registry description reported

Publisher io.github.mcp-dir · first seen 2026-08-12 · endpoint https://api.mcp.ai/p_omie

allow

verdict

gateway

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — gateway — safe to depend on

Cluster gateway · distinctiveness 0.542 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency778 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools35

vs populationhigh

capabilities1

harnessB

Trust — can it rely on it?

identityfarm_member

servers on its host99

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_956a6b2c63106cb33ab14431 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

authenticate connect marketplace omie_create_checking_account omie_create_customer omie_create_payable omie_create_receivable omie_delete_checking_account_entry omie_delete_payable omie_delete_receivable omie_get_checking_account_balance omie_get_customer omie_get_payable omie_get_receivable omie_lancar omie_list_accounts omie_list_categories omie_list_checking_accounts omie_list_customers omie_list_departments omie_list_document_types omie_list_financial_movements omie_list_invoices omie_list_payables omie_list_projects omie_list_receivables omie_settle_payable omie_settle_receivable omie_update_checking_account omie_update_customer omie_update_payable omie_update_receivable report_bug show_version toolkit_info

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	35/35	✓
has a description	35/35	✓
description is substantive	35/35	✓
parameters are typed	35/35	✓
parameters are described	3/35	3/35

35 of 35 tools graded · 35 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.9.241

server version mcp-ai

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:49Z	ok_tools	200	778	2025-06-18
2026-08-12T05:35:02Z	ok_tools	200	4050	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.mcp-dir/omie-mcp.svg)](https://robinsaige.com/s/io.github.mcp-dir/omie-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview