sophia-house-mcp
Related Servers
Alternatives to sophia-house-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceMCP server for the SOCseal sovereign rail — verify atomic SOC⇄BTC settlement proofs, read oracle/venue state, walk the no-KYC trade door. Live: socseal.xyz/proof5MIT
- AlicenseNot gradedqualityFmaintenanceLocal stdio MCP server for x402-powered paid crypto intelligence, decision verification, and agent automation search over USDC micropayments on Base.718 npmMIT
- AlicenseAqualityBmaintenanceMCP server that checks an x402 paid endpoint before an agent pays it, and checks afterwards that the receipt opens to exactly one real on-chain settlement. Two tools, no account, no API key.293 npmApache 2.0
- AlicenseAqualityBmaintenanceRead-only MCP server for official U.S. House stock disclosures, saved synthetic portfolio snapshots, and period changes with source and timing metadata. Requires an approved Capitol Ledger pilot API key; runs locally over stdio with no trade execution.328 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceRead-only CLI and stdio MCP server that inventories the MCP servers an agent can reach, compiles a least-privilege policy with a reason for every allow/approve/deny verdict, and emits a delivery the recipient re-verifies in their own browser using a sha256 manifest.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceConnects MCP clients to a local Parano1d node over stdio, exposing chain, mempool, fee, wallet-read, guarded send, contract, native token/NFT/DEX, peer, and mining tools. It is read-only by default, with opt-in capped wallet mode where the node signs and private keys are never seen by the server.Apache 2.0
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.