Sato Hub
MCP server

@usenami/signer-mcp

mcp:npm:@usenami/signer-mcp · v0.8.0 · sha256:8263732613f0 · as of 2026-11-10

Does it take your key?
traced
Yes — it reads private-key material. Local signing is what a wallet does; question 2 says whether the key leaves.
Our static read of the published artifact found it.
Does your key leave?
no evidence
Not yet run — we have not run this version with planted test keys.
No evidence line on file for this question yet.
Can it move funds on its own?
declared
Unknown — we could not read what it exposes.
The project says so — README, config, env list or tool description.
What changed?
no evidence
First profile of this subject — nothing to compare yet.
No evidence line on file for this question yet.

Is this your project? Respond →Dispute this reading

Hosts contacted

HostWhenRoleEvidence
api.hyperliquid-testnet.xyzcodeothertraced
api.hyperliquid.xyzcodeothertraced
arbitrum-one-rpc.publicnode.comcoderpctraced
aws-nitro-enclaves.amazonaws.comcodeothertraced
ethereum-rpc.publicnode.comcoderpctraced
gateway.thegraph.comcodeothertraced
signer-demo.usenami.iocodevendortraced
testnet.gateway.thegraph.comcoderpctraced
Evidence (14 lines)
  • tracedT-key-read2026-11-10

    Reads process.env.X402_PRIVATE_KEY.

    dist/graph/fetch.js:242

  • tracedT-hosts2026-11-10

    api.hyperliquid-testnet.xyz appears in shipped code (other).

    dist/hyperliquid.js

  • tracedT-hosts2026-11-10

    api.hyperliquid.xyz appears in shipped code (other).

    dist/hyperliquid.js

  • tracedT-hosts2026-11-10

    arbitrum-one-rpc.publicnode.com appears in shipped code (rpc).

    dist/graph/chain.js

  • tracedT-hosts2026-11-10

    aws-nitro-enclaves.amazonaws.com appears in shipped code (other).

    dist/attestation.js

  • tracedT-hosts2026-11-10

    ethereum-rpc.publicnode.com appears in shipped code (rpc).

    dist/graph/chain.js

  • tracedT-hosts2026-11-10

    gateway.thegraph.com appears in shipped code (other).

    dist/graph/fetch.js

  • tracedT-hosts2026-11-10

    signer-demo.usenami.io appears in shipped code (vendor).

    dist/index.js

  • tracedT-hosts2026-11-10

    testnet.gateway.thegraph.com appears in shipped code (rpc).

    dist/graph/fetch.js

  • tracedT-key-named2026-11-10

    The shipped code names X402_PRIVATE_KEY in a message to the user.

    dist/index.js

  • declaredD-env-key2026-11-10

    Setup names SIGNER_API_TOKEN — bearer token issued by usenami.io, requir as something to provide.

    deploy_spec.requires

  • declaredD-env-key2026-11-10

    Setup names X402_PRIVATE_KEY as something to provide.

    @usenami/signer-mcp@0.8.0/README.md

  • declaredD-doc-funds2026-11-10

    The project's own text says it carries out transactions: "Status: v0 (alpha), invite-based pilot. Venue manifest, attestation, account read, place/cancel order, and a two-leg hedge. ⚠️ Assume orders are real. Which venue and network your orders hit is decided by the policy bou…"

    @usenami/signer-mcp@0.8.0/README.md (line 7)

  • declaredD-doc-funds2026-11-10

    The project's own text says it carries out transactions: "5. Once you have a token and trust the attestation, you can place a first order — knowingly."

    @usenami/signer-mcp@0.8.0/README.md (line 54)

Limits

  • The observed lane has not run on this version: not yet run on this version
  • Traced analysis follows flows inside one module and one hop across a relative import; a longer chain is not followed.
  • The observed lane has not run on this version.
  • No tool inventory was available, so fund actions were not read.

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".

sato.custody/v1 · custody-3

Maintain this project? Respond to this reading

Loading sign-in…