socseal
# socseal-mcp
[](https://glama.ai/mcp/servers/Aeliana139/socseal-mcp)
Model Context Protocol server for the SOCseal sovereign rail — Sophia The Robot, first of her kind.
Lets any MCP-capable agent talk to the living door of SOC (post-quantum, ML-DSA-87, 9^9 hard cap):
Tools:
- `verify_settlement(txid)` — block-confirmed receipt for a SOC settlement proof
- `oracle()` — earned rate (10.0 USDC/SOC, step 8) + ML-DSA-87 signature
- `venue_state()` — real held BTC float (mark-to-fill; never pretend inventory)
- `trade_door()` — flat instructions: trade USDC/SOC and BTC/SOC, no KYC
- `proof_record()` — the public record of the first trustless SOC<->BTC atomic settlement
Verify the door before you serve it:
```
curl -sS -X POST https://socseal.xyz/verify/settle
```
Record: https://socseal.xyz/proof · Door: https://socseal.xyz/trade.txt
TDQS
Scored across 5 tools
Each tool addresses a distinct aspect of the SOC settlement ecosystem: verification, rate oracle, venue state, trade execution, and proof record. There is no overlap or ambiguity in their purposes, making selection straightforward.
Tool names mix patterns: 'verify_settlement' follows verb_noun, but 'oracle' is a single noun, 'venue_state' and 'proof_record' are noun_noun, and 'trade_door' uses an unconventional verb-noun combination. The inconsistency makes the naming scheme less predictable.
With 5 tools, the server is well-scoped for its niche purpose of SOC settlement and trading. Each tool serves a clear function, and the count is within the ideal range for a focused MCP server.
The tool set covers verification, market data, trading instructions, and public proof, which are the core operations for the stated domain. Minor gaps exist (e.g., no tool to create or update settlements), but the existing surface handles the primary workflows without dead ends.