exploreme-sei-mcp bronze

testnet.seistream.app

“# Exploreme MCP (Sei dual-chain) This server exposes Sei chain data over MCP. Its EVM and Cosmos surfaces share one network while retaining separate address and transaction formats. - Unified API route prefix: /api/v2 - EVM and Cosmos tools use the same backend; their path namespaces remain separate. - Search and pointer availability follow the deployed API surface. - Explorer UI: https://seistream.app - Scope: auto ## Tool naming convention - `*_evm_*` — EVM side: 0x... addresses, 0x... tx hashes, eth_* RPC. - `*_cosmos_*` — Cosmos side: bech32 addresses (sei..., seivaloper...), cosmos tx hashes. - `get_pointer_mapping` — resolve EVM/Cosmos address counterparts where the chain supports pointer mappings. - `explorer_search` — dispatcher: hands an arbitrary query to the indexer, returns EVM or Cosmos hits. ## Signing No private key ever reaches this server. Write flows always use prepare → sign externally → broadcast: - EVM: `prepare_*` returns unsigned tx fields; user signs with vie

https://api.seistream.app/mcp its card

✓ Checked 5d ago “ prompts, resourceTemplates, resources, tools

✓ we checked this   “ the operator says this

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate

Issued by Google Trust Services domain-validated

Valid until 14 Jan 2027 as of our check on 9 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

api.seistream.app.

Connection

TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 9 Nov 2026. The agent is served from api.seistream.app, so that server's operator chose this. What this means

DANE / TLSA

Not verified (TLSA query returned RCodeNameError)

Discovery

Well-known document

This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 2 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified.

AI use policy

Search: yesAI input: yesAI training: no

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.

AI-facing documents

Publishes /llms.txt — “Seistream” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.

First seen

12 Oct 2026

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of testnet.seistream.app controls every word below.

This card declares no skills. That is not a fault — the field is optional, and an agent can be perfectly functional without describing itself.

What kind of listing

• No skills declared: Its card declares no skills, or, for an MCP server, listed no tools.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

What its catalog declares

From the ARD catalog this host publishes at /.well-known/ai-catalog.json. The operator controls every entry; agenttru.st verified that the catalog exists and parses, and nothing about what the entries say.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol

mcp

Version

0.1.0

Operate this agent and would rather not be listed? Request removal.