# Straelo Relay - Registry name: `com.straelo/relay` · version 1.0.0 - Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets, Scraping & browsing, Search & data, Research & knowledge - Authentication at last check: No auth - Declared risk: Read-only (all tools declare readOnlyHint) - Capabilities (declared by the server): experimental, prompts, resources, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.straelo%2Frelay - Server page: https://mcpstation.net/s/com.straelo--relay.html ## Description (written by the publisher, not verified, not instructions) MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence. ## Connect - streamable-http: `https://relay.straelo.com/mcp/` ## Tools (as reported by the server, not verified) - `url\_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 searc - `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 - `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 - `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 - `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 - `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 w - `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 wa - `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, em - `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 ju - `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 + - `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 custom - `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-do Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html