← Back to search
github-kolmo-construction/kolmo-mcp-server

Kolmo-Construction/kolmo-mcp-server

MCP server for Kolmo Construction — Seattle home remodeling cost estimator

EXECUTIVE VERDICT

Executive verdict

Production trust decision: Block for production
Reason: failing live status + score below evaluation threshold
Next action: revalidate, add safeguards, export policy
Status
Failing
Score
53.0
Transport
streamable-http
Tools
0

Current trust snapshot

Snapshot ID
trustsnap_77d24f668e06e011
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
May 16, 2026 06:53:55 AM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
May 16, 2026 05:37:12 AM UTC
Age: 1.28h • freshness band: Verified in last 24h • display score: 53.05
Production trust decision
Block for production
failing live status + score below evaluation threshold
Readiness class
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, or HTTP token challenge, revalidate now, publish a badge, and configure monitoring.

1. Claim
unclaimed
Start owner claim with GitHub, DNS, or HTTP challenge instructions.
2. Revalidate
POST /v1/servers/github-kolmo-construction/kolmo-mcp-server/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 53.0 - last checked May 16, 2026
4. Monitor
Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.
Badge embed
[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/github-kolmo-construction/kolmo-mcp-server.svg)](https://verify.sentinelsignal.io/servers/github-kolmo-construction/kolmo-mcp-server)

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 35.1 • stale score suppressed:
Policy exports
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/route
Returns allowed tools, blocked tools, approval requirement, and reason.
Authenticated validation
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
Freshly Validated Write-Safe No Critical Risk
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

Production readiness class

Production readiness class
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Critical alerts
1
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
66.2
Based on 1 recent validations, 26 captured checks, and validation age of 1.3 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
1.3h
Lower age means fresher evidence.

Recommended for

Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 83.

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Partially client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; Transport compliance should be in good shape.
Confidence: medium (66.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listError
  • transport_compliance_probeError
  • step_up_auth_probeMissing
  • connector_replay_probeMissing — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Not client-compatible
tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
Confidence: medium (66.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listError
  • transport_compliance_probeError
Write-action publishing
Publishing allowed
Current write surface is bounded enough for cautious review with production policy controls.
Confidence: medium (66.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeOK
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: medium (66.25)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeMissing
  • connector_replay_probeMissing

Why compatibility is limited by client

ChatGPT custom connector
Partially client-compatible
Remediation checklist
  • OpenAI connectors expect OAuth for remote server auth.
  • Dynamic client registration materially improves connector setup.
  • tools/list must succeed.
  • Transport compliance should be in good shape.
  • search fetch only is not yet satisfied
  • write actions present is not yet satisfied
Claude remote MCP
Not client-compatible
Remediation checklist
  • tools/list must succeed.
  • Transport behavior should match Claude-compatible HTTP expectations.
  • A useful Claude integration needs at least one exposed tool.
  • search fetch only is not yet satisfied
  • write actions present is not yet satisfied
  • oauth configured is not yet satisfied
Write-safe publishing
Ready
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Confidence: medium (66.25)
Winning source: live_validation
Triggering alerts
  • server_failing • critical • Latest validation is failing
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partially client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Not client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing allowed action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector compatibility
Compatible with review
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; Transport compliance should be in good shape. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Compatible with review
tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; Transport compliance should be in good shape.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
  • remote_transport: Passes
  • tool_discovery: Likely to fail
  • auth_connect: Passes
  • safe_write_review: Passes

Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
0.0
Validation success 30d
0.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
May 16, 2026 05:37:12 AM UTC Latest validation: failing Score 53.0 with status failing.

Capabilities

Use-case taxonomy
development

Security posture

Tools analyzed
0
High-risk tools
0
Destructive tools
0
Exec tools
0
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
none

Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance

Governance status
OK
Safe to publish
Auth boundary
public_or_unclear
Blast radius
Low
High-risk tools
0
Confirmation signals
none
Safeguard count
0

Status detail: No unsafe write-action governance gaps detected on the latest validation.

ToolRiskFlagsSafeguards
No high-risk tools were detected on the latest run.

Action-controls diff

Need at least two validation runs before diffing action controls.

Why this score?

Access & Protocol
30.5/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
13.7/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
25/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
11.91/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
16.95/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
5.92/8
Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
0.4/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
0/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
2/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
3.5/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
3/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
3.3/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
0.1/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
2.5/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
2/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
2/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
4/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
2/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
2.5/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
0/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
0/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
3/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0.3/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
1.4/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
0.5/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
4/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
2/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3.9/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
0/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
3/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
3/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
2/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
0/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
3/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
0/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
0/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
55.6
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; Transport compliance should be in good shape.
Connector URL: https://www.kolmo.io/mcp
# No OAuth metadata detected.
# Server: github-kolmo-construction/kolmo-mcp-server
Claude Desktop
50.0
blocked
tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
{
  "mcpServers": {
    "kolmo-mcp-server": {
      "command": "npx",
      "args": ["mcp-remote", "https://www.kolmo.io/mcp"]
    }
  }
}
Smithery
60.0
partial
Tool discovery must succeed.; Machine-readable failure semantics should be present.
smithery mcp add "https://www.kolmo.io/mcp"
Generic Streamable HTTP
83.3
compatible
tools/list must succeed.
curl -sS https://www.kolmo.io/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
Critical Ensure tools/list succeeds consistently Tools discovery is the minimum viable contract for most MCP clients and directories. Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
Playbook
  • Make `tools/list` deterministic across repeated calls.
  • Document or relax auth requirements for discovery routes.
  • Check that tool names, descriptions, and schemas remain stable across deploys.
Critical Respond to latest validation is failing Core MCP flows did not validate successfully on the latest run. Fix the failing checks first, then revalidate to confirm the recovery path.
Playbook
  • Fix the failing checks first.
  • Review the latest incident feed and validation diff for the first regression.
  • Revalidate once the remediation lands.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Keep connector refreshes backward compatible Managed connector clients freeze tool snapshots, so removed tools, new required args, and breaking output changes can break published integrations after refresh. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
High Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Raise Interface Quality score How well the tool/resource interface communicates and behaves under automation. Improve schemas, error contracts, and recovery messages so agents can reason about the surface automatically.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Repair prompts/list or stop advertising prompts Prompt metadata should either work live or be removed from the advertised capability set. Only advertise prompts if prompts/list works and prompt arguments are documented.
Playbook
  • Only advertise prompts that are actually accessible.
  • Add prompt descriptions and argument docs.
  • Run a live `prompts/list` check after any prompt changes.
Medium Repair resources/list or stop advertising resources Resource metadata should either work live or be removed from the advertised capability set. Only advertise resources if resources/list works and resources expose stable URIs/types.
Playbook
  • Only advertise resources with stable URIs and read semantics.
  • Add MIME/type hints where possible.
  • Run a live `resources/list` and `resources/read` check after updates.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Tool Surface Design 0/4 -4.0
Tool Snapshot Churn 0/4 -4.0
Tool Namespace Clarity 0/4 -4.0
Tool Capability Clarity 0/4 -4.0
Schema Completeness 0/4 -4.0
Result Shape Stability 0/4 -4.0
Input Sanitization Safety 0/4 -4.0
Trust Confidence 0.1/4 -3.9
Recovery Semantics 0.3/4 -3.7
Error Contract 0.4/4 -3.6
Freshness Confidence 0.5/4 -3.5
Dependency Supply Chain Signal 0.5/4 -3.5

Validation diff

Need at least two validation runs before diffing changes.

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

Status
Missing
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Error
Transport
streamable-http
Session header
yes
Protocol header
no
Bad protocol response
400
DELETE teardown
204
Expired session retry
400
Last-Event-ID visible
no

Issues: missing_protocol_header, expired_session_not_404

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Likely to fail
  • initializeOK
  • tools_listError
Read-only fetch flow Likely to fail
  • resource_readMissing
  • read_only_tool_surfaceMissing
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Passes
  • action_safety_probeOK

Registry & provenance divergence

Probe status
OK
Direct official match
no
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a

Active alerts

Aliases & registry graph

IdentifierSourceCanonicalScore
github-kolmo-construction/kolmo-mcp-server github_topic_registry yes 53.05

Alias consolidation

Canonical identifier
github-kolmo-construction/kolmo-mcp-server
Duplicate aliases
0
Registry sources
github_topic_registry
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Install snippets

Openai Connectors
Connector URL: https://www.kolmo.io/mcp
# No OAuth metadata detected.
# Server: github-kolmo-construction/kolmo-mcp-server
Claude Desktop
{
  "mcpServers": {
    "kolmo-mcp-server": {
      "command": "npx",
      "args": ["mcp-remote", "https://www.kolmo.io/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://www.kolmo.io/mcp"
Generic Http
curl -sS https://www.kolmo.io/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools
No live tool surface captured yet.
Observed from the latest live validation against https://www.kolmo.io/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
0 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for github-kolmo-construction/kolmo-mcp-server.
Direct machine links

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
1
Average Latency Ms
1862.01
Healthy Run Ratio Recent
0.0
Registry Presence Count
1
Active Alert Count
1
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development
Score Trend
53.05
Remediation Count
20
High Risk Tool Count
0
Destructive Tool Count
0
Exec Tool Count
0

Maintainer response quality

Score
33.33
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Failing
Validation profile
remote_mcp
Started
May 16, 2026 05:37:11 AM UTC
Latency
1862.0 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe OK n/a No high-risk write, destructive, or exec tools detected.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Error n/a Publishability blockers: tools list, transport compliance, server card, tool surface.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe Missing n/a tools list unavailable
initialize OK 179.3 ms Protocol 2025-03-26
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 186.6 ms Client error '404 Not Found' for url 'https://www.kolmo.io/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe Warning n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 22.3 ms Fetched https://www.kolmo.io/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 174.5 ms Client error '400 Bad Request' for url 'https://www.kolmo.io/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a not advertised
resources_list Missing 189.1 ms Client error '400 Bad Request' for url 'https://www.kolmo.io/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
server_card Error 255.2 ms Client error '404 Not Found' for url 'https://www.kolmo.io/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe OK 238.4 ms 35 tool(s) exposed
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no tools
tools_list Error 188.2 ms Client error '400 Bad Request' for url 'https://www.kolmo.io/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
transport_compliance_probe Error 160.4 ms Issues: missing protocol header, expired session not 404 (bad protocol=400, DELETE=204, expired session=400).
utility_coverage_probe Missing 89.3 ms No completions evidence; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {},
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 0,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 0
          },
          "secret_tools": 0,
          "tool_count": 0
        }
      },
      "latency_ms": null,
      "status": "ok"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": [
          "prompts",
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "tools_list",
          "transport_compliance",
          "server_card",
          "tool_surface"
        ],
        "criteria": {
          "action_safety": true,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": false,
          "tools_list": false,
          "transport_compliance": false
        },
        "high_risk_tools": 0,
        "tool_count": 0,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "error"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "reason": "tools_list_unavailable"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "mcp-session-id": "ab3651e5-c00e-4582-b3d3-e41609e32aeb",
          "ratelimit-limit": "300",
          "ratelimit-remaining": "299",
          "ratelimit-reset": "900",
          "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "prompts": {
                "listChanged": true
              },
              "tools": {
                "listChanged": true
              }
            },
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "description": "MCP server for Seattle-area home remodeling: 35 tools (cost estimation, weather scheduling, renovation ROI, contractor license verification, financing, project portfolio, neighborhood activity, reviews, permits, address-first parcel lookup, NL project parser, grounded permit Q&A, neighbor permit activity, source-freshness telemetry, material catalog, blog, author bios, procurement codes, service-area coverage, project testimonials, quotes) + 6 workflow prompts (estimate_project, check_permit_needs, plan_renovation, verify_contractor, compare_financing, explore_neighborhood).",
              "name": "kolmo-construction",
              "version": "1.3.0"
            }
          }
        },
        "url": "https://www.kolmo.io/mcp"
      },
      "latency_ms": 179.31,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://www.kolmo.io/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://www.kolmo.io/.well-known/oauth-protected-resource"
      },
      "latency_ms": 186.64,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "io.github.arcar-org/arcar-mcp",
          "io.github.linxule/vox-mcp",
          "ai.borealhost/mcp",
          "com.meetvalis/valis-credit-intelligence",
          "ai.primeta/primeta",
          "io.github.bookyo/nsfw-image-detector",
          "io.github.buildingapplications/mcp",
          "com.exploit-intel/eip-mcp",
          "io.github.Fabric-Protocol/fabric",
          "io.github.gogogadgetbytes/planka"
        ],
        "official_peer_count": 10,
        "registry_source": "github_topic_registry"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8",
          "ratelimit-limit": "300",
          "ratelimit-remaining": "299",
          "ratelimit-reset": "900",
          "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "http_status": 200,
        "url": "https://www.kolmo.io/robots.txt"
      },
      "latency_ms": 22.27,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://www.kolmo.io/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "ratelimit-limit": "300",
          "ratelimit-remaining": "299",
          "ratelimit-reset": "900",
          "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "http_status": 400,
        "payload": {},
        "reason": "not_advertised",
        "url": "https://www.kolmo.io/mcp"
      },
      "latency_ms": 174.53,
      "status": "missing"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2025-03-26",
        "lag_days": 244,
        "latest_known_version": "2025-11-25",
        "releases_behind": 2,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": false,
        "drift_fields": [],
        "metadata_document_count": 1,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://www.kolmo.io/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "ratelimit-limit": "300",
          "ratelimit-remaining": "299",
          "ratelimit-reset": "900",
          "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "http_status": 400,
        "payload": {},
        "reason": "not_advertised",
        "url": "https://www.kolmo.io/mcp"
      },
      "latency_ms": 189.07,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://www.kolmo.io/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://www.kolmo.io/.well-known/mcp/server-card.json"
      },
      "latency_ms": 255.24,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "mcp-session-id": "ab3651e5-c00e-4582-b3d3-e41609e32aeb",
          "ratelimit-limit": "300",
          "ratelimit-remaining": "299",
          "ratelimit-reset": "900",
          "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "http_status": 200,
        "payload": {
          "id": 301,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "Get Kolmo Construction company information: contact details, hours, service area, specializations, and tools.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "properties": {},
                  "type": "object"
                },
                "name": "get_business_info"
              },
              {
                "description": "List all residential remodeling services with slugs, descriptions, and page URLs. Use `search` to find by keyword.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "limit": {
                      "description": "Max results (default 50)",
                      "maximum": 100,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "offset": {
                      "description": "Pagination offset (default 0)",
                      "minimum": 0,
                      "type": "integer"
                    },
                    "search": {
                      "description": "Filter by keyword in service name or description",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "list_services"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "slug": {
                      "description": "The URL slug, e.g. \"kitchen-remodeling\"",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "get_service"
              },
              {
                "description": "List commercial construction services. Optionally filter by category: office, retail, industrial, hospitality, public. The \"public\" category covers public works and government contracts \u2014 Kolmo is WA State SEDBE-certified (#D700031098), King County SCS-certified (#7259), prevailing wage compliant, and MRSC Small Works Roster eligible (projects under $350K).",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "category": {
                      "description": "Filter: office, retail, industrial, hospitality, public",
                      "type": "string"
                    },
                    "limit": {
                      "description": "Max results (default 50)",
                      "maximum": 100,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "offset": {
                      "description": "Pagination offset (default 0)",
                      "minimum": 0,
                      "type": "integer"
                    }
                  },
                  "type": "object"
                },
                "name": "list_commercial_services"
              },
              {
                "description": "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.).",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "system": {
                      "description": "Code system to return (default: all)",
                      "enum": [
                        "all",
                        "naics",
                        "nigp",
                        "unspsc"
                      ],
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "list_procurement_codes"
              },
              {
                "description": "List completed remodeling projects with before/after photos and locations. Filter by category or keyword.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "category": {
                      "description": "Filter: kitchen, bathroom, full-home, outdoor, basement",
                      "type": "string"
                    },
                    "limit": {
                      "description": "Max results (default 20)",
                      "maximum": 100,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "offset": {
                      "description": "Pagination offset (default 0)",
                      "minimum": 0,
                      "type": "integer"
                    },
                    "search": {
                      "description": "Filter by keyword in project title, description, or location",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "list_projects"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "slug": {
                      "description": "The URL slug of the project",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "get_project"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "keyword": {
                      "description": "Keyword to fuzzy-match against testimonial project name or content (e.g. \"kitchen\", \"deck\")",
                      "type": "string"
                    },
                    "limit": {
                      "description": "Max results (default 10)",
                      "maximum": 50,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "minRating": {
                      "description": "Minimum star rating (1-5, default 1)",
                      "maximum": 5,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "projectSlug": {
                      "description": "Project slug to match (e.g. \"ballard-kitchen-remodel\"). Falls back to title match.",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "get_project_testimonials"
              },
              {
                "description": "List published blog posts about home remodeling, renovation costs, and construction tips. Filter by tag or author name.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "author": {
                      "description": "Filter posts by author name, e.g. \"Marcus Reid\"",
                      "type": "string"
                    },
                    "limit": {
                      "description": "Max posts to return (default 20)",
                      "maximum": 50,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "offset": {
                      "description": "Pagination offset (default 0)",
                      "minimum": 0,
                      "type": "integer"
                    },
                    "tag": {
                      "description": "Filter posts by tag, e.g. \"flooring\", \"deck\", \"painting\"",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "list_blog_posts"
              },
              {
                "description": "Get the full markdown content of a blog post by its slug.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "slug": {
                      "description": "The URL slug of the blog post",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "get_blog_post"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "properties": {},
                  "type": "object"
                },
                "name": "list_blog_tags_and_categories"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "dryRun": {
                      "description": "If true, validate and preview without submitting (default false)",
                      "type": "boolean"
                    },
                    "email": {
                      "description": "Email address",
                      "format": "email",
                      "type": "string"
                    },
                    "message": {
                      "description": "Project description or question",
                      "minLength": 10,
                      "type": "string"
                    },
                    "name": {
                      "description": "Full name",
                      "minLength": 1,
                      "type": "string"
                    },
                    "phone": {
                      "description": "Phone number (optional)",
                      "type": "string"
                    },
                    "service": {
                      "description": "Service needed, e.g. \"kitchen remodel\"",
                      "type": "string"
                    }
                  },
                  "required": [
                    "name",
                    "email",
                    "message"
                  ],
                  "type": "object"
                },
                "name": "submit_contact_request"
              },
              {
                "description": "List all 11 supported calculator project types with their required input fields and descriptions. Useful for discovery before calling get_estimate.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "properties": {},
                  "type": "object"
                },
                "name": "list_project_types"
              },
              {
                "description": "Get available material choices for a project type \u2014 flooring types, paint grades, decking materials, kitchen/bath scope tiers, ADA modifications, etc. Use the returned IDs in the project fields of get_estimate.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "projectType": {
                      "description": "The project type to list materials for",
                      "enum": [
                        "interior-painting",
                        "deck",
                        "exterior-painting",
                        "flooring",
                        "windows",
                        "siding",
                        "fence",
                        "landscaping",
                        "kitchen",
                        "bathroom",
                        "ada"
                      ],
                      "type": "string"
                    }
                  },
                  "required": [
                    "projectType"
                  ],
                  "type": "object"
                },
                "name": "get_material_options"
              },
              {
                "description": "Calculate a Seattle-area cost estimate. Returns total, material, labor costs, days, and itemized line items.\n\nMaterial 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.\n\nRequired fields by projectType:\n\ninterior-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)\n\nexterior-painting: wallArea(sqft) | trimArea(sqft) | doorCount | paintQuality (material ID) | surfacePrepLevel (\"minimal\"|\"moderate\"|\"extensive\") | includesPrimer (bool) | stories (1-3) | colorChange (bool)\n\nflooring: rooms (Array<{id,name,length(ft),width(ft)}>) | flooringMaterial (material ID, e.g. \"vinyl-plank-lvp\",\"solid-hardwood\",\"ceramic-tile\") | includesUnderlayment (bool) | underlaymentType? (material ID) | includesBaseboard (bool) | baseboardType? (material ID) | baseboardLinearFeet? | includesRemoval (bool) | removalType? (\"carpet\"|\"tile\"|\"hardwood\") | includesSubfloorPrep (bool) | transitionCount\n\ndeck: 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\")\n\nwindows: windows (Array<{id,windowType(e.g.\"double-hung\",\"casement\",\"slider\",\"bay\"),width(inches 12-120),height(inches 12-120),quantity}>) | qualityLevel (\"standard\"|\"premium\"|\"luxury\") | includesTrimWork (bool) | trimMaterial? (material ID) | includesRemoval (bool) | energyEfficient (bool)\n\nsiding: wallArea(sqft) | sidingMaterial (material ID) | includesInsulation (bool) | insulationType? (string) | homeHeight (\"single-story\"|\"two-story\"|\"three-story\") | includesRemoval (bool) | existingSidingType? (string) | trimLinearFeet (number) | soffit (bool) | soffitLinearFeet? (number)\n\nfence: linearFeet | fenceMaterial (material ID) | height (ft, 3-8) | gateCount (number 0-10) | gateWidth? (ft) | style? (e.g. \"privacy\",\"picket\") | includesRemoval (bool) | terrain (\"flat\"|\"sloped\"|\"mixed\") | concreteFootings (bool)\n\nlandscaping: yardArea(sqft, 100\u201350000) | includesIrrigation(bool) | irrigationType?(string) | irrigationZones?(1\u201320) | includesSod(bool) | sodSquareFeet?(defaults to yardArea) | includesMulch(bool) | mulchSquareFeet?(defaults to yardArea) | includesSitePrep(bool) | plants?(Array<{id,plantType,quantity,size(\"small\"|\"medium\"|\"large\")}>) | hardscapeFeatures?(Array<{id,featureType,squareFeet,material}>)\n\nkitchen: kitchenSize(sqft, 40-600) | scope(\"cosmetic\"|\"standard\"|\"full-gut\") | cabinets(\"keep\"|\"reface\"|\"prefab\"|\"semi-custom\"|\"custom\") | countertop(\"keep\"|\"laminate\"|\"butcher-block\"|\"quartz\"|\"granite\"|\"marble\") | appliances(\"keep\"|\"budget\"|\"mid-range\"|\"premium\") | flooring(\"keep\"|\"lvp\"|\"tile\"|\"hardwood\") | backsplash?(bool) | plumbingRelocation?(bool) | electricalUpgrade?(bool) | island?(bool) | lighting?(bool)\n\nbathroom: bathroomType(\"half-bath\"|\"full-bath\"|\"primary-bath\"|\"accessible\") | bathroomSize(sqft, 20-300) | scope(\"cosmetic\"|\"standard\"|\"full-gut\") | showerTub(\"keep\"|\"tub-to-shower\"|\"walk-in-shower\"|\"tub-replacement\"|\"freestanding-tub\") | vanity(\"keep\"|\"budget\"|\"mid-range\"|\"premium\") | tileWork(\"none\"|\"floor-only\"|\"floor-and-shower\"|\"full-tile\") | heatedFloors?(bool) | newLighting?(bool) | ventilation?(bool) | plumbingRelocation?(bool)\n\nada: projectScope(\"single-room\"|\"whole-home\"|\"bathroom-specific\") | modifications({grabBars?,walkInShower?,widerDoorways?,ramp?,nonSlipFlooring?,leverHandles?,raisedToilet?,rollUnderSink?,accessibleCounters?,stairLift?} all bool) | currentCondition(\"minor\"|\"moderate\"|\"major\") | homeStories?(1-3) | doorwayCount?(0-20) | rampLengthFeet?(0-60) | flooringSquareFeet?(0-5000)",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "project": {
                      "additionalProperties": {},
                      "description": "Project input fields \u2014 see tool description for required fields per projectType.",
                      "type": "object"
                    },
                    "projectType": {
                      "description": "The type of project",
                      "enum": [
                        "interior-painting",
                        "deck",
                        "exterior-painting",
                        "flooring",
                        "windows",
                        "siding",
                        "fence",
                        "landscaping",
                        "kitchen",
                        "bathroom",
                        "ada"
                      ],
                      "type": "string"
                    }
                  },
                  "required": [
                    "projectType",
                    "project"
                  ],
                  "type": "object"
                },
                "name": "get_estimate"
              },
              {
                "description": "List customer reviews and testimonials for Kolmo Construction. Combines verified Google reviews and on-site testimonials. Filter by minimum star rating.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "limit": {
                      "description": "Max results (default 20)",
                      "maximum": 100,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "minRating": {
                      "description": "Minimum star rating to include (1-5, default 1)",
                      "maximum": 5,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "offset": {
                      "description": "Pagination offset (default 0)",
                      "minimum": 0,
                      "type": "integer"
                    },
                    "source": {
                      "description": "Source to query: all (default), google, testimonials",
                      "enum": [
                        "all",
                        "google",
                        "testimonials"
                      ],
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "list_reviews"
              },
              {
                "description": "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 \u2014 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?\"",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "location": {
                      "description": "City or jurisdiction slug, e.g. \"Seattle\", \"Bellevue\", \"Tacoma\", \"king-county-unincorporated\"",
                      "type": "string"
                    },
                    "projectType": {
                      "description": "Project type \u2014 canonical: kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "check_permit_requirements"
              },
              {
                "description": "Enumerate permit rules with full detail \u2014 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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "jurisdiction": {
                      "description": "Jurisdiction slug or display name (e.g. \"seattle\", \"bellevue\", \"tacoma\")",
                      "type": "string"
                    },
                    "keyword": {
                      "description": "Keyword in project type, trigger, thresholds, or notes (e.g. \"deck\", \"adu\", \"egress\")",
                      "type": "string"
                    },
                    "limit": {
                      "description": "Max results (default 50)",
                      "maximum": 200,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "onlyAuthoritative": {
                      "description": "If true, exclude legacy LLM-seeded rows. Default true.",
                      "type": "boolean"
                    }
                  },
                  "type": "object"
                },
                "name": "get_permit_rule_details"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "contractorQuery": {
                      "description": "Contractor license number or business name",
                      "type": "string"
                    },
                    "jurisdictionSlug": {
                      "description": "Permit jurisdiction slug (e.g. \"seattle\", \"tacoma\")",
                      "type": "string"
                    },
                    "projectType": {
                      "description": "Canonical project type (kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition)",
                      "type": "string"
                    }
                  },
                  "required": [
                    "contractorQuery",
                    "jurisdictionSlug",
                    "projectType"
                  ],
                  "type": "object"
                },
                "name": "match_contractor_to_permit"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "jurisdictionSlug": {
                      "description": "Jurisdiction slug, e.g. \"seattle\", \"bellevue\", \"tacoma\" (use list_permit_jurisdictions to discover)",
                      "type": "string"
                    },
                    "projectType": {
                      "description": "Canonical project type",
                      "enum": [
                        "kitchen",
                        "bathroom",
                        "basement",
                        "deck",
                        "fence",
                        "siding",
                        "windows",
                        "flooring",
                        "adu",
                        "roofing",
                        "hvac",
                        "electrical",
                        "plumbing",
                        "addition"
                      ],
                      "type": "string"
                    },
                    "valuationUsd": {
                      "description": "Project valuation in USD (materials + labor)",
                      "minimum": 0,
                      "type": "number"
                    }
                  },
                  "required": [
                    "jurisdictionSlug",
                    "projectType",
                    "valuationUsd"
                  ],
                  "type": "object"
                },
                "name": "estimate_permit_fee"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "county": {
                      "description": "Filter by county",
                      "enum": [
                        "King",
                        "Pierce",
                        "Snohomish"
                      ],
                      "type": "string"
                    },
                    "verifiedOnly": {
                      "description": "If true, only return rows where portal_url is populated (verified from official source). Default false.",
                      "type": "boolean"
                    }
                  },
                  "type": "object"
                },
                "name": "list_permit_jurisdictions"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "address": {
                      "description": "Full street address (e.g., \"1234 NE 65th St, Seattle, WA 98115\"). Must be in King, Pierce, or Snohomish County, WA.",
                      "maxLength": 250,
                      "minLength": 3,
                      "type": "string"
                    },
                    "forceRefresh": {
                      "description": "Skip the 30-day cache and re-fetch from county GIS + overlay sources. Default false.",
                      "type": "boolean"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "lookup_parcel_by_address"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "cityName": {
                      "description": "City name (e.g., \"Seattle\", \"Bellevue\")",
                      "type": "string"
                    },
                    "description": {
                      "description": "Free-text project description (e.g., \"I want to add a 200 sqft deck off my master bedroom on the second floor\")",
                      "maxLength": 2000,
                      "minLength": 1,
                      "type": "string"
                    },
                    "jurisdictionSlug": {
                      "description": "Jurisdiction slug from lookup_parcel_by_address (helps disambiguate region-specific terminology)",
                      "type": "string"
                    },
                    "zoningCode": {
                      "description": "Zoning code from lookup_parcel_by_address (e.g., \"NR2\", \"LR1\")",
                      "type": "string"
                    }
                  },
                  "required": [
                    "description"
                  ],
                  "type": "object"
                },
                "name": "parse_project_description"
              },
              {
                "description": "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 \u2014 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?\"",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "address": {
                      "description": "Full street address in King, Pierce, or Snohomish County, WA",
                      "maxLength": 250,
                      "minLength": 3,
                      "type": "string"
                    },
                    "question": {
                      "description": "A single permit/zoning/setback/overlay question about this parcel",
                      "maxLength": 1000,
                      "minLength": 3,
                      "type": "string"
                    }
                  },
                  "required": [
                    "address",
                    "question"
                  ],
                  "type": "object"
                },
                "name": "answer_permit_question"
              },
              {
                "description": "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 \u2014 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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "address": {
                      "description": "Full street address in King, Pierce, or Snohomish County, WA",
                      "maxLength": 250,
                      "minLength": 3,
                      "type": "string"
                    }
                  },
                  "required": [
                    "address"
                  ],
                  "type": "object"
                },
                "name": "get_neighbor_permit_activity"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "jurisdictionSlug": {
                      "description": "Optional jurisdiction filter (e.g., \"seattle\", \"bellevue\"). When omitted, returns rollup across all jurisdictions.",
                      "type": "string"
                    },
                    "limit": {
                      "description": "Max snapshots to return (default 50, newest first)",
                      "maximum": 200,
                      "minimum": 1,
                      "type": "integer"
                    }
                  },
                  "type": "object"
                },
                "name": "get_permit_data_freshness"
              },
              {
                "description": "Browse the full material catalog with pricing \u2014 flooring types, paint grades, decking materials, siding, windows, fencing, and more. Use category to filter. Returns material IDs compatible with get_estimate.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "category": {
                      "description": "Filter by category: painting, flooring, decking, siding, windows, fencing, landscaping",
                      "type": "string"
                    },
                    "limit": {
                      "description": "Max results (default 50)",
                      "maximum": 200,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "offset": {
                      "description": "Pagination offset (default 0)",
                      "minimum": 0,
                      "type": "integer"
                    },
                    "search": {
                      "description": "Filter by keyword in material name or description",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "get_material_catalog"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "days": {
                      "description": "Number of days to forecast (1-14, default 7)",
                      "maximum": 14,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "projectType": {
                      "description": "Type of project to check weather suitability for",
                      "enum": [
                        "exterior-painting",
                        "deck",
                        "roofing",
                        "landscaping",
                        "siding",
                        "fence",
                        "windows",
                        "interior"
                      ],
                      "type": "string"
                    }
                  },
                  "required": [
                    "projectType"
                  ],
                  "type": "object"
                },
                "name": "get_weather_window"
              },
              {
                "description": "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 \u2014 e.g. \"Has Kolmo worked in Ballard?\" or \"What has Kolmo done in Capitol Hill?\"",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "neighborhood": {
                      "description": "Seattle neighborhood or city, e.g. \"Ballard\", \"Capitol Hill\", \"Bellevue\", \"Queen Anne\"",
                      "type": "string"
                    }
                  },
                  "required": [
                    "neighborhood"
                  ],
                  "type": "object"
                },
                "name": "get_neighborhood_project_activity"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "location": {
                      "description": "City, neighborhood, or ZIP to check, e.g. \"Ballard\", \"Bellevue\", \"98105\", \"Tacoma\"",
                      "type": "string"
                    }
                  },
                  "required": [
                    "location"
                  ],
                  "type": "object"
                },
                "name": "check_service_area_coverage"
              },
              {
                "description": "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 \u2014 e.g. \"What ROI does a kitchen remodel get in Seattle?\" or \"Which remodel pays off the most?\"",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "estimatedCost": {
                      "description": "Your estimated project budget in USD. If provided, returns expected resale value added.",
                      "type": "number"
                    },
                    "projectType": {
                      "description": "Type of project, e.g. \"kitchen\", \"bathroom\", \"deck\", \"windows\", \"siding\", \"ADU\", \"basement\". Omit to see all projects ranked by ROI.",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "get_project_roi"
              },
              {
                "description": "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 \u2014 checks if they are licensed, bonded, and insured in WA.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "query": {
                      "description": "Contractor license number (e.g. \"KOLMOL*753JS\") or business name (e.g. \"Kolmo Construction\")",
                      "type": "string"
                    }
                  },
                  "required": [
                    "query"
                  ],
                  "type": "object"
                },
                "name": "check_contractor_license_status"
              },
              {
                "description": "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.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "author": {
                      "description": "Author name or slug, e.g. \"Marcus Reid\", \"marcus-reid\", \"Emily Chen\", \"emily-chen\"",
                      "type": "string"
                    }
                  },
                  "required": [
                    "author"
                  ],
                  "type": "object"
                },
                "name": "get_author_bio"
              },
              {
                "description": "Search across all Kolmo content \u2014 services, projects, and blog posts \u2014 with a single keyword query. Returns ranked results grouped by type. Use this instead of calling list_services + list_projects + list_blog_posts separately.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "limit": {
                      "description": "Max results per type (default 5)",
                      "maximum": 20,
                      "minimum": 1,
                      "type": "integer"
                    },
                    "query": {
                      "description": "Search keyword or phrase, e.g. \"deck Seattle\", \"kitchen cost\", \"permit\"",
                      "minLength": 1,
                      "type": "string"
                    },
                    "types": {
                      "description": "Content types to include (default: all three)",
                      "items": {
                        "enum": [
                          "services",
                          "projects",
                          "blog"
                        ],
                        "type": "string"
                      },
                      "type": "array"
                    }
                  },
                  "required": [
                    "query"
                  ],
                  "type": "object"
                },
                "name": "search_content"
              },
              {
                "description": "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 \u2014 HELOC, home improvement loans, cash-out refinance, and contractor payment plans.",
                "execution": {
                  "taskSupport": "forbidden"
                },
                "inputSchema": {
                  "$schema": "http://json-schema.org/draft-07/schema#",
                  "additionalProperties": false,
                  "properties": {
                    "creditProfile": {
                      "description": "Approximate credit profile: excellent (750+), good (680-749), fair (620-679). Default: good",
                      "enum": [
                        "excellent",
                        "good",
                        "fair"
                      ],
                      "type": "string"
                    },
                    "projectBudget": {
                      "description": "Estimated project cost in USD",
                      "minimum": 1000,
                      "type": "number"
                    }
                  },
                  "required": [
                    "projectBudget"
                  ],
                  "type": "object"
                },
                "name": "get_financing_options"
              }
            ]
          }
        },
        "requested_protocol_version": "2025-03-26",
        "resumed": true,
        "session_id_present": true,
        "transport": "streamable-http",
        "url": "https://www.kolmo.io/mcp"
      },
      "latency_ms": 238.36,
      "status": "ok"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://www.kolmo.io/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "ratelimit-limit": "300",
          "ratelimit-remaining": "299",
          "ratelimit-reset": "900",
          "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "http_status": 400,
        "payload": {},
        "url": "https://www.kolmo.io/mcp"
      },
      "latency_ms": 188.19,
      "status": "error"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json",
          "ratelimit-limit": "300",
          "ratelimit-remaining": "299",
          "ratelimit-reset": "900",
          "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "bad_protocol_payload": {
          "error": {
            "code": -32000,
            "message": "Bad Request: Unsupported protocol version: 1999-99-99 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"
          },
          "id": null,
          "jsonrpc": "2.0"
        },
        "bad_protocol_status_code": 400,
        "delete_error": null,
        "delete_status_code": 204,
        "expired_session_error": null,
        "expired_session_status_code": 400,
        "issues": [
          "missing_protocol_header",
          "expired_session_not_404"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": true,
        "transport": "streamable-http"
      },
      "latency_ms": 160.38,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [
          "prompts",
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 400,
          "probe_status": "missing"
        }
      },
      "latency_ms": 89.26,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://www.kolmo.io/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://www.kolmo.io/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://www.kolmo.io/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://www.kolmo.io/.well-known/mcp/server-card.json"
    },
    "tools_list": {
      "error": "Client error '400 Bad Request' for url 'https://www.kolmo.io/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
      "headers": {
        "content-type": "application/json",
        "ratelimit-limit": "300",
        "ratelimit-remaining": "299",
        "ratelimit-reset": "900",
        "strict-transport-security": "max-age=31536000; includeSubDomains"
      },
      "http_status": 400,
      "payload": {},
      "url": "https://www.kolmo.io/mcp"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "application/json",
        "ratelimit-limit": "300",
        "ratelimit-remaining": "299",
        "ratelimit-reset": "900",
        "strict-transport-security": "max-age=31536000; includeSubDomains"
      },
      "bad_protocol_payload": {
        "error": {
          "code": -32000,
          "message": "Bad Request: Unsupported protocol version: 1999-99-99 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"
        },
        "id": null,
        "jsonrpc": "2.0"
      },
      "bad_protocol_status_code": 400,
      "delete_error": null,
      "delete_status_code": 204,
      "expired_session_error": null,
      "expired_session_status_code": 400,
      "issues": [
        "missing_protocol_header",
        "expired_session_not_404"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2025-03-26",
      "session_id_present": true,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://www.kolmo.io/mcp",
  "server_card_payload": null,
  "server_identifier": "github-kolmo-construction/kolmo-mcp-server"
}

Known versions

Validation history

7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
0%
Freshness
1.3h
TimestampStatusScoreLatencyTools
May 16, 2026 05:37:12 AM UTC Failing 53.0 1862.0 ms 0

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
May 16, 2026 05:37:12 AM UTC Failing 53.0 2025-03-26 public 0 0 none

Recent validation runs

StartedStatusSummaryLatencyChecks
May 16, 2026 05:37:11 AM UTC Completed Failing 1862.0 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe