Home / MCP registry index / io.kolmo.www/kolmo-mcp-server

io.kolmo.www/kolmo-mcp-server

io.kolmo.www/kolmo-mcp-server in the official MCP registry. Endpoint https://www.kolmo.io/mcp. Source: github.com/Kolmo-Construction/kolmo-mcp-server.

The registry describes it as: WA permit rules (city + state baseline, cited), parcel zoning, L&I checks, Seattle estimates & ROI

We read its 42 tools on 2026-10-22. 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.

Tools it advertises

get_business_info list_services get_service list_commercial_services list_procurement_codes list_projects get_project get_project_testimonials list_blog_posts get_blog_post list_blog_tags_and_categories submit_contact_request list_project_types get_material_options get_estimate list_reviews check_permit_requirements get_permit_rule_details match_contractor_to_permit estimate_permit_fee resolve_permit_submittals list_permit_jurisdictions lookup_parcel_by_address parse_project_description answer_permit_question get_neighbor_permit_activity get_permit_timeline get_common_plan_review_corrections get_permit_data_freshness get_material_catalog get_weather_window get_neighborhood_project_activity check_service_area_coverage get_project_roi check_contractor_license_status get_author_bio search_content get_financing_options request_walkthrough get_my_quote respond_to_quote get_payment_link

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-kolmo-www-kolmo-mcp-server/badge.svg)](https://lazaretto.dev/mcp-registry/io-kolmo-www-kolmo-mcp-server)

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.