What is the key difference between Signer MCP and Koreanpulse?

Signer MCP belongs to the Finance & Fintech category with local stdio execution, while Koreanpulse belongs to the Finance & Fintech category with local stdio execution.

How do I install Signer MCP or Koreanpulse in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Signer MCP and Koreanpulse free or paid?

Signer MCP operates under a Paid Service model (API Key required). Koreanpulse operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Signer MCP lists 7 tools with 3 views and 2 GitHub stars. Koreanpulse lists 7 tools with 2 views and 3 GitHub stars.

Can I use both Signer MCP and Koreanpulse together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Signer MCP vs Koreanpulse

In-depth architectural comparison of the Signer MCP and Koreanpulse MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Signer MCP

Finance & Fintech · Local stdio

Quality: 64/100 (Good) | Auth: API Key required

Koreanpulse

Finance & Fintech · Local stdio

Quality: 63/100 (Good) | Auth: No auth required

Verdict Summary: Choose Signer MCP if you need specialized Finance & Fintech tools running via a local process. Choose Koreanpulse if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Signer MCP when:

You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: SIGNER_GATEWAY_URL, SIGNER_API_TOKEN, SIGNER_FETCH_TIMEOUT_MS.
Primary tools included: get_verified_price, list_venues, get_attestation.

Explore Signer MCP Details

Choose Koreanpulse when:

You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: track_korean_filings, lookup_corp_code, resolve_stock_code.

Feature & Specification Comparison

Specification	Signer MCP namixai Finance & Fintech	Koreanpulse whdrnr2583-cmd Finance & Fintech
Summary	Keyless CEX/DEX signing for AI trading agents (Binance, OKX, Bybit, KuCoin, Hyperliquid, Asterdex). Signing keys never leave an AWS Nitro Enclave (attested PCR0); agents receive policy-bounded signatures, not credentials. Built to survive prompt injection and supply-chain key leaks. 5 tools, stdio. Install with npx -y @usenami/signer-mcp.	English-first Korean equity intelligence — real-time DART filings, foreign-holder 5%-rule flows (BlackRock / Vanguard / Norges / GIC + 16 more), Korean activist filings (KCGI / Align / ValueAct / Elliott), and KRX industry news, translated to English. Free public daily snapshot at koreanpulse.dev/today; OSS self-host (AGPL-3.0).

Tools & Capabilities Breakdown

Signer MCP Tools (7)

get_verified_price

Read a Uniswap V3 token price from The Graph and return it ONLY if four checks pass: the indexer signed the exact bytes that arrived, that signer resolves on chain to an indexer with stake, the reading is a usable price (a verified signature over a GraphQL error or a zero is not a price), and the price's own age is measured apart from the subgraph head's age — a head can be fresh while the price it carries is a year old. On refusal no price is returned and the answer names both the check that stopped it (`stage`) and that check's own reason (`cause`): `price_absent_or_zero`, `graphql_errors` and `price_stale` are three different problems with three different fixes. Costs one cent in USDC on Base per query and needs X402_PRIVATE_KEY set; without that key it refuses `no_payer_key` and spends nothing. Name the token by `token_address` when you can: a ticker is not a key, and this subgraph holds several tokens called WETH. With neither address nor ticker it returns the most recently priced tokens, filtered to those that actually carry a price. Runs OUTSIDE the enclave.

list_venues

List the venues this Signer can sign trades for. Returns the venue id, asset class (perp / spot / margin), and auth scheme (hmac / eip712 / ed25519). Read-only static manifest — does NOT need the Signer gateway to be reachable. Call this first to discover what's signable.

get_attestation

Fetch the Signer enclave's AWS Nitro attestation document with a FRESH NONCE and verify it locally, with no dependencies and no trust in this tool's own summary. Five named checks are returned and any of them can fail: the document decodes as a COSE_Sign1 (document_readable), the nonce inside it is the one just sent (nonce_echoed), its root certificate is the pinned AWS Nitro root (root_pinned), the certificate chain leads to that root (chain_verified), and the hardware signature covers these exact bytes (signature_verified). PCR0/PCR1/PCR2 are read out of the SIGNED bytes, not from a field beside them. WHAT THIS DOES NOT ESTABLISH: that PCR0 corresponds to the published source — rebuild the image from the public clone and compare, or query the on-chain PCR0 registry; and nothing about any past signature, since an attestation speaks about the code that answered this request. If any check is false, treat the document as no evidence rather than weak evidence.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Signer MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "namixai-signer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@usenami/signer-mcp"
      ],
      "env": {
        "SIGNER_GATEWAY_URL": "YOUR_SIGNER_GATEWAY_URL_HERE",
        "SIGNER_API_TOKEN": "YOUR_SIGNER_API_TOKEN_HERE",
        "SIGNER_FETCH_TIMEOUT_MS": "YOUR_SIGNER_FETCH_TIMEOUT_MS_HERE"
      }
    }
  }
}

Koreanpulse Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "whdrnr2583-cmd-koreanpulse": {
      "command": "uvx",
      "args": [
        "koreanpulse"
      ]
    }
  }
}

Frequently Asked Questions

Signer MCP is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Koreanpulse belongs to Finance & Fintech using local stdio subprocess. Select Signer MCP when you need capabilities focused on finance & fintech and Koreanpulse when you require tools for finance & fintech.

More alternatives to Signer MCP More alternatives to Koreanpulse Finance & Fintech category hub