# io.github.andrew-ji-cupix/cupix-compass (remote · 7qc1f4ft9d.execute-api.us-west-2.amazonaws.com)

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

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

## Components

- remote · `7qc1f4ft9d.execute-api.us-west-2.amazonaws.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/andrew-ji-cupix-cupix-compass/7qc1f4ft9d.md), [page](https://verifymcp.io/servers/andrew-ji-cupix-cupix-compass/7qc1f4ft9d)

## Channel facts

- Endpoint: `https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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

Scored 2026-08-03.

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

## Install

### Claude

```bash
claude mcp add --transport http andrew-ji-cupix-cupix-compass https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp
```

### Codex

```toml
[mcp_servers.andrew-ji-cupix-cupix-compass]
url = "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "andrew-ji-cupix-cupix-compass": {
      "type": "remote",
      "url": "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add andrew-ji-cupix-cupix-compass --url https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  andrew-ji-cupix-cupix-compass:
    url: "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "andrew-ji-cupix-cupix-compass": {
      "type": "http",
      "url": "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp"
    }
  }
}
```

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

## Changelog

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

### 2026-08-03 (score 62, +1)

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

### 2026-08-01 (score 61, +1)

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

### 2026-07-31 (score 60, +4)

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

### 2026-07-30 (score 56, +1)

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

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

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

### 2026-07-27 (score 54, +1)

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

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

First indexed and scored.

## MCP tools (6)

### `list-my-projects` (~230 tokens)

Browse all the CupixWorks projects you have access to.

List construction projects the user can access within a team.

\**Use this tool ONLY when the user wants to switch project or has no
saved current project.** If `check-current-project` returns a
saved facility_key, do NOT call this tool — call the analysis tool
directly with no arguments.

Required workflow when this tool IS appropriate:
1\. Present the returned projects to the user.
2\. Wait for the user to select one.
3\. Call `set-focus-project` with team_domain and facility_key to persist
   the selection so future sessions skip this step.
4\. Then invoke analysis tools.

Args:
    team_domain: Team domain. Optional; if omitted, falls back to the
        saved current project, otherwise returns the team list so the
        caller can pick a team first.
    user_intent: REQUIRED. Pass the user's original question or request verbatim. Used for analytics only, does not affect results.

Returns:
    str: Accessible facilities with their keys and names.

Input parameters:

- `team_domain`
- `user_intent` (string)

Output parameters:

- `result` (string)

### `ask-about-project-data` (~476 tokens)

Ask about anything in your projects: properties, BIM and drawing files, annotations, and capture details.

Query the construction project database using natural language (Text-to-SQL).
Converts natural language into SQL to retrieve captures, annotations, progress metrics,
schedules, and other project records.
Pass the user's question as-is without modification.
For trade visibility, use `analyze-progress-and-forecasts` instead.
\**WORKFLOW:**
\- **Default**: call this tool with only `query`. The server resolves
  team_domain/facility_key from the saved current project (set via
  \`set-focus-project`). Do NOT call `list-my-projects`
  again just to obtain these values.
\- Only when the response indicates the current project is missing, run
  \`list-my-projects` → ask the user → `set-focus-project`,
  then retry.
\- Pass explicit team_domain/facility_key **only** when the user
  clearly wants to query a different project than the saved one.
\**Available tables:**
\- progresses: SI progress metrics (level, category, phase, workarea, cost, dates)
\- captures: Camera captures metadata (level, camera_model, capture_state, user_email)
\- records: Capture events with timestamps (captured_at, state, id)
\- photo_notes: Photonotes (description, state, user_email, created_at)
\- voice_notes: Voicenotes (level, description, state, user_email, created_at)
\- facilities: Site info (name, address, size, location, bim_count, created_at)
\- users: User profiles (name, email)
\- workareas: Spatial zones (level, name, user_name)

Args:
    query: Natural language question (pass as-is, no SQL syntax)
    team_domain: Omit by default. Pass only to override the current project.
    facility_key: Omit by default. Pass only to override the current project.
    user_intent: REQUIRED. Pass the user's original question or request verbatim. Used for analytics only, does not affect results.
    scope: Previous ask-about-project-data result identity to search within.

Returns:
    List of TextContent with query results and metadata

Input parameters:

- `facility_key`
- `query` (string, required)
- `scope`
- `team_domain`
- `user_intent` (string)

Output parameters:

- `result` (array)

### `set-focus-project` (~148 tokens)

Choose the project to focus on so answers stay accurate and on topic.

Save the user's current team and project so subsequent tool calls can omit
the `team_domain` / `facility_key` arguments.

Args:
    team_domain: Team domain to remember (required unless `clear=True`).
    facility_key: Facility key to remember (required unless `clear=True`).
    clear: If true, delete the stored selection and ignore the other args.
    user_intent: REQUIRED. Pass the user's original question or request verbatim. Used for analytics only, does not affect results.

Returns:
    Human-readable confirmation message.

Input parameters:

- `clear` (boolean)
- `facility_key`
- `team_domain`
- `user_intent` (string)

Output parameters:

- `result` (string)

### `check-current-project` (~31 tokens)

See which project the conversation is currently focused on.

Return the currently saved team_domain and facility_key for this user.

Input parameters:

- `user_intent` (string)

Output parameters:

- `result` (string)

### `search-site-photos` (~467 tokens)

Find what matters in geo-tagged 360° site photos by content, like site context, safety risks, quality issues, and key objects.

Search 360° captures (panoramic site photos) by visual content analysis.
Searches what is VISUALLY SEEN in 360° captures — safety hazards, quality issues, work types,
objects, equipment, materials, and physical site conditions.
Do NOT use for capture counts or statistics — use `ask-about-project-data` instead.
\**WORKFLOW:**
\- **Default**: call this tool with only `query` (and optionally
  date filters / limit). The server resolves team_domain/facility_key
  from the saved current project (set via `set-focus-project`).
  Do NOT call `list-my-projects` again just to obtain these
  values.
\- Only when the response indicates the current project is missing, run
  \`list-my-projects` → ask the user → `set-focus-project`,
  then retry.
\- Pass explicit team_domain/facility_key **only** when the user
  clearly wants to search a different project than the saved one.

\**Date filtering:** Only use start_date/end_date when the user explicitly mentions dates.
Format: YYYY-MM-DD. Omit entirely for general queries without date context.

Args:
    query: Keywords or phrases describing what to find in 360° captures
    team_domain: Omit by default. Pass only to override the current project.
    facility_key: Omit by default. Pass only to override the current project.
    user_intent: REQUIRED. Pass the user's original question or request verbatim. Used for analytics only, does not affect results.
    limit: Maximum number of results (default: 10)
    start_date: Start date filter, YYYY-MM-DD (omit if no date context)
    end_date: End date filter, YYYY-MM-DD (omit if no date context)
    scope: Previous search-site-photos result identity to search within.

Returns:
    ToolResult: Image viewer links, 3D coordinates, and capture dates

Input parameters:

- `end_date` (string)
- `facility_key`
- `limit` (integer)
- `query` (string, required)
- `scope`
- `start_date` (string)
- `team_domain`
- `user_intent` (string)

Output parameters:

- `result` (array)

### `analyze-progress-and-forecasts` (~288 tokens)

Analyze construction progress and forecasts from SiteInsights and/or Work in Place (WIP) intelligence.

Analyze Work In Place (WIP) progress from SiteInsights(SI) — completion
rates, delays, and forecasts.
Generates a progress report: overall completion, progress by category/vendor/level,
delay analysis, and estimated completion dates.
\**WORKFLOW:**
\- **Default**: call this tool with NO arguments. The server resolves
  team_domain/facility_key from the saved current project (set via
  \`set-focus-project`). Do NOT call `list-my-projects`
  again just to obtain these values — the saved selection is the
  source of truth.
\- Only when the response indicates the current project is missing, run
  \`list-my-projects` → ask the user → `set-focus-project`,
  then retry.
\- Pass explicit arguments **only** when the user clearly wants to
  analyze a different project than the saved one.

Args:
    team_domain: Omit by default. Pass only to override the current project.
    facility_key: Omit by default. Pass only to override the current project.
    user_intent: REQUIRED. Pass the user's original question or request verbatim. Used for analytics only, does not affect results.

Returns:
    Progress analysis report with completion rates and forecasts

Input parameters:

- `facility_key`
- `team_domain`
- `user_intent` (string)

Output parameters:

- `result` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/andrew-ji-cupix-cupix-compass/7qc1f4ft9d#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 61
- 2026-07-31: 60
- 2026-07-30: 56
- 2026-07-29: 55
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 53

## Links

- Remote endpoint: https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/andrew-ji-cupix-cupix-compass/7qc1f4ft9d/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/andrew-ji-cupix-cupix-compass/7qc1f4ft9d/changelog.json
- HTML version of this page: https://verifymcp.io/servers/andrew-ji-cupix-cupix-compass/7qc1f4ft9d