Frontier Signal
Query verified AI data-broker buyer programmes and demand signals.
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 »).
claude mcp add --transport http frontier-signal 'https://mcp.velab.org/mcp'
{
"mcpServers": {
"frontier-signal": {
"type": "http",
"url": "https://mcp.velab.org/mcp"
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Frontier Signal MCP
Query verified AI data-broker buyer programmes and demand signals from VE Lab Frontier Signal.
Public and read-only. No API keys, no login, no gated watchlist. Tools never invent hit counts.
Live surfaces:
- Remote MCP (Streamable HTTP):
https://mcp.velab.org/mcp(preferred custom domain after deploy;*.workers.devis the v1 fallback) - Privacy policy: docs/privacy.md · hosted at
/privacyon the same Worker - Product: velab.org/frontier-signal
- Public weekly brief: velab.org/frontier-signal/brief
- Gated watchlist (not exposed here): velab.org/frontier-signal/watchlist
What it does
One verb: query verified buyer programmes and demand signals.
| Tool | Title | Returns |
|---|---|---|
list_buyer_programmes | List buyer programmes | Sources from a baseline, optional filters type, status, category. Fields: name, url, band, referral, categories, status, notes. |
get_programme | Get a programme | One source by exact or fuzzy name. |
demand_mix | Demand mix | Hot categories ([category, mention_count]) for latest or a given observed date. |
latest_brief | Latest public brief | Public brief markdown for latest or a date. Gated sections are stripped. |
deltas | Baseline deltas | deltas_vs_prev (and recheck if present) for latest or a date. |
list_observed_dates | List observed dates | Baseline dates (and public brief dates) in this checkout. |
Every tool sets title and readOnlyHint: true (Claude Connectors / ChatGPT Apps requirement). Mention counts on demand_mix are heuristics recorded on the baseline, not search-engine hit counts.
Remote HTTPS MCP
This is the path for Official MCP Registry remotes, Claude custom connectors, and ChatGPT Apps.
| Transport | Streamable HTTP |
| Endpoint | https://mcp.velab.org/mcp |
| Privacy | https://mcp.velab.org/privacy |
| Auth | None (public read-only) |
| Worker | worker/ (Cloudflare Workers + createMcpHandler) |
If mcp.velab.org is not yet attached, the Worker also publishes https://frontier-signal-mcp.<your-subdomain>.workers.dev/mcp. After wrangler deploy, Wrangler prints the live URL — use that until the custom domain is on.
Hit the remote URL
# Health
curl -sS https://mcp.velab.org/health
# MCP initialize (Streamable HTTP)
curl -sS https://mcp.velab.org/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
Cursor (remote):
{
"mcpServers": {
"frontier-signal": {
"url": "https://mcp.velab.org/mcp"
}
}
}
Claude custom connector — test steps
- Open claude.ai → Settings → Connectors (or Custom connectors).
- Add custom connector.
- Name:
Frontier Signal. - URL:
https://mcp.velab.org/mcp(or theworkers.devURL from deploy). - Authentication: No authentication.
- Save and enable the connector for a chat.
- Ask: Using Frontier Signal, list observed dates and then the demand mix. Do not invent extra mention counts.
- Confirm Claude calls
list_observed_datesthendemand_mix. Latest cut should be2026-11-03in this checkout; Software / code mention count is 12 (heuristic, not a hit count). - Optional: Look up Lazarus →
get_programmereturns Turing (Lazarus). Show the public brief →latest_briefmust not include gated watchlist copy.
ChatGPT Apps / Connectors
- Create or edit the app / custom GPT.
- Add an MCP server / connector with URL
https://mcp.velab.org/mcp. - No OAuth client ID or secret.
- Smoke the same prompts as the Claude steps above.
- Point the app’s privacy URL at
https://mcp.velab.org/privacy.
Listing materials (Registry, Claude, ChatGPT)
| Field | Copy |
|---|---|
| One-liner | Query verified AI data-broker buyer programmes and demand signals. |
| Description | Frontier Signal is VE Lab’s public, read-only MCP for daily baselines of AI data-buyer programmes, demand mix, and public briefs. No login. Does not invent hit counts or expose the gated watchlist. |
| Support | hello@velab.org (also alet@velab.org) |
| Privacy policy | https://mcp.velab.org/privacy |
| Homepage | https://velab.org/frontier-signal/ |
| MCP URL | https://mcp.velab.org/mcp |
| Icon / brand | VE Lab / Frontier Signal — velab.org |
server.json lists the Streamable HTTP remote plus the local PyPI/stdio package. Registry publish is still a later step (mcp-publisher).
Local stdio (Cursor / Claude Desktop)
Requires Python 3.11+ and uv.
git clone https://github.com/collectivewinca/frontier-signal-mcp
cd frontier-signal-mcp
uv sync
uv run python -m frontier_signal_mcp
Equivalent: uv run frontier-signal-mcp.
Cursor (~/.cursor/mcp.json or project .cursor/mcp.json)
{
"mcpServers": {
"frontier-signal": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/to/frontier-signal-mcp",
"run",
"python",
"-m",
"frontier_signal_mcp"
]
}
}
}
Claude Desktop (claude_desktop_config.json)
Same command / args as Cursor, under mcpServers.frontier-signal.
Deploy the Worker
Cloudflare account used by VE Lab Workers: aa6789c67f992fd0b9f5933e86e11184 (set as account_id in worker/wrangler.jsonc).
cd worker
npm ci
npm test
npx wrangler login # or: export CLOUDFLARE_API_TOKEN=...
npx wrangler deploy # prints https://frontier-signal-mcp.<subdomain>.workers.dev
This environment has no Cloudflare API token, so production is not published from the PR agent. Config is worker/wrangler.jsonc (Wrangler 4; equivalent to wrangler.toml). After login, the commands above are the whole deploy.
Or from repo root: bash scripts/deploy.sh.
Attach the preferred host after the Worker exists and the velab.org zone is in this account:
cd worker
npx wrangler deploy --x-route-zones --domain mcp.velab.org
Then confirm:
https://mcp.velab.org/mcp— Streamable HTTPhttps://mcp.velab.org/privacy— this policyhttps://mcp.velab.org/health—{ ok: true, ... }
Local Worker: cd worker && npm run dev then http://127.0.0.1:8787/mcp.
Dropping in a newer daily baseline: add files under data/, run npm run embed-data in worker/, redeploy. The Python stdio server picks up new files on the next tool call without a rebuild.
Data (offline from the repo)
data/baselines/YYYY-MM-DD.json
data/briefs/YYYY-MM-DD.md
Sample cuts: 2026-10-30, 2026-11-02, 2026-11-03 (plus the public brief for 2026-11-03).
- Copy the day’s JSON to
data/baselines/YYYY-MM-DD.json(observedmust match the filename). - Copy only the public brief to
data/briefs/YYYY-MM-DD.md. Stop before any gated / watchlist-login heading. - Stdio: restart the MCP client if needed. Remote:
cd worker && npm run embed-data && npx wrangler deploy.
Override the Python data directory with FRONTIER_SIGNAL_DATA_DIR=/path/to/data.
Privacy
Full policy: docs/privacy.md (rendered at /privacy on the Worker).
- Public verified data only. No PII, no credentials, no API keys.
- No gated watchlist content.
latest_briefstrips gated headings. - No invented hit counts.
demand_mixreturns thehotarray as recorded. - No auth is correct for this product.
Distribution intent (10-store)
- Official MCP Registry —
server.jsonnameio.github.collectivewinca/frontier-signal-mcp, withremotes(Streamable HTTP) andpackages(stdio). - ChatGPT Apps and Claude Connectors (custom connector URL above).
- Then Google Connected Apps, Grok, Cursor Marketplace, Meta Muse, Copilot Agent Store, AgentExchange, AWS Marketplace.
This repo is not yet submitted to those stores.
Development
uv sync
uv run pytest
cd worker && npm ci && npm test
See AGENTS.md for invariants and CHANGELOG.md for releases.
License
Questions fréquentes
Qu'est-ce que Frontier Signal ?
Query verified AI data-broker buyer programmes and demand signals.
Comment installer Frontier Signal ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http frontier-signal 'https://mcp.velab.org/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Frontier Signal ?
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.
Frontier Signal est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient Frontier Signal ?
Il est publié par collectivewinca. 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.