# Argos Bot CTS Bridge Lookup (remote · arcus-api.argosbot.io)

Inspect ownerless Arc/Base CTS bridges and token mappings; 0.007 USDC via x402 per lookup.

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

## Components

- remote · `arcus-api.argosbot.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/arcbot11-argos-cts-bridge-lookup/arcus-api.md), [page](https://verifymcp.io/servers/arcbot11-argos-cts-bridge-lookup/arcus-api)

## Channel facts

- Endpoint: `https://arcus-api.argosbot.io/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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/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).
  - Tool/resource definitions use about 218 tokens (~109/item across 2 items; 1 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Argos Bot CTS Bridge Lookup MCP server?

Argos Bot CTS Bridge Lookup is a hosted endpoint at https://arcus-api.argosbot.io/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.

### Claude

```bash
claude mcp add --transport http arcbot11-argos-cts-bridge-lookup 'https://arcus-api.argosbot.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "arcbot11-argos-cts-bridge-lookup": {
      "url": "https://arcus-api.argosbot.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "arcbot11-argos-cts-bridge-lookup": {
      "type": "http",
      "url": "https://arcus-api.argosbot.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.arcbot11-argos-cts-bridge-lookup]
url = "https://arcus-api.argosbot.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "arcbot11-argos-cts-bridge-lookup": {
      "type": "remote",
      "url": "https://arcus-api.argosbot.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add arcbot11-argos-cts-bridge-lookup --url 'https://arcus-api.argosbot.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  arcbot11-argos-cts-bridge-lookup:
    url: "https://arcus-api.argosbot.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "arcbot11-argos-cts-bridge-lookup": {
      "Transport": "http",
      "Url": "https://arcus-api.argosbot.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add arcbot11-argos-cts-bridge-lookup -t streamable-http -u 'https://arcus-api.argosbot.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "arcbot11-argos-cts-bridge-lookup": {
      "type": "http",
      "url": "https://arcus-api.argosbot.io/mcp"
    }
  }
}
```

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

## Changelog

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

### 2026-11-05 (score 75, +1)

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

### 2026-11-03 (score 74, +1)

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

### 2026-11-01 (score 73, +1)

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

### 2026-10-30 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 71)

First indexed and scored.

## MCP tools (1)

### `lookup_ownerless_bridge` (~150 tokens)

Arc / Base ownerless CTS bridge lookup

Costs 0.007 USDC on Arc per lookup. Inspect an original or wrapped token on Arc or Base using Circle CTS, CrossChainTokenService and CCTP. Returns token roles, counterpart addresses, wrapped supply, contract checks and block evidence. No bridge execution. A missing bridge is a valid paid result. Requires an x402-capable client; never request private keys.

Input parameters:

- `chain` (string): Chain containing the input address; omit to inspect both Arc and Base.
- `finality` (string): Block finality used for the lookup.
- `token` (string, required): Original or wrapped ERC-20 contract address to check. Replace the example with any Arc or Base token address.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/arcbot11-argos-cts-bridge-lookup/arcus-api#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71

## Common questions

### What is the Argos Bot CTS Bridge Lookup MCP server?

Argos Bot CTS Bridge Lookup is an MCP server listed in the public MCP registry as io.github.arcbot11/argos-cts-bridge-lookup. Inspect ownerless Arc/Base CTS bridges and token mappings; 0.007 USDC via x402 per lookup. This page covers its hosted endpoint (https://arcus-api.argosbot.io/mcp).

### Is the Argos Bot CTS Bridge Lookup MCP server safe to use?

Argos Bot CTS Bridge Lookup scores 75 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 Argos Bot CTS Bridge Lookup MCP server expose?

Argos Bot CTS Bridge Lookup exposes 1 tool: lookup_ownerless_bridge. Their descriptions and schemas cost roughly 150 tokens of context every time the server is loaded.

### Does the Argos Bot CTS Bridge Lookup MCP server require authentication?

No. We connected to Argos Bot CTS Bridge Lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Argos Bot CTS Bridge Lookup MCP server still maintained?

Argos Bot CTS Bridge Lookup is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Argos Bot CTS Bridge Lookup MCP server?

VerifyMCP ran 13 checks on Argos Bot CTS Bridge Lookup, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://arcus-api.argosbot.io/mcp
- Website: https://www.argosbot.io/x402
- Changelog RSS feed: https://verifymcp.io/servers/arcbot11-argos-cts-bridge-lookup/arcus-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/arcbot11-argos-cts-bridge-lookup/arcus-api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/arcbot11-argos-cts-bridge-lookup/arcus-api.json
- HTML version of this page: https://verifymcp.io/servers/arcbot11-argos-cts-bridge-lookup/arcus-api