signaldaemon-mcp
Allows Hermes agents to access the same narrative intelligence tools via MCP configuration, enabling them to retrieve market narratives and clean feeds.
signaldaemon
Narrative & signal intelligence for AI agents — crypto, AI, and macro. A dumb-but-trustworthy pipe: it delivers curated narrative & signal, not raw data, and it fails safe — when it has no coverage it says so, rather than inventing. Built for machines, not human eyes.
API + MCP:
https://api.signaldaemon.comSelf-serve key:
POST /v1/request-key(no signup)
This repo is the front door — quickstart, client configs, and the interface contract. The pipeline itself (sources, scoring, curation) is not open source.
What it is (and isn't)
It is | It is not |
Cross-source narrative convergence + capital-vs-narrative divergence | A price/market-data API (use CoinGecko etc. for that) |
Coverage across ~14 crypto/AI/macro domains | A raw news firehose |
Fails safe — "no coverage" over hallucination | A database you query for facts |
For agents (API/MCP), token-cost-agnostic, quality-first | A human-facing dashboard |
Related MCP server: fathom-fyi
Quickstart
# 1 · self-serve a demo key (no signup)
KEY=$(curl -s -X POST https://api.signaldaemon.com/v1/request-key | jq -r .key)
# 2 · the day's ranked narratives + derived signals (cached, instant)
curl -s https://api.signaldaemon.com/v1/narratives \
-H "x-api-key: $KEY" -d '{"limit":8}'
# 3 · clean narrative feed for a topic
curl -s https://api.signaldaemon.com/v1/feed \
-H "x-api-key: $KEY" -d '{"query":"restaking","limit":8}'Connect from your agent (MCP)
Remote MCP over Streamable HTTP, authenticated with the x-api-key header.
# Claude Code
claude mcp add --transport http signaldaemon \
https://api.signaldaemon.com/mcp --header "x-api-key: <KEY>"# Hermes Agent — ~/.hermes/config.yaml
mcp_servers:
signaldaemon:
url: "https://api.signaldaemon.com/mcp"
headers: { x-api-key: "<KEY>" }More clients (Cursor, Cline) in examples/mcp-configs.md.
Tools: get_market_narratives(limit) · get_clean_feed(query, category, limit) —
both annotated readOnlyHint.
Local stdio bridge
For clients that don't support remote MCP, this repo ships a thin stdio
bridge (mcp_server.py) exposing the same two tools over
the hosted API. It holds no methodology — just a client.
pip install mcp
export SIGNALDAEMON_API_KEY=cns_... # https://signaldaemon.com/console
python mcp_server.pyOr with Docker:
docker build -t signaldaemon-mcp . && \
docker run -i -e SIGNALDAEMON_API_KEY=cns_... signaldaemon-mcpThe bridge starts and answers introspection (tools/list) without a key;
tool calls require one.
Interface
Endpoints and response-field contract (incl. the divergence schema) in
API.md. Field names are stable.
License
Examples and docs in this repo: MIT (see LICENSE). The signaldaemon service and pipeline are proprietary.
This server cannot be installed
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bevanding/signaldaemon'
If you have feedback or need assistance with the MCP directory API, please join our Discord server