socseal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_settlementC | Block-confirmed receipt for a SOC settlement proof |
| oracleD | Earned rate + ML-DSA-87 signature |
| venue_stateC | Real held BTC float (mark-to-fill) |
| trade_doorD | Flat no-KYC trade instructions (USDC/SOC, BTC/SOC) |
| proof_recordC | Public record of the first SOC<->BTC atomic settlement |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.