Skip to content
External endpointresponds

cupix-compass

Explore and analyze Cupix construction site data: 360 images, progress, and insights.

Endpoint URL
https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:58 AM UTC
Check
MCP initialize · 8s limit
Latency
170 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.andrew-ji-cupix/cupix-compass

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
cupix-compass
Version
1.29.0
Capability keys
experimental, prompts, resources, tools
Tool names
list-my-projects, ask-about-project-data, set-focus-project, check-current-project, search-site-photos, analyze-progress-and-forecasts, compare-site-findings
Instructions excerpt

Cupix Compass MCP — construction site analysis tools. CURRENT PROJECT (IMPORTANT): The server persists each user's selected team_domain and facility_key across sessions. Do NOT re-collect this selection every session. At the start of a new conversation, before calling `list-my-projects` for selection: 1. Call `check-current-project` once. If it returns saved values, use those. 2. Call analysis tools (`analyze-progress-and-forecasts`, `ask-about-project-data`, `search-site-photos`, `compare-site-findings`) with NO team_domain / facility_key arguments — the server resolves them from the saved current project. 3. Only when `check-current-project` returns "No current project", run `list-my-projects` → ask the user → `set-focus-project`. Pass explicit team_domain / facility_key only when the user clearly wants to analyze a different project than the saved one. Use `compare-site-findings` for added/resolved/unchanged findings or other QA/Q

Reported Aug 17, 2026, 04:58 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 404ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 166ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 418ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 170ms