io.github.bevanding/signaldaemon

Registre officiel Finance et paiements

Narrative & signal intelligence for AI agents: crypto/AI/macro convergence & divergence.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http signaldaemon 'https://api.signaldaemon.com/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "signaldaemon": {
            "type": "http",
            "url": "https://api.signaldaemon.com/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. signaldaemon
  2. What it is (and isn't)
  3. Quickstart
  4. Connect from your agent (MCP)
  5. Local stdio bridge
  6. Interface
  7. License

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.

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 isIt is not
Cross-source narrative convergence + capital-vs-narrative divergenceA price/market-data API (use CoinGecko etc. for that)
Coverage across ~14 crypto/AI/macro domainsA raw news firehose
Fails safe — "no coverage" over hallucinationA database you query for facts
For agents (API/MCP), token-cost-agnostic, quality-firstA human-facing dashboard

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) · vet_trade(symbol, side) — all annotated readOnlyHint. vet_trade is the pre-trade gate: hand it a candidate trade and it returns a narrative-layer stance (support/caution/contradict/no_signal) with reason + confidence — it vets, it does not recommend.

Local stdio bridge

For clients that don't support remote MCP, this repo ships a thin stdio bridge (mcp_server.py) exposing the same three 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.py

Or with Docker:

docker build -t signaldaemon-mcp . && \
docker run -i -e SIGNALDAEMON_API_KEY=cns_... signaldaemon-mcp

The 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. </content>

Questions fréquentes

Qu'est-ce que io.github.bevanding/signaldaemon ?

Narrative & signal intelligence for AI agents: crypto/AI/macro convergence & divergence.

Comment installer io.github.bevanding/signaldaemon ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http signaldaemon 'https://api.signaldaemon.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.bevanding/signaldaemon ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.bevanding/signaldaemon est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.bevanding/signaldaemon ?

Il est publié par bevanding. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.