Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Harbor Crew Cross-Chain Report

REMOTE · RESGUARDO-WALLETS-260926.TIWEEDMASTER.CHATGPT.SITE · SCANNED SEP 29

EVM reports for 1–5 addresses. Pay 0.02 USDC, USDT, or Binance-Peg BSC-USD direct.

65 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 285 tokens (~142/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Harbor Crew Cross-Chain Report MCP server?

Harbor Crew Cross-Chain Report is a hosted endpoint at https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/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 · resguardo-wallets-260926.tiweedmaster.chatgpt.site

# add to Claude Code
claude mcp add --transport http rocket-harbor-420-harbor-cross-chain-report 'https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "rocket-harbor-420-harbor-cross-chain-report": {
      "url": "https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rocket-harbor-420-harbor-cross-chain-report": {
      "type": "http",
      "url": "https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.rocket-harbor-420-harbor-cross-chain-report]
url = "https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rocket-harbor-420-harbor-cross-chain-report": {
      "type": "remote",
      "url": "https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rocket-harbor-420-harbor-cross-chain-report --url 'https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  rocket-harbor-420-harbor-cross-chain-report:
    url: "https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rocket-harbor-420-harbor-cross-chain-report": {
      "Transport": "http",
      "Url": "https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add rocket-harbor-420-harbor-cross-chain-report -t streamable-http -u 'https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "rocket-harbor-420-harbor-cross-chain-report": {
      "type": "http",
      "url": "https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp"
    }
  }
}

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

Changelog

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.

  • 29 Sept 26 +10
    • Judged manipulation: unverified → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “submit_paid_cross_chain_report” rewrote its description, which is the text the model reads security
    • Schema quality: 113 → 142 ▼ functional
    • Schema quality: 113 → 133 ▼ functional
    • Schema quality: unverified → good ▲ functional
    • Schema quality: unverified → excellent ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • “submit_paid_cross_chain_report” added an optional parameter “paymentRailId” cosmetic
    • “submit_paid_cross_chain_report” reworded the description of “signature” cosmetic
    • “submit_paid_cross_chain_report” reworded the description of “txHash” cosmetic
  • 28 Sept 26 55

    First indexed and scored.

Diagnostics

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 29 Sept 2026 · Probed https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.tiweedmaster.chatgpt.site CN=WE1,O=Google Trust Services,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA256 e0cc66e7cbba24c20ec12d5012de29fa
SANs: *.tiweedmaster.chatgpt.site
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of resguardo-wallets-260926.tiweedmaster.chatgpt.site. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
site. present 31826 13 Verified
chatgpt.site. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp Verified 200
http (plaintext) http://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp HTTPS enforced 302 https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp
MCP tools · 2 exposed · ~249 tokens

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 →

Tool Tokens
get_cross_chain_report_quote ~39

Read the current price, supported networks, batch size, and payment destination for one cross-chain report. This tool never initiates a payment.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_paid_cross_chain_report ~210

Redeem a report after the user has manually paid exactly 0.02 of a listed payment asset (USDC, USDT, or Binance-Peg BSC-USD) on its EVM network and manually signed the report authorization. This tool only submits the supplied receipt and signature for verification; it never pays, moves funds, approves a contract, or signs for the user. The payment is direct to the operator.

NameTypeReqDescription
addressesarrayyesOne to five public EVM addresses to inspect.
payerAddressstringyesThe public wallet address that made the payment and signed the authorization.
paymentRailIdstring–Accepted payment network and asset. Defaults to base-usdc for backward compatibility.
signaturestringyesA 65-byte personal_sign signature binding the payment rail, network, transaction hash, and exact address batch. It does not authorize a transfer.
txHashstringyesThe transaction hash for the user's completed payment on the selected network.

No output schema declared.

No examples provided.

Common questions

What is the Harbor Crew Cross-Chain Report MCP server?

Harbor Crew Cross-Chain Report is an MCP server listed in the public MCP registry as io.github.Rocket-Harbor-420/harbor-cross-chain-report. EVM reports for 1–5 addresses. Pay 0.02 USDC, USDT, or Binance-Peg BSC-USD direct. This page covers its hosted endpoint (https://resguardo-wallets-260926.tiweedmaster.chatgpt.site/api/v1/mcp).

Is the Harbor Crew Cross-Chain Report MCP server safe to use?

Harbor Crew Cross-Chain Report scores 65 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 Harbor Crew Cross-Chain Report MCP server expose?

Harbor Crew Cross-Chain Report exposes 2 tools: get_cross_chain_report_quote, submit_paid_cross_chain_report. Their descriptions and schemas cost roughly 249 tokens of context every time the server is loaded.

Does the Harbor Crew Cross-Chain Report MCP server require authentication?

No. We connected to Harbor Crew Cross-Chain Report without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Harbor Crew Cross-Chain Report MCP server still maintained?

Harbor Crew Cross-Chain Report is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.