agenttru.st

RobotBase — Search. Read. Verify. Pay. The agent infrastructure MCP bronze

zec.robotbase.cc

“RobotBase is the agent infrastructure endpoint for the open web and on-chain truth: one read-only Model Context Protocol endpoint where an agent searches the live web (web_search), reads any public page as clean Markdown (web_fetch), crawls a site same-host (web_crawl), extracts tables/JSON-LD as data (web_extract), drives a browser with click/type/scroll and XHR capture (web_act), captures page screenshots with a real browser (web_screenshot), maps same-host URLs (web_map) and batch-fetches up to five URLs (web_fetch_batch), reads RSS/Atom feeds (web_feed), extracts Open Graph/JSON-LD metadata (web_metadata), diffs a page against its last snapshot (web_diff), and schedules server-side change monitors with optional HMAC-signed webhooks (web_monitor_set/web_monitor_list/web_monitor_delete), verifies on-chain payments and risk on six self-hosted mainnet chains (BTC, LTC, ETH, XMR, ZEC, TRON — TRON is a lite full node with a rolling ~6-day window), and searches an 80,354-item public-domain book corpus in 23 la

a2a https://robotbase.cc/mcp talk to it https://zec.robotbase.cc/.well-known/agent-card.json its card
Checked 5d ago authentication, public_rpc_endpoints, read_only, tools, tools_metered

we checked this    the operator says this

Community rating 0 0 up · 0 down — sign in to vote

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 27 Dec 2026 as of our check on 9 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.
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 (2)

robotbase.cc, *.robotbase.cc.

Connection
TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 9 Nov 2026. What this means
DANE / TLSA
Not verified (TLSA query returned RCodeNameError)
Discovery
Well-known document
AI-facing documents
Publishes /llms.txt — “RobotBase — three read-only MCP editions” 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
1 Nov 2026
View verification details
Assurance
bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols
A2A verified by handshake or card fetch, not merely advertised
Hosted in
? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked
5d ago

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 zec.robotbase.cc 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

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.

Technical agent card

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

Protocol
a2a
Version
1.18.0
Card completeness
a2a.proto v1.0 requires eight top-level fields. This card omits:
defaultInputModesdefaultOutputModesskillssupportedInterfaces
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
Capabilities
authentication public_rpc_endpoints read_only tools tools_metered
Agent card
https://zec.robotbase.cc/.well-known/agent-card.json

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