Signal8 MCP

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

1. 1

   Install / connect

   Publisher instructions

   Publisher provides npx stdio and JSON with SIGNAL8_API_KEY; npm -g alone is not client registration.

   publisher documented install or connect · Publisher instructions

   npx @signal8ai/mcp

   Copy
2. 2

   Configure / authenticate

   MCP100 setup guide

   Required SIGNAl8 key spelling: SIGNAL8_API_KEY. Authentication must be configured before account data access.

   Environment variables referenced by this route (respect the alternatives above): SIGNAL8_API_KEY

   {
     "mcpServers": {
       "signal8": {
         "args": [
           "-y",
           "@signal8ai/mcp"
         ],
         "command": "npx",
         "env": {
           "SIGNAL8_API_KEY": "YOUR_SIGNAL8_API_KEY"
         }
       }
     }
   }

   Copy
3. 3

   Check connection

   Suggested check

   User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.

4. 4

   Remove / uninstall / revoke

   MCP100 setup guide

   Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.

   Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.

   Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.