mcp-registry/io.favcrm/favcrm/mark_invoice_sent / alternatives
mcp-registry/io.favcrm/favcrm/mark_invoice_sentThe best live alternatives to mcp-registry/io.favcrm/favcrm/mark_invoice_sent right now are mcp-registry/io.github.ainode-tech/accounting-mcp/send_invoice, mcp-registry/now.shiply/shiply/contract_send, mcp-registry/io.github.timwal78/mcp-x402/proof_invoice, mcp-registry/io.github.termi24/eyeot-erp/create_invoice, mcp-registry/io.github.loved0543-dotcom/kdata-gate/build_invoice_draft_packet — capability-matched and ranked by current reliability. mcp-registry/io.favcrm/favcrm/mark_invoice_sent itself is currently "healthy".
mcp-registry/io.github.ainode-tech/accounting-mcp/send_invoice is the top capability-matched alternative that's live right now. Other options: mcp-registry/now.shiply/shiply/contract_send, mcp-registry/io.github.timwal78/mcp-x402/proof_invoice, mcp-registry/io.github.termi24/eyeot-erp/create_invoice, mcp-registry/io.github.loved0543-dotcom/kdata-gate/build_invoice_draft_packet. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.favcrm/favcrm/mark_invoice_sent's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.favcrm%2Ffavcrm%2Fmark_invoice_sent.
By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.favcrm%2Ffavcrm%2Fmark_invoice_sent
or MCP find_alternatives. Check mcp-registry/io.favcrm/favcrm/mark_invoice_sent's live status: https://glimind.com/tool/mcp-registry/io.favcrm/favcrm/mark_invoice_sent.