CleanSignal MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_commodity_regimeA | Returns de-noised real-time commodity/FX market regime and physical hedging actions (Copper, Gold, Crude, CNH, Lithium, Aluminum, SCFI Freight). |
| filter_social_signalsC | De-noises raw social/X streams: Strips crypto shills and bot spam, isolating high-purity vendor complaint and buying intent signals. |
| scan_b2b_buying_intentB | Scans real-time verified B2B buying signals, active tender RFQs, and GEO AI visibility ranking (industrial_machinery, logistics, saas, medical_devices, dtc_ecommerce). |
| buy_cleansignal_creditsB | Instant $0.99 USD top-up link for 100 metered CleanSignal API calls via Polar.sh. |
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 4 tools
The four tools mostly target distinct jobs: commodity regime lookup, social-signal filtering, B2B intent scanning, and credit purchase. The main overlap risk is between filter_social_signals and scan_b2b_buying_intent, since both relate to extracting buying signals from external data, but their descriptions differentiate raw social-stream de-noising from verified B2B/tender scanning.
All tool names follow a consistent snake_case verb_noun pattern: get_, filter_, scan_, and buy_. The convention is predictable and readable throughout.
Four tools is on the thin side but appropriate for a focused signal/intelligence API with three data products plus billing. Each tool has a clear role, though the surface could feel slightly underpowered if the service grows.
The tool set covers the main signal products and a credit top-up, but there is no tool to check remaining credits, account usage, or subscription status. It also lacks history/time-series access for commodity regimes or signal streams, which are notable gaps for a metered data service.