mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_fee / alternatives
mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_feeThe best live alternatives to mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_fee right now are mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_breakdown, mcp-registry/io.github.baneado98/muni-dev-cost/estimate_dev_cost, mcp-registry/io.github.baneado98/muni-dev-cost/estimate_by_units, mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_source, mcp-registry/io.github.baneado98/muni-dev-cost/get_dev_costs — capability-matched and ranked by current reliability. mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_fee itself is currently "healthy".
mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_breakdown is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.baneado98/muni-dev-cost/estimate_dev_cost, mcp-registry/io.github.baneado98/muni-dev-cost/estimate_by_units, mcp-registry/io.github.baneado98/muni-dev-cost/get_fee_schedule_source, mcp-registry/io.github.baneado98/muni-dev-cost/get_dev_costs. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_fee's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.kolmo.www%2Fkolmo-mcp-server%2Festimate_permit_fee.
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.kolmo.www%2Fkolmo-mcp-server%2Festimate_permit_fee
or MCP find_alternatives. Check mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_fee's live status: https://glimind.com/tool/mcp-registry/io.kolmo.www/kolmo-mcp-server/estimate_permit_fee.