sophia-house-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOK_BASE | No | Base URL for the public settlement book. By default the server hits the live settlement doors on the operator box (127.0.0.1). To point it at the public front, set this to https://socseal.xyz. | |
| SOCSEAL_BASE | No | Base URL for the settlement doors. By default the server hits the live settlement doors on the operator box (127.0.0.1). To point it at the public front, set this to https://socseal.xyz. |
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_settlementA | Prove a transaction id actually MINED on-chain (SEPTA: height>0 and out of mempool). Submit a 64-hex txid, get the block-confirmed verdict + post-quantum signed evidence. Fail-closed: unknown/never-mined ids return a clean negative, never a fake success. Read-only; does not pay. |
| anchor_receiptA | Confirm an anchor stamp is on-chain: given a txid, report SEPTA mined status (height>0, out of mempool) from the keeper, and if that txid is a known settlement-book anchor, return its full record (block, atoms, sealed text, verify status). Read-only. |
| book_statusA | Read the public settlement book for a day: day number, status, merkle roots (root_open/root_close), clearing summary and the on-chain anchor (block, txid, verify status). Read-only public mirror. Use this to audit the venue's market history. |
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 3 tools
verify_settlement and anchor_receipt both check SEPTA mined status for a given txid; the latter adds anchor record retrieval, so an agent might pick verify_settlement when it actually needs anchor_receipt. Descriptions differentiate the special case, but the overlap in on-chain verification logic creates some ambiguity.
verify_settlement and anchor_receipt follow a verb_noun pattern, but book_status is noun_noun, and the verb choices are not from a consistent family. Still mostly readable but mixed conventions.
Three tools is lean but each covers a distinct read-only operation (verify a tx, verify an anchor, read a day's book) for a narrow settlement-verification service. Slightly under-scoped but reasonable.
Covers verifying a single txid, verifying an anchor stamp, and reading a day's settlement book. Missing batch verification or lookup of individual settlement details by other criteria, but core audit needs are met.