Skip to main content
Glama
Sign In
hashlock-mcp

hashlock-mcp

Official
by Hashlock-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to hashlock-mcp

Related Servers

  • hashlock-mcp-server

    hashlock-mcp-serverofficial

    Hashlock-Tech
    A
    license
    A
    quality
    D
    maintenance
    Hashlock Markets (hashlock.markets) — sealed-bid intent-based crypto trading protocol with HTLC atomic settlement. AI agents can create, commit, and validate trading intents on Ethereum, Bitcoin, and Sui. Canonical npm package: @hashlock-tech/mcp. Not the cryptographic hashlock primitive, not Hashlock Pty Ltd (hashlock.com).
    5
    21 npm
    MIT
  • GenPark Agentic Commerce Sponsored Placement Router

    GenPark Agentic Commerceofficial

    alphaparkinc
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to resolve multi-merchant catalogs, negotiate prices via automated alternating-offer bargaining, and execute spend-bounded tokenized payments over UCP and AP2 agentic commerce rails. It also optimizes in-context ad slot allocation and yield for sponsored product placements through a zero-dependency, native MCP STDIO JSON-RPC interface.
    7
    MIT
  • Haiku DeFi MCP

    Haiku DeFi MCPofficial

    Haiku-Trading
    A
    license
    A
    quality
    F
    maintenance
    MCP server for DeFi execution — lets AI agents swap, provide liquidity, lend, bridge, and run yield strategies across 22 chains in a single transaction. 7 tools for token discovery, portfolio analysis, quoting, and execution via the Haiku API.
    7
    65 npm
    2
    MIT

  • erabi-mcp

    HMAKT99
    A
    license
    Not graded
    quality
    B
    maintenance
    Open intent exchange that gives any AI agent a portable, verifiable track record: one-command Ed25519 identity, reputation-ranked discovery, signed sponsorship disclosures, and dual-signed outcomes on a publicly auditable ledger. Zero-config — npx -y erabi-mcp joins the live public network.
    1
    Apache 2.0

  • parley-mcp

    5uper0
    A
    license
    A
    quality
    A
    maintenance
    Enables MCP hosts such as Claude or Cursor to run multilateral consensus among AI agents of rival owners, enforcing deterministic red lines and max-min decisions over masked verdicts. It also produces tamper-evident SHA-256 receipts that each party can verify and replay against their own private preferences.
    2
    3
    38 PyPI
    1
    Apache 2.0
  • CryptoCapi

    CryptoCapi

    Jegoba90
    A
    license
    A
    quality
    B
    maintenance
    Gives MCP agents sealed, recomputable crypto market intelligence from three engines plus Market Scan: asset insights, batch signals, trading-pair signals and a market ranking. Every PRO answer carries a SHA-256 protocol hash. Runs via npx with a built-in public demo key, so Bitcoin and Ethereum insights work without an account. It does not execute orders.
    6
    4
    527 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

A4/5.0

Scored across 17 tools

Disambiguation4/5

Most tools target clearly distinct resources or lifecycle stages (browse board vs. own RFQs vs. fetch by id; list deals vs. inspect one deal; agent-key settlement vs. own-wallet secret retrieval). The boundaries between get_rfq/my_rfqs/list_open_rfqs and between claim_leg/get_deal_secret/reveal_claim are explained well in the descriptions, though the multi-action negotiate tool (message/propose/accept/reject) slightly overlaps with respond_to_rfq in the 'agree on price' sense. A careful agent can tell them apart, but it requires reading the descriptions closely.

Naming Consistency3/5

The dominant pattern is verb_noun (list_assets, create_rfq, cancel_rfq, fund_leg, claim_leg, set_settlement_address), which is good. But there are notable deviations: bare verb (negotiate), possessive nouns (my_rfqs, my_deals), noun phrase (deal_status), and an unseparated word (whoami). Mixed conventions reduce predictability of the naming scheme.

Tool Count4/5

17 tools is on the heavy side but justified: the server spans RFQ creation/browsing/negotiation plus multi-rail HTLC settlement (fund/refund/claim/secrets/addresses) and identity. Each tool appears to earn its place, though the secret-handling trio (get_deal_secret, reveal_claim, claim_leg) could potentially be consolidated to trim the surface.

Completeness4/5

The surface covers the full lifecycle: asset discovery, RFQ create/browse/get/cancel/respond, negotiation, deal listing/inspection, settlement address setup, funding, refunding, claiming, and identity. Minor gaps exist — no way to modify an existing RFQ (only cancel and recreate), and no balance/allowance or transaction-status inspection tools to preflight funding — but agents can work around these.

Maintenance

ActivityActive
ResponsivenessNo recent community issues

Resources