MCP servers observed by Lowdown
io.github.douglac/contaazul-mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 58 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.douglac/contaazul-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.douglac/contaazul-mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 3 compared days.
- 2026-11-18: descriptions changed, server version changed
- 2026-11-15: input or output schemas changed, descriptions changed, server version changed
- 2026-11-12: server version changed
What tools does it list?
58 tools on 2026-11-18:
authenticateconnectcontaazul_cancel_chargecontaazul_contract_next_numbercontaazul_contract_writecontaazul_create_budgetcontaazul_delete_budgetscontaazul_delete_contractcontaazul_delete_settlementcontaazul_generate_chargecontaazul_get_account_balancecontaazul_get_budgetcontaazul_get_chargecontaazul_get_companycontaazul_get_contractcontaazul_get_initial_balancecontaazul_get_installmentcontaazul_get_invoice_nfecontaazul_get_personcontaazul_get_salecontaazul_get_settlementcontaazul_list_accountscontaazul_list_budgetscontaazul_list_categoriescontaazul_list_changed_eventscontaazul_list_contractscontaazul_list_cost_centerscontaazul_list_financial_accountscontaazul_list_installmentscontaazul_list_invoices_nfecontaazul_list_invoices_nfsecontaazul_list_payablescontaazul_list_peoplecontaazul_list_productscontaazul_list_receivablescontaazul_list_sale_itemscontaazul_list_salescontaazul_list_servicescontaazul_list_settlementscontaazul_list_transferscontaazul_payable_createcontaazul_person_deletecontaazul_person_write_createcontaazul_person_write_updatecontaazul_product_writecontaazul_receivable_createcontaazul_sale_cancelcontaazul_sale_write_createcontaazul_sale_write_updatecontaazul_service_writecontaazul_settle_installmentcontaazul_terminate_contractcontaazul_update_installmentcontaazul_update_settlementmarketplacereport_bugshow_versiontoolkit_info
MCP Registry declaration
- Registry name:
io.github.douglac/contaazul-mcp - Declared version: 0.1.0
- Status: active
- Declared hosts:
api.mcp.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.douglac/contaazul-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.douglac/contaazul-mcp?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).