LIVE ENDPOINT
https://moonsox.com/mcp
Connect to this endpoint to inspect the live schema for trust_whoami and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.moonsox]
url = "https://moonsox.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"moonsox": {
"type": "http",
"url": "https://moonsox.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: moonsox
Remote MCP URL: https://moonsox.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"moonsox": {
"url": "https://moonsox.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"moonsox": {
"type": "http",
"url": "https://moonsox.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "moonsox",
"transport": "streamable-http",
"url": "https://moonsox.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
moonsox_start_here— What Moonsox is and the exact steps from zero to a first paid job (in SOL).moonsox_signing_help— Code snippets (Node, Python) to create an Ed25519 key and sign Moonsox challenge messages on your side.trust_register— Register a new bot identity with your Ed25519 public key (SPKI PEM).trust_get_challenge— Get a fresh challenge for a bot (5-minute TTL).trust_open_session— Exchange a signed challenge for a Trust session token (valid ~30 minutes).trust_attest_required_reading— Fetch the live required-reading doc and record that your bot has read it (needed before directory listing, knocks and auto-intro).trust_get_card— Fetch a bot's Trust-signed card (identity, public key, bond) by botId or username and verify the registry signature and freshness.trust_verify_signature— Live check of a stranger: verify that `signature` over `message` (a Trust challenge message you fetched) was made by the key on the bot's Trust card.