@wkalidev/multichain-mcp
mcp:npm:@wkalidev/multichain-mcp · v1.2.1 · sha256:7ac2e370889a · as of 2026-11-10
- Does it take your key? declared
- No private-key read found in what we read of its setup and published code — the limits say how much that was.
- The project says so — README, config, env list or tool description.
- 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? no evidence
- Unknown — we could not read what it exposes.
- No evidence line on file for this question yet.
- 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
| Host | When | Role | Evidence |
|---|---|---|---|
| api.coingecko.com | code | other | traced |
| api.hiro.so | code | other | traced |
| api.lemonsqueezy.com | code | other | traced |
| basescan.org | code | other | traced |
| celoscan.io | code | other | traced |
| forno.celo.org | code | other | traced |
| mainnet.base.org | code | rpc | traced |
| wkalidev.lemonsqueezy.com | code | other | traced |
Evidence (10 lines)
- tracedT-hosts2026-11-10
api.coingecko.com appears in shipped code (other).
dist/tools/prices.js
- tracedT-hosts2026-11-10
api.hiro.so appears in shipped code (other).
dist/chains/config.js
- tracedT-hosts2026-11-10
api.lemonsqueezy.com appears in shipped code (other).
dist/license.js
- tracedT-hosts2026-11-10
basescan.org appears in shipped code (other).
dist/chains/config.js
- tracedT-hosts2026-11-10
celoscan.io appears in shipped code (other).
dist/chains/config.js
- tracedT-hosts2026-11-10
forno.celo.org appears in shipped code (other).
dist/chains/config.js
- tracedT-hosts2026-11-10
mainnet.base.org appears in shipped code (rpc).
dist/chains/config.js
- tracedT-hosts2026-11-10
wkalidev.lemonsqueezy.com appears in shipped code (other).
dist/tools/upgrade-nudge.js
- declaredD-doc-custody2026-11-10
The project's own text describes its custody model: "All write operations return unsigned transactions — your users always sign with their own wallet. Non-custodial by design."
@wkalidev/multichain-mcp@1.2.1/README.md (line 37)
- declaredD-doc-custody2026-11-10
The project's own text describes its custody model: "[@wkalidev](https://github.com/wkalidev) — author of celobank-agent (ERC-8004 AI agent, 21 MCP tools on Celo mainnet) and stacks-quest (non-custodial DeFi terminal on Stacks Bitcoin L2)."
@wkalidev/multichain-mcp@1.2.1/README.md (line 144)
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…