Is Usenami Signer MCP open source?

Yes. Usenami Signer MCP is open source under the MIT license; the repository is https://github.com/namixai/signer-mcp. Checked as of 2026-10-21.

Which chains does Usenami Signer MCP support?

Sato Hub has no confirmed chain list for Usenami Signer MCP as of 2026-10-21; treat chain support as unknown.

Is Usenami Signer MCP still maintained?

The most recent code activity Sato Hub observed was on 2026-10-01 (last commit 2026-10-01, last release 2026-06-09), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.

Is Usenami Signer MCP verified on Sato Hub?

Sato Hub holds one earned check for Usenami Signer MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 69 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.

Security Tool

Usenami Signer MCP

MCP server that signs CEX/DEX orders inside an attested AWS Nitro Enclave so keys never touch the agent process.

Sato Score69

EarlyUnverifiedActive · 20d ago

Usenami Signer MCP is an open-source security tool, with last code activity on 2026-10-01 (Active). Latest release on 2026-06-09. Sato Score 69/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install Usenami Signer MCP →

Last commit Oct 1, 2026 · Last release Jun 9, 2026 · ★ 2

Listed from github.com/namixai/signer-mcp on 2026-07-19. Install: reproduced by Sato Hub on 2026-10-19. Evidence →

Website ↗GitHub ↗

Next step

Watch Usenami Signer MCP

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp

Run Sato Hub Preflight on namixai/signer-mcp before I use it.

Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Signer MCP exposes order-signing for exchanges like Binance, OKX, and Asterdex as MCP tools, but the private key lives inside an AWS Nitro Enclave with attested PCR0 rather than in the agent's runtime memory. Trading-agent builders use it to reduce the blast radius of prompt injection or a compromised agent process, since the LLM never sees or can exfiltrate the signing key — it can only request signatures for specific orders.

Sato Score

69/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness: 35/35
Code transparency: 17/20
Interface verifiability: 8/10
Docs & demo: 0/10
Listing transparency & provenance: 6/15
Independent verification: 3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

View verification & embed badge →History →How the Sato Score works

Sato Check

v0.8.0 · as of 2026-09-29

Does it take your key?: Reads a key
Does your key leave?: Not yet run
Can it move funds on its own?: Unknown

Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from github.com/namixai/signer-mcp on 2026-07-19. Install: reproduced by Sato Hub on 2026-10-19.

Claim	Value	Evidence	Source	Checked
Chains supported	not stated	self-reported	github.com/namixai/signer-mcp	as of 2026-10-21
Verification status	Unverified — not independently reviewed	self-reported	github.com/namixai/signer-mcp	as of 2026-10-21
Recent activity	last release 2026-06-09 · last commit 2026-10-01	observed	github.com/namixai/signer-mcp	2026-10-21
Install works	reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour	✓ reproduced	raw.githubusercontent.com	2026-10-19
Website answers	answered (HTTP 200)	observed	github.com/namixai/signer-mcp	2026-10-21
Daily check record	90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history	observed	—	2026-10-20
Takes your key	reads private-key material	traced	satohub.ai	2026-09-29
Key leaves the machine	not yet run with planted test keysthe sandbox lane has not run on this version	observed	satohub.ai	not dated
Moves funds on its own	unknown — could not read what it exposes	traced	satohub.ai	2026-09-29
Sato Score	69/100 (Medium)how open, active and verifiable — not a safety or quality grade	computed	satohub.ai	2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Oct 19, 2026

Runtime: Node.js (npm package, MCP server; also an ElizaOS plugin)

npm install @usenami/signer-mcp
{"mcpServers": {"signer": {"command": "npx", "args": ["-y", "@usenami/signer-mcp"], "env": {"SIGNER_GATEWAY_URL": "https://signer.usenami.io", "SIGNER_API_TOKEN": "sk_live_..."}}}}

You supply: SIGNER_API_TOKEN — bearer token issued by usenami.io, required for paid tools; high-risk if exposed since it authorizes order signing (docs state the private key itself stays in an AWS Nitro Enclave, never loaded locally), SIGNER_GATEWAY_URL — optional, defaults to https://signer.usenami.io

Add to Cursor Add to VS Code

claude mcp add satohub-namixai-signer-mcp -- npx -y @usenami/signer-mcp

A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-10-19. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

100%of 91 checks since 2026-07-23 succeeded

Currently responding for 91 days

Succeeded: 91
Failed: 0
Their error: 0
Unattributed: 0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded

100%

7-day rolling; unattributable days are gaps · 30/30 days

Tools listed

fewer than 2 points—

from the server's own tools/list · 0/30 days

Sato Score

as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains: Unknown
Agent types: MCP server
Open source: Yes
Last checked: 2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#key-custody#tee#trading#signing

Where Usenami Signer MCP fits

Trading Identity & Verification

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Usenami Signer MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

Oct 19, 2026
Verified: deploy spec
Sep 26, 2026
Edited: entity class, resource type
Jul 24, 2026
Sato Hub began tracking this listing
Jul 19, 2026
Listed on Sato Hub

Compared with

Alternatives to Usenami Signer MCP →

Appears in

Security tools an agent can call, scored →

Related Resources

Coinbase AgentKit

Active

Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain

Active★ 1.3k

Hyperliquid

Active

VenueVerified

Onchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.

MultichainHyperliquid

Recent★ 506▸ Jun 2023

Model Context Protocol (MCP)

Active

Standard

Anthropic's open standard for connecting AI systems to external tools and data sources.

Unknown

Active★ 9.5k

Reference

QuestionsWhat people ask about this pageShowHide

Cite this pagePlain text, APA or BibTeXShowHide

Cite this page

Sato Hub. "Usenami Signer MCP — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/namixai-signer-mcp

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Usenami Signer MCP

Next step

Watch Usenami Signer MCP

Check it from your agent

Your project?

Overview

Sato Score

Sato Check

Evidence — listed vs checked · what the words mean

Install — reproduced in a container Oct 19, 2026

Observed record — 91 daily checks since 2026-07-23

Last 30 days — to 2026-10-21, one point per UTC day

Details

Marketplace Signals

Where Usenami Signer MCP fits

Listing History

Compared with

Appears in

Related Resources

Coinbase AgentKit

Hyperliquid

Model Context Protocol (MCP)

Questions people ask about Usenami Signer MCP

Cite this page

Join the Sato Hub Briefing