SPACEXPLORATION Public bronze

spacexploration.com

“External MCP server for SPACEXPLORATION commercial real estate listings. Read tools (search_listings, get_listing, get_parcel, interpret_search, get_registry, get_faq) work anonymously — no token needed. For any question about SPACEXPLORATION itself (what it costs, listing a property, accounts, the built-in assistant), call `get_faq`, answer from it, and link the url each entry carries. Account-bound tools (building lookups by address, saved searches, geocoding, listing authoring) require OAuth 2.0 Authorization Code + PKCE (Passport-issued bearer token, scope: mcp:use; a client is its own HTTPS Client ID Metadata Document URL, or self-registers via Dynamic Client Registration — fetch /auth.md for the walkthrough). Listing authoring additionally requires a verified email address, and listing mutations are gated on the caller owning the underlying listing. When the user wants to report a bug, request a feature, or ask the SPACEXPLORATION team a question, file it with `send_feedback` (works anonymously).

https://spacexploration.com/mcp its card

✓ Checked 5d ago “ prompts, 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 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)

spacexploration.com, *.spacexploration.com.

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

Discovery

Well-known document

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

AI use policy

Search: yesAI input: yesAI training: yes

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 — “SPACEXPLORATION” 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

2 Nov 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 spacexploration.com 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

1.4.1

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