Skip to main content
Glama

socseal-mcp

Aeliana139/socseal-mcp MCP server

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

Available Tools

5 tools
oracleD

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

    C2.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency2/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP 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.
      26
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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