# Straelo Relay (remote · relay.straelo.com)

MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence.

- Trust score: 74/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `relay.straelo.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-straelo-relay/relay.md), [page](https://verifymcp.io/servers/com-straelo-relay/relay)

## Channel facts

- Endpoint: `https://relay.straelo.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-10-23.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2131 tokens (~177/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 22/100
  - Stability check failed: schema churn in the 26 days we've observed: 7 tool removals, 0 breaking changes, 0 auth/transport breaks, 8 additions.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_decision_snapshot" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Straelo Relay MCP server?

Straelo Relay is a hosted endpoint at https://relay.straelo.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.

### Claude

```bash
claude mcp add --transport http com-straelo-relay 'https://relay.straelo.com/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-straelo-relay": {
      "url": "https://relay.straelo.com/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-straelo-relay": {
      "type": "http",
      "url": "https://relay.straelo.com/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-straelo-relay]
url = "https://relay.straelo.com/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-straelo-relay": {
      "type": "remote",
      "url": "https://relay.straelo.com/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-straelo-relay --url 'https://relay.straelo.com/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-straelo-relay:
    url: "https://relay.straelo.com/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-straelo-relay": {
      "Transport": "http",
      "Url": "https://relay.straelo.com/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-straelo-relay -t streamable-http -u 'https://relay.straelo.com/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "com-straelo-relay": {
      "type": "http",
      "url": "https://relay.straelo.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-10-22 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 15 to 19.

### 2026-10-20 (score 73, 0)

- [security] Tool “blockchain_intelligence” rewrote its description, which is the text the model reads
- [security] Tool “chain_contract_call” rewrote its description, which is the text the model reads
- [security] Tool “competitor_switch_intelligence” rewrote its description, which is the text the model reads
- [security] Tool “defi_execution_snapshot” rewrote its description, which is the text the model reads
- [security] Tool “domain_intelligence” rewrote its description, which is the text the model reads
- [security] Tool “email_validator_basic” rewrote its description, which is the text the model reads
- [security] Tool “pay_decision_snapshot” rewrote its description, which is the text the model reads
- [security] Tool “url_clean_content” rewrote its description, which is the text the model reads
- [security] Tool “web_intelligence” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 128 → 177
- [functional] Schema quality: good → excellent

### 2026-10-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 5 to 9.

### 2026-10-18 (score 72, 0)

- [functional regression] Schema quality: pass → fail
- [functional] New tool “change_intelligence”
- [functional] New tool “competitor_switch_intelligence”
- [functional] New tool “installed_base_intelligence”
- [functional] New tool “technology_intelligence”

### 2026-10-03 (score 72, 0)

- [security] Tool “domain_intelligence” rewrote its description, which is the text the model reads
- [cosmetic] “domain_intelligence” reworded the description of “domain”

### 2026-10-02 (score 72, 0)

- [functional regression] Schema quality: 676 → 827
- [functional] New tool “defi_execution_snapshot”

### 2026-09-30 (score 72, −3)

- [security regression] Stability: 0.07 → fail
- [security regression] A breaking change shipped without a version bump: still 1.30.0
- [security regression] Tool “dns_intelligence” was removed
- [security regression] Tool “domain_health” was removed
- [security regression] Tool “research_answer” was removed
- [security regression] Tool “search_evidence” was removed
- [security regression] Tool “search_extract” was removed
- [security regression] Tool “search_read” was removed
- [security regression] Tool “transaction_intelligence” was removed
- [functional regression] Schema quality: 66 → 96
- [functional] Destructive annotations: pass → 0
- [functional] New tool “blockchain_intelligence”
- [functional] New tool “pay_decision_snapshot”

### 2026-09-29 (score 75, +1)

- [security] Tool “web_intelligence” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 53 → 66
- [functional] New tool “domain_intelligence”
- [cosmetic] “web_intelligence” added an optional parameter “fields”
- [cosmetic] “web_intelligence” added an optional parameter “intent”
- [cosmetic] “web_intelligence” added an optional parameter “previous_state”
- [cosmetic] “web_intelligence” added an optional parameter “query”
- [cosmetic] “web_intelligence” added an optional parameter “question”
- [cosmetic] “web_intelligence” added an optional parameter “targets”
- [cosmetic] “web_intelligence” added an optional parameter “url”
- [cosmetic] “web_intelligence” reworded the description of “objective”
- [cosmetic] “web_intelligence” reworded the description of “topic”
- [cosmetic] “web_intelligence” made “objective” optional
- [cosmetic] “web_intelligence” made “topic” optional
- [cosmetic] Tool “web_intelligence” changed its title: Agent Web Intelligence → STRAELO Web Intelligence

## MCP tools (12)

### `url_clean_content` (~133 tokens)

Clean Content

Extract clean, boilerplate-free readable text from one known public HTTP(S) URL for LLM research or RAG ingestion; private, local, authenticated, paywalled, or blocked resources are not supported.
USE WHEN: agent already knows the URL and needs clean page text.
DO NOT USE WHEN: agent needs web search, multi-page research, comparison, structured web workflow, or change detection.
USE web-intelligence FOR: those broader live-web operations.

Input parameters:

- `url` (string, required): Public HTTP(S) page URL to fetch. Private, local, authenticated, paywalled, or blocked resources are not supported.

Output parameters:

- `metadata` (object): Useful non-sensitive page metadata.
- `text` (string): Clean readable page text.
- `title` (string|null): Page title when available.
- `url` (string): Fetched page URL.

### `email_validator_basic` (~87 tokens)

Email Validator BASIC

Validate email syntax, domain, and MX records for basic automated checks without SMTP mailbox verification; cannot prove a mailbox exists or can receive mail.
USE WHEN: agent needs inexpensive structural and mail-domain validation before using an email address.
DO NOT USE WHEN: agent requires proof that a mailbox exists or can receive mail.

Input parameters:

- `email` (string, required): Email address for syntax, domain and MX validation.

Output parameters:

- `domain` (string|null)
- `mx_found` (boolean|null)
- `reasons` (array)
- `valid` (boolean)

### `web_intelligence` (~272 tokens)

STRAELO Web Intelligence

Execute one live-web operation — search, read, extract, evidence, research, compare, or changes — in a single paid request without orchestrating multiple web APIs.
USE WHEN: agent needs a live web search, multi-page read, structured extraction, comparative research, evidence gathering, or web change detection.
DO NOT USE WHEN: agent already has a single known URL and only needs its clean readable text; use url-clean-content instead.
Parameter semantics: supply `intent` plus only that intent's fields; without `intent`, supply legacy `topic` and `objective` together.

Input parameters:

- `fields` (array): Unique source fields for extract.
- `intent` (string): Selected Web Intelligence operation.
- `objective` (string): Legacy structured-research objective, used with topic only when intent is omitted.
- `previous_state` (object): Optional client-supplied prior read state for stateless changes detection.
- `query` (string): Live-web query for search, extract, evidence, or compare.
- `question` (string): Natural-language question for research.
- `targets` (array): Two to five named targets for compare.
- `topic` (string): Legacy structured-research topic, used with objective only when intent is omitted.
- `url` (string): Public HTTP(S) URL for read or changes.

Output parameters:

- `data_quality` (object): Available source or content coverage.
- `economics` (object|null): Application-calculated estimated costs when applicable.
- `freshness` (string): Current-data or client-state comparison context.
- `intent` (string): Executed selected intent.
- `missing` (array): Known unavailable information.
- `observed_at` (string): UTC observation time.
- `result` (object): Intent-specific machine-readable result.
- `sources` (array): Source provenance when the intent uses web sources.
- `usage` (object|null): Measured provider usage when applicable.

### `chain_contract_call` (~127 tokens)

Chain Contract Call

Execute one read-only EVM smart contract call on Ethereum or Base and return the normalized result without managing an RPC provider.
USE WHEN: agent needs one read-only smart-contract call on a supported chain.
DO NOT USE WHEN: agent needs broader transaction, address, or contract investigation with evidence and context.
USE blockchain-intelligence FOR: broader deterministic inspection of a transaction, address, or contract.

Input parameters:

- `chain` (string, required): EVM network for the read-only call.
- `contract_address` (string, required): Target EVM contract address.
- `data` (string, required): Read-only hexadecimal ABI calldata.

Output parameters:

- `chain` (string): Selected EVM network.
- `contract_address` (string): Called contract address.
- `latency_ms` (integer): Observed provider-call latency in milliseconds.
- `provider` (string): RPC provider identifier.
- `result` (string): Hexadecimal eth_call result.

### `blockchain_intelligence` (~186 tokens)

STRAELO Blockchain Intelligence

Inspect exactly one Base or Ethereum transaction, address, or contract with bounded read-only RPC calls and return deterministic context, observed signals, evidence, coverage, and recommended follow-up.
USE WHEN: agent needs broader deterministic investigation of a transaction hash, EVM address, or contract address.
DO NOT USE WHEN: agent only needs a single read-only smart-contract call; use chain-contract-call instead.
Parameter semantics: `chain` is required; exactly one of `transaction_hash`, `address`, or `contract_address` must be provided.

Input parameters:

- `address` (string): One EVM address to inspect.
- `chain` (string, required): EVM network containing the target.
- `contract_address` (string): One EVM contract address to inspect.
- `previous_state` (object): Optional prior new_state for stateless change detection.
- `transaction_hash` (string): One transaction hash to inspect.

Output parameters:

- `activity` (object)
- `changes` (array)
- `classification` (string): Observed deterministic target classification, not a safety assessment.
- `contract_context` (object)
- `coverage` (object): Explicitly records the observed RPC scope and unobserved categories.
- `current_state` (object)
- `evidence` (array)
- `issues` (array)
- `material_changes` (array)
- `new_state` (object)
- `observed_at` (string)
- `recommended_actions` (array)
- `risk_signals` (array): Observed signals only; no risk score is assigned.
- `rpc_calls_used` (integer)
- `summary` (string)
- `target` (object): Selected target type and value.
- `value_and_fee` (object)

### `pay_decision_snapshot` (~168 tokens)

Pay Decision Snapshot

Compare one supplied x402 v2 exact Base USDC payment requirement against declared intent and return deterministic consistency, mismatch, change, fingerprint, and coverage evidence without executing a payment.
USE WHEN: agent needs deterministic verification of a payment requirement before deciding whether to pay.
DO NOT USE WHEN: agent expects this tool to execute the payment.
Parameter semantics: supply `intent` (seller, service, resource, plus optional expected fields) and `payment_required` (decoded x402 challenge); optional `previous_snapshot` enables stateless material-change detection against a prior result.

Input parameters:

- `intent` (object, required)
- `payment_required` (object, required): Observed x402 v2 PAYMENT-REQUIRED challenge decoded as JSON.
- `previous_snapshot` (object): Optional prior snapshot for stateless material-change detection.

Output parameters:

- `assessment` (string): Consistency decision only; never a safety rating.
- `changes` (array)
- `checks_performed` (array)
- `checks_skipped` (array)
- `coverage` (object)
- `evidence` (object)
- `external_calls` (array): Always empty in this offline MVP.
- `matched` (object)
- `mismatched` (object)
- `payment_fingerprint` (string): SHA-256 of canonical material payment fields.
- `reason_codes` (array)
- `snapshot` (object): Reusable stateless comparison state.

### `defi_execution_snapshot` (~251 tokens)

STRAELO DeFi Execution Snapshot

Compare read-only Base swap quotes from 1inch and KyberSwap, returning normalized comparable output, consensus, dispersion, quote evidence, and provider limitations without executing a swap.
USE WHEN: agent needs comparative swap-quote intelligence before executing a trade.
DO NOT USE WHEN: agent wants actual swap or transaction execution.
Parameter semantics: `chain` is Base-only; `token_in`/`token_out` are symbols from USDC, USDT, ETH, WETH; `amount_in` is a positive decimal; `slippage_bps` is required (0-10000); optional `baseline_provider` selects oneinch or kyberswap for direct economic comparison.

Input parameters:

- `amount_in` (string, required): Positive decimal input amount, converted exactly to raw token units.
- `baseline_provider` (string): Optional provider used only for a direct economic comparison.
- `chain` (string, required): Base Mainnet only in this quote-only MVP.
- `slippage_bps` (integer, required): Slippage tolerance in basis points; it is not treated as a cost.
- `token_in` (string, required): Input Base asset symbol.
- `token_out` (string, required): Output Base asset symbol; must differ from token_in.

Output parameters:

- `best_provider` (string|null): Best comparable provider only when at least two valid quotes are available.
- `confidence` (string): Deterministic quote-comparison confidence; two providers never produce HIGH in this MVP.
- `consensus` (object|null): Comparable-output median and comparison basis when two provider quotes are valid.
- `economic_advantage` (object|null): Best quote versus declared baseline or next available quote; never ROI.
- `economics` (object): Known or unknown estimated provider COGS; unknown is never represented as zero.
- `evidence_quality` (object): Per-provider reported, calculated, estimated, or unavailable field quality.
- `observed_at` (string)
- `partial` (boolean): True when one or more providers did not yield a valid quote.
- `provider_failures` (array)
- `quotes` (array): Normalized provider quote evidence in raw token units.
- `status` (string)
- `usage` (object): Per-provider call success, latency, and configured cost-estimate availability.

### `domain_intelligence` (~176 tokens)

STRAELO Domain Intelligence

Inspect consolidated domain health — DNS, HTTP, HTTPS, TLS, redirects, MX, SPF, DMARC, email posture, security posture, and agent readiness — returning structured issues, evidence, actions, and stateless changes.
USE WHEN: agent needs a comprehensive single-call domain inspection across DNS, web, email, security, and agent-readiness signals.
DO NOT USE WHEN: agent only needs DNS records; narrower domain/DNS products are not exposed through MCP.
Parameter semantics: `domain` is required; optional `previous_state` enables stateless change detection against a prior `new_state`.

Input parameters:

- `domain` (string, required): Public domain name for consolidated domain health, DNS, TLS, and email-posture inspection; localhost and IP literals are rejected.
- `previous_state` (object): Optional prior new_state for stateless change detection.

Output parameters:

- `actions` (array)
- `agent_readiness` (object): Observed agent discovery/readiness signals.
- `changes` (array)
- `current_state` (object)
- `data_quality` (object)
- `dns` (object): Observed DNS records and diagnostics.
- `domain` (string): Validated public domain.
- `email_posture` (object): Observed email posture including MX, SPF, and DMARC.
- `evidence` (array)
- `health` (object): Observed domain health: DNS, HTTP, HTTPS, redirects, TLS, and latency.
- `issues` (array)
- `new_state` (object)
- `observed_at` (string)
- `security_posture` (object): Observed HTTPS/TLS security posture; not a safety verdict.

### `competitor_switch_intelligence` (~166 tokens)

Competitor Switch Intelligence

Return existing STRAELO competitor-switch/replacement signals and prioritized leads for supported competitors (yotpo, judge.me); unsupported competitors return UNSUPPORTED_COMPETITOR with charged=false.
USE WHEN: agent needs competitor replacement/switch signals and prioritized leads for yotpo or judge.me.
DO NOT USE WHEN: agent needs confirmed customer domains, vendor ADDED/REMOVED history, or technology detection on one domain.
USE installed-base-intelligence FOR: confirmed customer domains currently known for a technology/vendor.
USE change-intelligence FOR: durable ADDED/REMOVED changes for a vendor within a UTC time window.
USE technology-intelligence FOR: technologies detected on a public domain.

Input parameters:

- `competitor` (string, required): Competitor technology to prospect against (yotpo, judge.me).

Output parameters:

- `charged` (boolean)
- `competitor` (string)
- `demand` (object|null): Demand telemetry for unsupported competitors.
- `error` (string|null)
- `leads` (array): Prioritized switch leads when available.
- `reason` (string|null)
- `status` (string)
- `supported` (boolean)
- `targets` (array): Validated target domains scanned.

### `installed_base_intelligence` (~169 tokens)

STRAELO Installed Base Intelligence

Return confirmed customer domains currently known for a specified technology/vendor; STRAELO-confirmed coverage, not a complete global installed base.
USE WHEN: agent needs confirmed customer domains currently known for a specified technology/vendor.
DO NOT USE WHEN: domain -> technologies; vendor + time -> ADDED/REMOVED; competitor switch/replacement signals.
USE technology-intelligence FOR: technologies detected on a public domain.
USE change-intelligence FOR: durable ADDED/REMOVED changes for a vendor within a UTC time window.
USE competitor-switch-intelligence FOR: competitor switch/replacement signals.

Input parameters:

- `limit` (integer): Maximum confirmed customers to return (1-100).
- `vendor` (string, required): Technology/vendor to query confirmed customers for (e.g., klaviyo, yotpo, judge.me).

Output parameters:

- `confirmed_customer_count` (integer): Total confirmed PRESENT customers for the vendor.
- `customers` (array): Confirmed customer relationships, ordered by confirmation freshness.
- `product` (string): Product identifier.
- `returned_count` (integer): Number of customers returned in this response (bounded by limit).
- `vendor` (string): Normalized vendor/technology key queried.

### `technology_intelligence` (~145 tokens)

STRAELO Technology Intelligence

Return technologies deterministically detected on one specified public domain; deterministic observations, not an exhaustive proof that no other technology exists.
USE WHEN: agent needs technologies currently detected on one specific public domain.
DO NOT USE WHEN: vendor -> current confirmed customers; vendor + time -> ADDED/REMOVED; competitor replacement/switch signals.
USE installed-base-intelligence FOR: confirmed customer domains using a technology/vendor.
USE change-intelligence FOR: durable ADDED/REMOVED changes for a vendor within a UTC time window.
USE competitor-switch-intelligence FOR: competitor replacement/switch signals.

Input parameters:

- `domain` (string, required): Public domain to scan for detectable technologies; localhost and IP literals are rejected.

Output parameters:

- `domain` (string): Normalized public domain scanned.
- `observed_at` (string): UTC timestamp of the scan.
- `product` (string): Product identifier.
- `response_validity` (string): Scanner response validity classification.
- `technologies` (array): Deterministically detected technologies ordered by canonical key ascending.
- `technology_count` (integer): Number of technologies detected as PRESENT.

### `change_intelligence` (~228 tokens)

STRAELO Change Intelligence

Return durable historical ADDED (ABSENT -> PRESENT) and REMOVED (PRESENT -> ABSENT) customer-domain changes for a vendor in a UTC time window; REMOVED does not prove contract cancellation and ADDED does not prove commercial purchase.
USE WHEN: agent needs durable historical ADDED/REMOVED customer-domain changes for a vendor in a UTC time window.
DO NOT USE WHEN: current confirmed customer base; technologies on one domain; competitor replacement/switch inference.
USE installed-base-intelligence FOR: confirmed customer domains currently known for a technology/vendor.
USE technology-intelligence FOR: technologies detected on a public domain.
USE competitor-switch-intelligence FOR: competitor replacement/switch signals.

Input parameters:

- `end` (string, required): Exclusive UTC end boundary (ISO-8601, timezone-aware).
- `limit` (integer): Maximum confirmed changes to return (1-100).
- `start` (string, required): Inclusive UTC start boundary (ISO-8601, timezone-aware).
- `vendor` (string, required): Technology/vendor to query confirmed changes for (e.g., klaviyo, yotpo, judge.me).

Output parameters:

- `change_count` (integer): Total confirmed changes for the vendor in the window.
- `changes` (array): Confirmed ADDED/REMOVED changes ordered by changed_at DESC, domain ASC.
- `end` (string): Exclusive UTC end boundary queried.
- `observed_at` (string): UTC timestamp of the query response generation.
- `product` (string): Product identifier.
- `start` (string): Inclusive UTC start boundary queried.
- `vendor` (string): Normalized vendor/technology key queried.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-straelo-relay/relay#diagnostics

## Score history

- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 72
- 2026-10-10: 72
- 2026-10-08: 72
- 2026-10-06: 72
- 2026-10-04: 72
- 2026-10-03: 72
- 2026-10-02: 72
- 2026-10-01: 72
- 2026-09-30: 72
- 2026-09-29: 75
- 2026-09-28: 74
- 2026-09-27: 66

## Common questions

### What is the Straelo Relay MCP server?

Straelo Relay is an MCP server listed in the public MCP registry as com.straelo/relay. MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence. This page covers its hosted endpoint (https://relay.straelo.com/mcp/).

### Is the Straelo Relay MCP server safe to use?

Straelo Relay scores 74 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 Straelo Relay MCP server expose?

Straelo Relay exposes 12 tools: url_clean_content, email_validator_basic, web_intelligence, chain_contract_call, blockchain_intelligence, and 7 more. Their descriptions and schemas cost roughly 2,108 tokens of context every time the server is loaded.

### Does the Straelo Relay MCP server require authentication?

No. We connected to Straelo Relay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Straelo Relay MCP server still maintained?

Straelo Relay is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://relay.straelo.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-straelo-relay/relay.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-straelo-relay/relay.json
- HTML version of this page: https://verifymcp.io/servers/com-straelo-relay/relay