Frostyz (@frostyz) on X

What it claims

OSWiki, which runs an MCP server for NFT collection data, has released a separate signer that executes trades on that data from a chat client. Supported actions are buy, list, transfer and make offers, on Ethereum and ApeChain, across the collections the OSWiki MCP covers. The post is an announcement with no performance, fee or usage figures.

How it works

The post describes two components with a trust boundary between them. The OSWiki MCP server supplies collection data. The signer runs on the user's own machine and holds the private key. Every proposed action is checked and shown as a preview. User-set limits apply. Any action that sends NFTs or funds always requires explicit approval.

flowchart LR
  subgraph Remote
    MCP[OSWiki MCP server]
  end
  subgraph Local machine
    Chat[Chat client] --> Signer[Local signer + key]
    Signer --> Check{Within limits?<br/>Moves NFTs/funds?}
    Check -->|needs approval| User[User approves / rejects]
  end
  MCP -->|collection data| Chat
  User -->|approved| Chain[Ethereum / ApeChain]

The post does not say whether reads, listings or offers inside the limits skip the approval step. It guarantees approval only for outgoing NFTs and funds.

How to use it

The setup command as it appears in the fetched text:

npx -y @oswikixyz/[email protected] setup

The npm scope is @oswikixyz. However, the package name and pinned version were mangled into [email protected] by email-address obfuscation on the scraped page, so the exact package name cannot be recovered from this text. Get it from the docs at mcp.oswiki.xyz/#trading, which the post says covers "everything else." Setup generates a new wallet.

Limits

• The author recommends using a fresh wallet, never a main wallet, and testing only with small funds. This is effectively a statement that the tool is experimental.
• The page does not say:
• which MCP clients are supported
• which limits can be configured
• whether the signer is open source or audited
• what fees apply
• what licence it uses
• npx -y downloads and runs the package without a confirmation prompt, and that package will hold a funded private key. Confirm the exact package name and its publisher from the docs before running it. Do not rely on the obfuscated string above.