io.github.andrew-ji-cupix/cupix-compass
REMOTE · 7QC1F4FT9D.EXECUTE-API.US-WEST-2.AMAZONAWS.COM · SCANNED OCT 4
Explore and analyze Cupix construction site data: 360 images, progress, and insights.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.github.andrew-ji-cupix/cupix-compass MCP server?
io.github.andrew-ji-cupix/cupix-compass is a hosted endpoint at https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · 7qc1f4ft9d.execute-api.us-west-2.amazonaws.com
claude mcp add --transport http andrew-ji-cupix-cupix-compass 'https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp'
{
"mcpServers": {
"andrew-ji-cupix-cupix-compass": {
"url": "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp"
}
}
} {
"servers": {
"andrew-ji-cupix-cupix-compass": {
"type": "http",
"url": "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp"
}
}
} [mcp_servers.andrew-ji-cupix-cupix-compass] url = "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp"
{
"$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 mcp add andrew-ji-cupix-cupix-compass --url 'https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp' --transport streamable-http
mcp_servers:
andrew-ji-cupix-cupix-compass:
url: "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp" {
"McpServers": {
"andrew-ji-cupix-cupix-compass": {
"Transport": "http",
"Url": "https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp"
}
}
} assistant mcp add andrew-ji-cupix-cupix-compass -t streamable-http -u 'https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Sept 26 −43
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 6 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask-about-project-data” rewrote its description, which is the text the model reads security
- Schema quality: 1905 → 2195 ▼ functional
- Schema quality: fair → good functional
- New tool “compare-site-findings” functional
- “ask-about-project-data” added an optional parameter “cursor” cosmetic
- “ask-about-project-data” added an optional parameter “limit” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.execute-api.us-west-2.amazonaws.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 18 Sept 2026 | 3 Apr 2027 | RSA 2048 | SHA256-RSA | 20e56d07aecedb137ca004688d552a0 |
| SANs: *.execute-api.us-west-2.amazonaws.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 7qc1f4ft9d.execute-api.us-west-2.amazonaws.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| amazonaws.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.cupix.works/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.cupix.works/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://mcp.cupix.works/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.cupix.works/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | metadata_resource_mismatch |
| Resource | https://mcp.cupix.works |
| Authorisation server | https://accounts.cupix.works/us |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp | Auth required | 401 | |
| http (plaintext) | http://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze-progress-and-forecasts Analyze construction progress and forecasts from SiteInsights and/or Work in Place (WIP) intelligence. ~288
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
| Name | Type | Req | Description |
|---|---|---|---|
| facility_key | – | – | – |
| team_domain | – | – | – |
| user_intent | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
ask-about-project-data Ask about anything in your projects: properties, BIM and drawing files, annotations, and capture details. ~520
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. limit: Number of rows per page. Values above 200 are capped at 200. cursor: Cursor for the next page of the same search. Returns: List…
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| facility_key | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| scope | – | – | – |
| team_domain | – | – | – |
| user_intent | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
check-current-project See which project the conversation is currently focused on. ~31
Return the currently saved team_domain and facility_key for this user.
| Name | Type | Req | Description |
|---|---|---|---|
| user_intent | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
compare-site-findings Compare Compass AI findings between two capture dates. ~175
Use for QA/QC questions about findings added, resolved, unchanged, moved, or otherwise changed between two dates. Use the prior dates again on a follow-up call and add level or confidence filters. The runtime uses pano camera coverage, so uncertain identity or possible movement is returned as INDETERMINATE instead of guessed ADDED/RESOLVED.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_date | string | yes | – |
| comparison_date | string | yes | – |
| facility_key | – | – | – |
| level_ids | array | – | – |
| limit | integer | – | – |
| min_confidence | number | – | – |
| minimum_level_number | – | – | – |
| polygon | – | – | – |
| query | string | yes | – |
| statuses | array | – | – |
| team_domain | – | – | – |
| timezone | string | – | – |
| user_intent | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | – | yes | – |
| classification_policy | string | yes | – |
| comparison | – | yes | – |
| findings | array | yes | – |
| normalized_request | – | yes | – |
| project | – | yes | – |
| query_id | string | yes | – |
| returned | integer | yes | – |
| schema_version | string | yes | – |
| summary | – | yes | – |
| total | integer | yes | – |
| warnings | array | yes | – |
No examples provided.
list-my-projects Browse all the CupixWorks projects you have access to. ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| team_domain | – | – | – |
| user_intent | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search-site-photos Find what matters in geo-tagged 360° site photos by content, like site context, safety risks, quality issues, and key objects. ~485
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. cursor: Cursor for the next page of the same search. Returns: ToolResult: Image viewer links, 3D coordinates, and capture dates
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| end_date | string | – | – |
| facility_key | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| scope | – | – | – |
| start_date | string | – | – |
| team_domain | – | – | – |
| user_intent | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
set-focus-project Choose the project to focus on so answers stay accurate and on topic. ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clear | boolean | – | – |
| facility_key | – | – | – |
| team_domain | – | – | – |
| user_intent | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.andrew-ji-cupix/cupix-compass MCP server?
io.github.andrew-ji-cupix/cupix-compass is an MCP server listed in the public MCP registry as io.github.andrew-ji-cupix/cupix-compass. Explore and analyze Cupix construction site data: 360 images, progress, and insights. This page covers its hosted endpoint (https://7qc1f4ft9d.execute-api.us-west-2.amazonaws.com/mcp).
Is the io.github.andrew-ji-cupix/cupix-compass MCP server safe to use?
io.github.andrew-ji-cupix/cupix-compass scores 33 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.andrew-ji-cupix/cupix-compass MCP server expose?
io.github.andrew-ji-cupix/cupix-compass exposes 7 tools: list-my-projects, ask-about-project-data, set-focus-project, check-current-project, search-site-photos, and 2 more. Their descriptions and schemas cost roughly 1,877 tokens of context every time the server is loaded.
Does the io.github.andrew-ji-cupix/cupix-compass MCP server require authentication?
Yes. io.github.andrew-ji-cupix/cupix-compass asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.andrew-ji-cupix/cupix-compass MCP server still maintained?
io.github.andrew-ji-cupix/cupix-compass is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.