Skip to main content
Glama

Related Servers

Alternatives to peerkith-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Read-only MCP (stdio) server for the socseal settlement venue — prove a payment MINED on-chain, read the public settlement book, anchor receipts. No KYC, no custody, fail-closed. Experimental, R=0 external payers.
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Zero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to locally verify nomue Protocol Release 1 Welch Records, performing scoped structural, digest, admissibility, computability, and two-sided Welch recomputation checks over stdio without requiring accounts, API keys, or network access.
      36 npm
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Tenant-bound MCP server for agent spend authorization, policy guardrails, evidence, escrow settlement, and portable receipts. Works with Cursor and Claude Code via stdio; npm (@paybond/kit) and Python (paybond-kit).
      31
      72 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      MCP security firewall (stdio): vet advertised tool definitions through static-scan → threat-feed → origin → pinning before they reach the model. Zero npm runtime deps. No secrets.
      9
      825 npm
      MIT

    TDQS

    B3/5.0

    Scored across 12 tools

    Disambiguation3/5

    Most tools target distinct resources or actions, but room_post is an explicit alias of post, and cap_check overlaps with cap_preflight in checking caps and potentially minting cap_token. Descriptions clarify intended usage, but an agent could still hesitate between the cap tools.

    Naming Consistency3/5

    Many tools follow a noun_verb pattern (pending_get, wall_get, trail_get, cap_check, cap_token_check), but the set also includes bare verbs (verify, post), a differently named alias (room_post), and a demo suffix (spend_demo). It is readable but not fully uniform.

    Tool Count4/5

    12 tools is within a reasonable range for this multi-resource verification and capability server. The redundant room_post alias makes the count slightly heavier than necessary, but not problematic.

    Completeness4/5

    The surface covers key reads (pending, wall, trail, llms, showcase), posting/verifying rows, and cap/token/spend lifecycle checks. Some edges such as cap discovery or room retrieval are not exposed, but core workflows appear workable.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive