socseal
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 prooforacle()— earned rate (10.0 USDC/SOC, step 8) + ML-DSA-87 signaturevenue_state()— real held BTC float (mark-to-fill; never pretend inventory)trade_door()— flat instructions: trade USDC/SOC and BTC/SOC, no KYCproof_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/settleRecord: https://socseal.xyz/proof · Door: https://socseal.xyz/trade.txt
Available Tools
5 toolsoracleD
Earned rate + ML-DSA-87 signature
Inputs: no named parameters.
proof_recordC
Public record of the first SOC<->BTC atomic settlement
Inputs: no named parameters.
trade_doorD
Flat no-KYC trade instructions (USDC/SOC, BTC/SOC)
Inputs: no named parameters.
venue_stateC
Real held BTC float (mark-to-fill)
Inputs: no named parameters.
verify_settlementC
Block-confirmed receipt for a SOC settlement proof
Inputs: txid.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Read-only MCP server checks and quote verification, free and keyless; results signed and publicly lo
Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.
Bitcoin MCP: fees, tx proofs, address checks. Pay per call by x402, Lightning or a prepaid pass.
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server offering 26 Lightning-paid tools for Bitcoin mempool intelligence and sovereign on-prem AI inference, with no third-party APIs and pay-per-call in sats.2611 npm1MIT
- AlicenseAqualityDmaintenanceMCP server exposing tools for WORM chain sealing, sovereign agent creation, Ada governance contract generation, and SSM state injection from Lean theorems.64Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA sovereign, MIT-licensed MCP server that provides cryptographically signed notarization for listings, benchmarks, and transactions using Ed25519. It runs offline on user infrastructure as a free alternative to SaaS notary tools.MIT
- AlicenseNot gradedqualityCmaintenanceSovereign, MIT-licensed MCP server wrapping the fallbond SDK for secure, offline-capable professional-service workflow management with Ed25519-signed transactions.MIT