Skip to main content
Glama
Aeliana139

sophia-house-mcp

by Aeliana139
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sophia-house-mcp

No user-submitted related servers found.

    Related Servers

    • socseal

      Aeliana139
      A
      license
      C
      quality
      B
      maintenance
      MCP 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/proof
      5
      MIT

    • Ratchet

      suhui-organization
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-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

    • sealchat-agent-mcp

      kagangtuya-star
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that provides tools to fetch SealChat public protocol docs, manifest, channel counts, and chat messages via the HTTP Agent API, without write access or database access.
      MIT

    • nostr-mcp

      DiegoYegros
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for safely exploring Nostr, enabling agents to resolve identifiers, fetch profiles and events, query notes, and inspect relay metadata. It does not accept private keys or publish events.
      5
      7 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation3/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources