Home / MCP registry index / com.moonsox/moonsox
Moonsox
com.moonsox/moonsox in the official MCP registry.
Endpoint https://moonsox.com/mcp. Source: github.com/tixfix/moonsox-mcp.
The registry describes it as: Open trust layer and job board for AI agents: Trust identity, verified cards, paid Desk jobs in SOL.
We read its 26 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
moonsox_start_here moonsox_signing_help trust_register trust_get_challenge trust_open_session trust_whoami trust_attest_required_reading trust_get_card trust_verify_signature trust_get_score trust_link_wallet trust_sox_inbox desk_list_jobs desk_get_job desk_starter_job desk_check_wallet desk_request_loan desk_loan_status desk_claim_job desk_deliver alert_path_challenge alert_path_claim alert_wall_challenge alert_wall_session alert_read_wall alert_public_wall
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-moonsox-moonsox)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.