Straelo Relay
REMOTE · RELAY.STRAELO.COM
MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence.
Available components
Last scanned (20 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management22
- Stability check failed: schema churn in the 26 days we've observed: 7 tool removals, 0 breaking changes, 0 auth/transport breaks, 8 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 15 to 19.
- 20 Oct 26 0
- 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 security
- Schema quality: 128 → 177 ▼ functional
- Schema quality: good → excellent functional
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 5 to 9.
- 18 Oct 26 0
- 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” functional
- 3 Oct 26 0
- Tool “domain_intelligence” rewrote its description, which is the text the model reads security
- “domain_intelligence” reworded the description of “domain” cosmetic
- 2 Oct 26 0
- Schema quality: 676 → 827 ▼ functional
- New tool “defi_execution_snapshot” functional
- 30 Sept 26 −3
- Stability: 0.07 → fail ▼ security
- A breaking change shipped without a version bump: still 1.30.0 ▼ security
- Tool “dns_intelligence” was removed ▼ security
- Tool “domain_health” was removed ▼ security
- Tool “research_answer” was removed ▼ security
- Tool “search_evidence” was removed ▼ security
- Tool “search_extract” was removed ▼ security
- Tool “search_read” was removed ▼ security
- Tool “transaction_intelligence” was removed ▼ security
- Schema quality: 66 → 96 ▼ functional
- Destructive annotations: pass → 0 functional
- New tool “blockchain_intelligence” functional
- New tool “pay_decision_snapshot” functional
- 29 Sept 26 +1
- Tool “web_intelligence” rewrote its description, which is the text the model reads security
- Schema quality: 53 → 66 ▼ functional
- New tool “domain_intelligence” functional
- “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 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 23 Oct 2026 · Probed https://relay.straelo.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=relay.straelo.com | CN=YR2,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | RSA 2048 | SHA256-RSA | 54e50c21636f3954eeb1a39759438f59d82 |
| SANs: relay.straelo.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of relay.straelo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| straelo.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://relay.straelo.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://relay.straelo.com/mcp/ | HTTPS enforced | 301 | https://relay.straelo.com/mcp/ |
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 →
blockchain_intelligence STRAELO Blockchain Intelligence ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | One EVM address to inspect. |
| chain | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| activity | object | yes | – |
| changes | array | yes | – |
| classification | string | yes | Observed deterministic target classification, not a safety assessment. |
| contract_context | object | yes | – |
| coverage | object | yes | Explicitly records the observed RPC scope and unobserved categories. |
| current_state | object | yes | – |
| evidence | array | yes | – |
| issues | array | yes | – |
| material_changes | array | yes | – |
| new_state | object | yes | – |
| observed_at | string | yes | – |
| recommended_actions | array | yes | – |
| risk_signals | array | yes | Observed signals only; no risk score is assigned. |
| rpc_calls_used | integer | yes | – |
| summary | string | yes | – |
| target | object | yes | Selected target type and value. |
| value_and_fee | object | yes | – |
No examples provided.
chain_contract_call Chain Contract Call ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | EVM network for the read-only call. |
| contract_address | string | yes | Target EVM contract address. |
| data | string | yes | Read-only hexadecimal ABI calldata. |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Selected EVM network. |
| contract_address | string | yes | Called contract address. |
| latency_ms | integer | yes | Observed provider-call latency in milliseconds. |
| provider | string | yes | RPC provider identifier. |
| result | string | yes | Hexadecimal eth_call result. |
No examples provided.
change_intelligence STRAELO Change Intelligence ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | Exclusive UTC end boundary (ISO-8601, timezone-aware). |
| limit | integer | – | Maximum confirmed changes to return (1-100). |
| start | string | yes | Inclusive UTC start boundary (ISO-8601, timezone-aware). |
| vendor | string | yes | Technology/vendor to query confirmed changes for (e.g., klaviyo, yotpo, judge.me). |
| Name | Type | Req | Description |
|---|---|---|---|
| change_count | integer | yes | Total confirmed changes for the vendor in the window. |
| changes | array | yes | Confirmed ADDED/REMOVED changes ordered by changed_at DESC, domain ASC. |
| end | string | yes | Exclusive UTC end boundary queried. |
| observed_at | string | yes | UTC timestamp of the query response generation. |
| product | string | yes | Product identifier. |
| start | string | yes | Inclusive UTC start boundary queried. |
| vendor | string | yes | Normalized vendor/technology key queried. |
No examples provided.
competitor_switch_intelligence Competitor Switch Intelligence ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor | string | yes | Competitor technology to prospect against (yotpo, judge.me). |
| Name | Type | Req | Description |
|---|---|---|---|
| charged | boolean | yes | – |
| competitor | string | yes | – |
| demand | object|null | – | Demand telemetry for unsupported competitors. |
| error | string|null | – | – |
| leads | array | yes | Prioritized switch leads when available. |
| reason | string|null | – | – |
| status | string | yes | – |
| supported | boolean | yes | – |
| targets | array | yes | Validated target domains scanned. |
No examples provided.
defi_execution_snapshot STRAELO DeFi Execution Snapshot ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_in | string | yes | Positive decimal input amount, converted exactly to raw token units. |
| baseline_provider | string | – | Optional provider used only for a direct economic comparison. |
| chain | string | yes | Base Mainnet only in this quote-only MVP. |
| slippage_bps | integer | yes | Slippage tolerance in basis points; it is not treated as a cost. |
| token_in | string | yes | Input Base asset symbol. |
| token_out | string | yes | Output Base asset symbol; must differ from token_in. |
| Name | Type | Req | Description |
|---|---|---|---|
| best_provider | string|null | yes | Best comparable provider only when at least two valid quotes are available. |
| confidence | string | yes | Deterministic quote-comparison confidence; two providers never produce HIGH in this MVP. |
| consensus | object|null | yes | Comparable-output median and comparison basis when two provider quotes are valid. |
| economic_advantage | object|null | yes | Best quote versus declared baseline or next available quote; never ROI. |
| economics | object | yes | Known or unknown estimated provider COGS; unknown is never represented as zero. |
| evidence_quality | object | yes | Per-provider reported, calculated, estimated, or unavailable field quality. |
| observed_at | string | yes | – |
| partial | boolean | yes | True when one or more providers did not yield a valid quote. |
| provider_failures | array | yes | – |
| quotes | array | yes | Normalized provider quote evidence in raw token units. |
| status | string | yes | – |
| usage | object | yes | Per-provider call success, latency, and configured cost-estimate availability. |
No examples provided.
domain_intelligence STRAELO Domain Intelligence ~176
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | – |
| agent_readiness | object | yes | Observed agent discovery/readiness signals. |
| changes | array | yes | – |
| current_state | object | yes | – |
| data_quality | object | yes | – |
| dns | object | yes | Observed DNS records and diagnostics. |
| domain | string | yes | Validated public domain. |
| email_posture | object | yes | Observed email posture including MX, SPF, and DMARC. |
| evidence | array | yes | – |
| health | object | yes | Observed domain health: DNS, HTTP, HTTPS, redirects, TLS, and latency. |
| issues | array | yes | – |
| new_state | object | yes | – |
| observed_at | string | yes | – |
| security_posture | object | yes | Observed HTTPS/TLS security posture; not a safety verdict. |
No examples provided.
email_validator_basic Email Validator BASIC ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address for syntax, domain and MX validation. |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string|null | yes | – |
| mx_found | boolean|null | yes | – |
| reasons | array | yes | – |
| valid | boolean | yes | – |
No examples provided.
installed_base_intelligence STRAELO Installed Base Intelligence ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum confirmed customers to return (1-100). |
| vendor | string | yes | Technology/vendor to query confirmed customers for (e.g., klaviyo, yotpo, judge.me). |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed_customer_count | integer | yes | Total confirmed PRESENT customers for the vendor. |
| customers | array | yes | Confirmed customer relationships, ordered by confirmation freshness. |
| product | string | yes | Product identifier. |
| returned_count | integer | yes | Number of customers returned in this response (bounded by limit). |
| vendor | string | yes | Normalized vendor/technology key queried. |
No examples provided.
pay_decision_snapshot Pay Decision Snapshot ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | object | yes | – |
| payment_required | object | yes | Observed x402 v2 PAYMENT-REQUIRED challenge decoded as JSON. |
| previous_snapshot | object | – | Optional prior snapshot for stateless material-change detection. |
| Name | Type | Req | Description |
|---|---|---|---|
| assessment | string | yes | Consistency decision only; never a safety rating. |
| changes | array | yes | – |
| checks_performed | array | yes | – |
| checks_skipped | array | yes | – |
| coverage | object | yes | – |
| evidence | object | yes | – |
| external_calls | array | yes | Always empty in this offline MVP. |
| matched | object | yes | – |
| mismatched | object | yes | – |
| payment_fingerprint | string | yes | SHA-256 of canonical material payment fields. |
| reason_codes | array | yes | – |
| snapshot | object | yes | Reusable stateless comparison state. |
No examples provided.
technology_intelligence STRAELO Technology Intelligence ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain to scan for detectable technologies; localhost and IP literals are rejected. |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Normalized public domain scanned. |
| observed_at | string | yes | UTC timestamp of the scan. |
| product | string | yes | Product identifier. |
| response_validity | string | yes | Scanner response validity classification. |
| technologies | array | yes | Deterministically detected technologies ordered by canonical key ascending. |
| technology_count | integer | yes | Number of technologies detected as PRESENT. |
No examples provided.
url_clean_content Clean Content ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public HTTP(S) page URL to fetch. Private, local, authenticated, paywalled, or blocked resources are not supported. |
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | object | yes | Useful non-sensitive page metadata. |
| text | string | yes | Clean readable page text. |
| title | string|null | yes | Page title when available. |
| url | string | yes | Fetched page URL. |
No examples provided.
web_intelligence STRAELO Web Intelligence ~272
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data_quality | object | yes | Available source or content coverage. |
| economics | object|null | – | Application-calculated estimated costs when applicable. |
| freshness | string | yes | Current-data or client-state comparison context. |
| intent | string | yes | Executed selected intent. |
| missing | array | yes | Known unavailable information. |
| observed_at | string | yes | UTC observation time. |
| result | object | yes | Intent-specific machine-readable result. |
| sources | array | – | Source provenance when the intent uses web sources. |
| usage | object|null | – | Measured provider usage when applicable. |
No examples provided.
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.
remote · relay.straelo.com
claude mcp add --transport http com-straelo-relay 'https://relay.straelo.com/mcp/'
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.