# io.kolmo.www/kolmo-mcp-server (remote · www.kolmo.io)

Seattle GC (SEDBE #D700031098). Residential & public works: estimates, ROI, permits, quotes.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.kolmo.io`: 70/100 (this document), [markdown](https://verifymcp.io/servers/io-kolmo-www-kolmo-mcp-server/www.md), [page](https://verifymcp.io/servers/io-kolmo-www-kolmo-mcp-server/www)

## Channel facts

- Endpoint: `https://www.kolmo.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.11`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 36 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 5479 tokens (~152/item across 36 items; 36 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-kolmo-www-kolmo-mcp-server https://www.kolmo.io/mcp
```

### Codex

```toml
[mcp_servers.io-kolmo-www-kolmo-mcp-server]
url = "https://www.kolmo.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-kolmo-www-kolmo-mcp-server": {
      "type": "remote",
      "url": "https://www.kolmo.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-kolmo-www-kolmo-mcp-server --url https://www.kolmo.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-kolmo-www-kolmo-mcp-server:
    url: "https://www.kolmo.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-kolmo-www-kolmo-mcp-server": {
      "type": "http",
      "url": "https://www.kolmo.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (36)

### `get_business_info` (~30 tokens)

Get Kolmo Construction company information: contact details, hours, service area, specializations, and tools.

### `list_services` (~73 tokens)

List all residential remodeling services with slugs, descriptions, and page URLs. Use `search` to find by keyword.

Input parameters:

- `limit` (integer): Max results (default 50)
- `offset` (integer): Pagination offset (default 0)
- `search` (string): Filter by keyword in service name or description

### `get_service` (~59 tokens)

Get full details for a specific residential service by its slug. If not found, returns a list of available slugs to help you pick the right one.

Input parameters:

- `slug` (string, required): The URL slug, e.g. "kitchen-remodeling"

### `list_commercial_services` (~130 tokens)

List commercial construction services. Optionally filter by category: office, retail, industrial, hospitality, public. The "public" category covers public works and government contracts — Kolmo is WA State SEDBE-certified (#D700031098), King County SCS-certified (#7259), prevailing wage compliant, and MRSC Small Works Roster eligible (projects under $350K).

Input parameters:

- `category` (string): Filter: office, retail, industrial, hospitality, public
- `limit` (integer): Max results (default 50)
- `offset` (integer): Pagination offset (default 0)

### `list_procurement_codes` (~125 tokens)

List Kolmo's vendor procurement codes (NAICS, NIGP, UNSPSC) for government and agency portals such as SAM.gov, WA WEBS, OpenGov, MRSC, King County, and City of Seattle. Use this when vetting Kolmo for gov bids or setting up Kolmo as a vendor. Primary NAICS is 236118 (Residential Remodelers); secondary codes cover commercial building and specialty trades (painting, flooring, drywall, windows, roofing, siding, etc.).

Input parameters:

- `system` (string): Code system to return (default: all)

### `list_projects` (~89 tokens)

List completed remodeling projects with before/after photos and locations. Filter by category or keyword.

Input parameters:

- `category` (string): Filter: kitchen, bathroom, full-home, outdoor, basement
- `limit` (integer): Max results (default 20)
- `offset` (integer): Pagination offset (default 0)
- `search` (string): Filter by keyword in project title, description, or location

### `get_project` (~52 tokens)

Get full details for a specific project by its slug, including before/after images and testimonial. If not found, returns a list of available slugs.

Input parameters:

- `slug` (string, required): The URL slug of the project

### `get_project_testimonials` (~154 tokens)

Get customer testimonials tied to a specific project (by slug or keyword) from the testimonials table. Returns star rating, customer name, project name, and quote text. Use to source social proof or case-study quotes for a particular job. For unfiltered reviews, use list_reviews.

Input parameters:

- `keyword` (string): Keyword to fuzzy-match against testimonial project name or content (e.g. "kitchen", "deck")
- `limit` (integer): Max results (default 10)
- `minRating` (integer): Minimum star rating (1-5, default 1)
- `projectSlug` (string): Project slug to match (e.g. "ballard-kitchen-remodel"). Falls back to title match.

### `list_blog_posts` (~102 tokens)

List published blog posts about home remodeling, renovation costs, and construction tips. Filter by tag or author name.

Input parameters:

- `author` (string): Filter posts by author name, e.g. "Marcus Reid"
- `limit` (integer): Max posts to return (default 20)
- `offset` (integer): Pagination offset (default 0)
- `tag` (string): Filter posts by tag, e.g. "flooring", "deck", "painting"

### `get_blog_post` (~36 tokens)

Get the full markdown content of a blog post by its slug.

Input parameters:

- `slug` (string, required): The URL slug of the blog post

### `list_blog_tags_and_categories` (~52 tokens)

Enumerate every tag and category used across Kolmo's published blog posts, with post counts. Use this to discover what topics Kolmo publishes on before calling list_blog_posts, or to surface coverage gaps.

### `submit_contact_request` (~116 tokens)

Submit a contact or quote request to Kolmo Construction on behalf of a user. Set dryRun: true to preview what would be sent without actually submitting.

Input parameters:

- `dryRun` (boolean): If true, validate and preview without submitting (default false)
- `email` (string, required): Email address
- `message` (string, required): Project description or question
- `name` (string, required): Full name
- `phone` (string): Phone number (optional)
- `service` (string): Service needed, e.g. "kitchen remodel"

### `list_project_types` (~34 tokens)

List all 11 supported calculator project types with their required input fields and descriptions. Useful for discovery before calling get_estimate.

### `get_material_options` (~66 tokens)

Get available material choices for a project type — flooring types, paint grades, decking materials, kitchen/bath scope tiers, ADA modifications, etc. Use the returned IDs in the project fields of get_estimate.

Input parameters:

- `projectType` (string, required): The project type to list materials for

### `get_estimate` (~1321 tokens)

Calculate a Seattle-area cost estimate. Returns total, material, labor costs, days, and itemized line items.

Material IDs: use get_material_options to get exact IDs, or pass a close match (e.g. "lvp", "composite", "cedar") and the server will resolve it. If ambiguous, the error message lists valid options.

Required fields by projectType:

interior-painting: rooms (Array<{id,name,length(ft),width(ft),height(6-30),paintCeiling(bool),paintTrim(bool),doorCount,windowCount,surfaceCondition("new-drywall"|"good-condition"|"poor-condition"),trimComplexity("baseboards-only"|"simple-trim"|"complex-trim"),wallTexture("smooth"|"light-texture"|"heavy-texture"),roomEmpty(bool)}>) | paintQuality (material ID) | paintFinish ("flat"|"eggshell"|"satin"|"semi-gloss"|"gloss") | includesPrimer (bool) | majorColorChange (bool)

exterior-painting: wallArea(sqft) | trimArea(sqft) | doorCount | paintQuality (material ID) | surfacePrepLevel ("minimal"|"moderate"|"extensive") | includesPrimer (bool) | stories (1-3) | colorChange (bool)

flooring: rooms (Array<{id,name,length(ft),width(ft)}>) | flooringMaterial (material ID, e.g. "standard-lvp-flooring","engineered-hardwood-oak","ceramic-tile-12x24") | includesUnderlayment (bool) | underlaymentType? (material ID) | includesBaseboard (bool) | baseboardType? (material ID) | baseboardLinearFeet? | includesRemoval (bool) | removalType? ("carpet"|"tile"|"hardwood") | includesSubfloorPrep (bool) | transitionCount

deck: deckType ("new"|"existing") | dimensions ({length,width,height(ft above ground)}) | deckingMaterial (material ID, e.g. "pressure-treated-decking","composite-decking-basic") | framingMaterial (material ID, e.g. "pressure-treated-framing-2x6") | includesRailing (bool) | railingMaterial? (material ID) | railingLinearFeet? | includesStairs (bool) | stairSteps? (0-20) | deckShape ("rectangle"|"l-shape"|"angled-corners"|"multi-level") | skirtingType ("none"|"lattice"|"matching-board")

windows: windows (Array<{id,windowType(e.g."double-…

Input parameters:

- `project` (object, required): Project input fields — see tool description for required fields per projectType.
- `projectType` (string, required): The type of project

### `list_reviews` (~99 tokens)

List customer reviews and testimonials for Kolmo Construction. Combines verified Google reviews and on-site testimonials. Filter by minimum star rating.

Input parameters:

- `limit` (integer): Max results (default 20)
- `minRating` (integer): Minimum star rating to include (1-5, default 1)
- `offset` (integer): Pagination offset (default 0)
- `source` (string): Source to query: all (default), google, testimonials

### `check_permit_requirements` (~255 tokens)

Check whether a residential construction project in King/Pierce/Snohomish counties requires a permit. Returns timeline, fee notes, inspection sequence, required submittals, and official source URL — preferring jurisdiction-verified rules. Use for "Do I need a permit to build a deck in Seattle?" or "What permits are required for a kitchen remodel in Bellevue?". Pass `address` to also receive the structured per-item SubmittalSet (`submittals_v2`) from the unified permit engine — Seattle is full SDCI fidelity, other 9 verified cities are wa-baseline-stub.

Input parameters:

- `address` (string): Full street address — when provided, the response includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor). Overrides `location` for jurisdiction routing.
- `location` (string): City or jurisdiction slug, e.g. "Seattle", "Bellevue", "Tacoma", "king-county-unincorporated"
- `projectType` (string): Project type — canonical: kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition

### `get_permit_rule_details` (~229 tokens)

Enumerate permit rules with full detail — timeline, fee model, inspection sequence, submittals, required contractor specialties. Filter by jurisdiction slug or keyword. Use for "what does a Seattle ADU permit require?" or to list all rules for a jurisdiction. Pass `address` to also receive `submittals_v2` (structured per-item SubmittalSet from the unified resolver) per rule.

Input parameters:

- `address` (string): Full street address — when provided, each result row also includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor).
- `jurisdiction` (string): Jurisdiction slug or display name (e.g. "seattle", "bellevue", "tacoma")
- `keyword` (string): Keyword in project type, trigger, thresholds, or notes (e.g. "deck", "adu", "egress")
- `limit` (integer): Max results (default 50)
- `onlyAuthoritative` (boolean): If true, exclude legacy LLM-seeded rows. Default true.

### `match_contractor_to_permit` (~152 tokens)

Cross-reference a WA contractor's L&I license specialty against a permit's required specialties. Returns whether the contractor is qualified to pull/work the permit, with explicit gap callouts (e.g. "missing electrical specialty 02"). Combines real-time L&I data with Kolmo's authoritative permit catalog.

Input parameters:

- `contractorQuery` (string, required): Contractor license number or business name
- `jurisdictionSlug` (string, required): Permit jurisdiction slug (e.g. "seattle", "tacoma")
- `projectType` (string, required): Canonical project type (kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition)

### `estimate_permit_fee` (~135 tokens)

Estimate the permit fee for a residential project based on jurisdiction, project type, and project valuation. Returns numeric breakdown when the authoritative rule has fee inputs, or qualitative feeNotes (with source URL) when the city publishes fees only as PDFs/spreadsheets. Never fabricates dollar amounts.

Input parameters:

- `jurisdictionSlug` (string, required): Jurisdiction slug, e.g. "seattle", "bellevue", "tacoma" (use list_permit_jurisdictions to discover)
- `projectType` (string, required): Canonical project type
- `valuationUsd` (number, required): Project valuation in USD (materials + labor)

### `resolve_permit_submittals` (~284 tokens)

Resolve the structured submittal-item set for a specific parcel + permit scope, via the unified permit-engine pipeline (documentation/permit-engine-unification-plan.md). Use this when you need the per-item checklist (with triggers, source citations, filler actor, gap-resolution path) — not just the rule-level summary that check_permit_requirements returns. Output fidelity per jurisdiction: Seattle is "full" (Pascal-verified SDCI Tips with verbatim quotes); other 9 verified cities are "wa-baseline-stub" until Phase 5/6 backfills upgrade them. Unverified jurisdictions return no-spec.

Input parameters:

- `address` (string, required): Full street address — geocoded to a parcel and matched to a jurisdiction provider
- `envelopeChange` (boolean): Project alters the building envelope (windows, doors, siding, roof). Default false. Drives WSEC triggers.
- `projectValuationUsd` (number): Project valuation in USD
- `scope` (string, required): Permit scope — the (project-type x work-class) identifier the provider catalogs by
- `structuralChange` (boolean): Project involves a structural change (header, framing, lateral). Default false. Drives several triggers.
- `totalFloorAreaSqft` (number): Total floor area in sqft. Used by SEPA threshold (>=12000) and other size-based triggers.

### `list_permit_jurisdictions` (~97 tokens)

List the jurisdictions in Kolmo's permit catalog (King, Pierce, Snohomish counties). Returns portal URLs, contact info, code-cycle metadata, and verification status. Use to discover which cities are supported and where to submit permits.

Input parameters:

- `county` (string): Filter by county
- `verifiedOnly` (boolean): If true, only return rows where portal_url is populated (verified from official source). Default false.

### `lookup_parcel_by_address` (~193 tokens)

Address-first parcel lookup powering the /permits experience. Geocodes a Seattle-area address (King, Pierce, or Snohomish County, WA), resolves the parcel from the county GIS, and returns zoning, setbacks, overlays (shoreline / ECA / flood / historic), lot area, jurisdiction routing, and prior-permit history. Every fact is cited to the city/county source. Use for "what can be built at 123 Main St Seattle?" or before calling check_permit_requirements / estimate_permit_fee for a specific parcel.

Input parameters:

- `address` (string, required): Full street address (e.g., "1234 NE 65th St, Seattle, WA 98115"). Must be in King, Pierce, or Snohomish County, WA.
- `forceRefresh` (boolean): Skip the 30-day cache and re-fetch from county GIS + overlay sources. Default false.

### `parse_project_description` (~217 tokens)

Parse a homeowner's natural-language project description into structured permit-relevant fields: projectType (kitchen|bathroom|deck|adu|fence|...), areaSqft, heightClass, attached/detached, position, and materials. Returns confidence + a single clarifyingQuestion when the parse is ambiguous. Use this before calling check_permit_requirements / estimate_permit_fee when you only have free text from the homeowner. Backed by Gemini 2.5 Pro with a constrained JSON schema.

Input parameters:

- `cityName` (string): City name (e.g., "Seattle", "Bellevue")
- `description` (string, required): Free-text project description (e.g., "I want to add a 200 sqft deck off my master bedroom on the second floor")
- `jurisdictionSlug` (string): Jurisdiction slug from lookup_parcel_by_address (helps disambiguate region-specific terminology)
- `zoningCode` (string): Zoning code from lookup_parcel_by_address (e.g., "NR2", "LR1")

### `answer_permit_question` (~153 tokens)

Grounded permit Q&A for a specific Seattle-area address. Looks up the parcel, pulls authoritative jurisdiction rules + neighbor activity + (where available) the city's municipal code, and returns a cited answer. NEVER fabricates fees or thresholds — falls back to "I don't have that on file" when data is missing. Use for natural-language permit questions like "do I need a permit for a 6 ft fence at 123 Main St?" or "what permits does an ADU at this address require?"

Input parameters:

- `address` (string, required): Full street address in King, Pierce, or Snohomish County, WA
- `question` (string, required): A single permit/zoning/setback/overlay question about this parcel

### `get_neighbor_permit_activity` (~118 tokens)

Aggregate permit activity within ~1500 ft of a Seattle-area parcel over the last 24 months. Returns total count, breakdown by category, and recent example permits (anonymized — no addresses). Sourced from city open-data portals (Socrata). Currently supports Seattle; other jurisdictions return jurisdictionSupported=false. Use to gauge neighborhood activity before quoting an unusual project, or to set homeowner expectations on what neighbors have built.

Input parameters:

- `address` (string, required): Full street address in King, Pierce, or Snohomish County, WA

### `get_permit_data_freshness` (~140 tokens)

Source-freshness telemetry for the permit catalog. Returns per-jurisdiction last-verified dates plus the latest results from the weekly source-of-truth snapshot pipeline (HTTP status, change-detection vs prior fetch). Use to answer "how current is this fee/timeline?" or to surface confidence in a permit answer. The /permits/data-quality page exposes the same signals.

Input parameters:

- `jurisdictionSlug` (string): Optional jurisdiction filter (e.g., "seattle", "bellevue"). When omitted, returns rollup across all jurisdictions.
- `limit` (integer): Max snapshots to return (default 50, newest first)

### `get_material_catalog` (~114 tokens)

Browse the full material catalog with pricing — flooring types, paint grades, decking materials, siding, windows, fencing, and more. Use category to filter. Returns material IDs compatible with get_estimate.

Input parameters:

- `category` (string): Filter by category: painting, flooring, decking, siding, windows, fencing, landscaping
- `limit` (integer): Max results (default 50)
- `offset` (integer): Pagination offset (default 0)
- `search` (string): Filter by keyword in material name or description

### `get_weather_window` (~99 tokens)

Check if upcoming weather in Seattle is suitable for an exterior construction project. Returns a day-by-day forecast with go/no-go recommendations based on project-specific requirements (temperature, rain, wind). Perfect for scheduling exterior painting, decking, roofing, landscaping, siding, or fencing.

Input parameters:

- `days` (integer): Number of days to forecast (1-14, default 7)
- `projectType` (string, required): Type of project to check weather suitability for

### `get_neighborhood_project_activity` (~103 tokens)

See what remodeling projects Kolmo Construction has completed in a specific Seattle neighborhood or city. Returns project counts by category, example projects, and typical project descriptions. Great for hyperlocal social proof — e.g. "Has Kolmo worked in Ballard?" or "What has Kolmo done in Capitol Hill?"

Input parameters:

- `neighborhood` (string, required): Seattle neighborhood or city, e.g. "Ballard", "Capitol Hill", "Bellevue", "Queen Anne"

### `check_service_area_coverage` (~107 tokens)

Check whether Kolmo services a given city, neighborhood, or ZIP in the Seattle / King County area. Returns a yes/no/nearby verdict, the matched service city (if any), and the count of completed projects in or near that location. Use before recommending Kolmo to a lead to confirm coverage.

Input parameters:

- `location` (string, required): City, neighborhood, or ZIP to check, e.g. "Ballard", "Bellevue", "98105", "Tacoma"

### `get_project_roi` (~149 tokens)

Get the estimated return on investment (ROI) for a home remodeling project in the Seattle area. Based on Remodeling Magazine Cost vs. Value data for the Pacific Northwest. Helps homeowners decide which projects add the most resale value — e.g. "What ROI does a kitchen remodel get in Seattle?" or "Which remodel pays off the most?"

Input parameters:

- `estimatedCost` (number): Your estimated project budget in USD. If provided, returns expected resale value added.
- `projectType` (string): Type of project, e.g. "kitchen", "bathroom", "deck", "windows", "siding", "ADU", "basement". Omit to see all projects ranked by ROI.

### `check_contractor_license_status` (~97 tokens)

Look up any Washington State contractor's license, bond, and insurance status using public L&I data (updated daily). Works for Kolmo or any competitor. Great for verifying a contractor before hiring — checks if they are licensed, bonded, and insured in WA.

Input parameters:

- `query` (string, required): Contractor license number (e.g. "KOLMOL*753JS") or business name (e.g. "Kolmo Construction")

### `get_author_bio` (~82 tokens)

Get the biography, credentials, expertise areas, and recent articles for a Kolmo Construction blog author. Use this to answer "who wrote this?" or to add author context to blog content.

Input parameters:

- `author` (string, required): Author name or slug, e.g. "Marcus Reid", "marcus-reid", "Emily Chen", "emily-chen"

### `search_content` (~109 tokens)

Search across all Kolmo content — services, projects, and blog posts — with a single keyword query. Returns ranked results grouped by type. Use this instead of calling list_services + list_projects + list_blog_posts separately.

Input parameters:

- `limit` (integer): Max results per type (default 5)
- `query` (string, required): Search keyword or phrase, e.g. "deck Seattle", "kitchen cost", "permit"
- `types` (array): Content types to include (default: all three)

### `get_financing_options` (~108 tokens)

Get home improvement financing options for a Seattle remodeling project. Returns loan types, estimated monthly payments, typical terms, and eligibility notes. Helps homeowners understand how to pay for a remodel — HELOC, home improvement loans, cash-out refinance, and contractor payment plans.

Input parameters:

- `creditProfile` (string): Approximate credit profile: excellent (750+), good (680-749), fair (620-679). Default: good
- `projectBudget` (number, required): Estimated project cost in USD

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-kolmo-www-kolmo-mcp-server/www#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 70
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://www.kolmo.io/mcp
- Repository: https://github.com/Kolmo-Construction/kolmo-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/io-kolmo-www-kolmo-mcp-server/www/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-kolmo-www-kolmo-mcp-server/www/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-kolmo-www-kolmo-mcp-server/www