@baselab-me/signals-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_TX_KEY | No | Wallet private key that signs and submits the on-chain coin creation transaction. Needs ETH on Base. Used for headless (fully automatic) mode. | |
| SIGNALS_API_URL | No | The URL of the signals platform API. | https://signals.baselab.me |
| AGENT_PAYMENT_KEY | No | Wallet private key that pays x402 USDC fees (approx. $0.05 per signal, $0.03 per upload). Needs USDC on Base. Used for headless (fully automatic) mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: create_signal_coin prepares transaction data, submit_transaction sends it on-chain, and upload_signal_media handles media uploads. There is no overlap or ambiguity between these three functions.
All tools follow a consistent verb_noun pattern with snake_case: create_signal_coin, submit_transaction, and upload_signal_media. The naming is predictable and readable throughout.
Three tools are reasonable for a focused server handling signal coin creation and posting on Base chain. It might feel slightly thin, but each tool has a clear role, making it well-scoped for the apparent purpose.
The tools cover the core workflow of creating and posting signal coins, including media upload. A minor gap is the lack of tools for managing or retrieving existing signal coins, but agents can likely work with the provided create-and-submit flow.