tell: buying signals with receipts

io.github.karank2512由 GitHub 帳號 karank2512 發布v0.1.0更新於 Oct 24, 2026

Ask tell 可說明哪些帳戶正在進入市場以及原因，每項結論背後都有憑證 URL。

AI 翻譯由 AI 模型根據下方的原文描述翻譯，可能有誤。

原文描述

Ask tell which accounts are in market and why, with a receipt URL behind every claim.

發布方自己的服務：tell.dev

已驗證STDIO僅桌面

服務詳細資訊

識別碼: io.github.karank2512/tell-mcp
傳輸: STDIO
執行環境: Desktop only
信任: Verified
發布於: Oct 20, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 karank2512。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.karank2512%2Ftell-mcp.svg)](https://sourceweft.com/mcp/io.github.karank2512%2Ftell-mcp?utm_source=readme&utm_medium=badge)

概覽

tell: buying signals with receipts 的本機 MCP 服務；無需登入；STDIO。

暫無 AI 概覽：以下資訊來自註冊中心條目和服務本身。

安裝

在 SourceWeft 中

開啟儀表板中的 tell: buying signals with receipts，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照儲存庫中的啟動說明。

README

tell-mcp

MCP server for tell, the open-source buying-signals pipeline. It lets Claude Desktop, Cursor or any MCP client ask which accounts are in market and why, with a receipt URL behind every signal (a job board, an SEC Form D filing, a news item). It runs locally over stdio and reads tell's public static JSON: no key, no account.

Quickstart

Claude Desktop (claude_desktop_config.json) or Cursor (~/.cursor/mcp.json):

json

{  "mcpServers": {    "tell": {      "command": "uvx",      "args": ["tell-mcp"],      "env": { "TELL_BASE_URL": "https://karank2512.github.io/tell-data" }    }  }}

{  "mcpServers": {    "tell": {      "command": "uvx",      "args": ["tell-mcp"],      "env": { "TELL_BASE_URL": "https://karank2512.github.io/tell-data" }    }  }}

Restart the app and ask: "Which of these ten domains are in market and why?"

Tools

Tool	Input	Output
`watch_accounts`	`domains`, `watchlist`	v0: the intake form link prefilled with the domains; the watchlist appears after the nightly job
`in_market`	`watchlist`, `since_days` (7), `min_score` (6.0), `families`	`[{domain, name, score, heat, top_contributions[:3]}]`, highest score first
`explain`	`domain`	Every contribution with its receipt URL, plus "why not higher" (signals that decayed in the last 30 days)
`events`	`domain`, `since`, `types`	Contributions and counted postings, newest first, at most 200, each with a URL
`coverage`	`domains`	Per domain: job board, SEC CIK, news feed, or "not monitored"

Prompt why_now_email(domain): the two-sentence "why now" for an outreach email, built from the top two signals with their receipt URLs. Tool descriptions ask the agent to cite the url of every signal it mentions and to call explain before writing outreach copy.

Configuration

Variable	Default	Meaning
`TELL_BASE_URL`	`https://karank2512.github.io/tell-data`	The static site to read
`TELL_API_KEY`, `TELL_API_URL`	unset	Both set: read companies and watchlists from the FastAPI service with a Bearer key
`TELL_INTAKE_FORM_URL`	unset	Intake form for `watch_accounts` (default: the repo's "Watch these domains" issue form)

v0 limitations

watch_accounts returns a prefilled link; it does not create the watchlist.
in_market reads public watchlists only (api/v0/watchlists/{slug}.json).
events has no raw event endpoint to read: it lists the scored contributions and the counted postings behind them.
Data refreshes with each ingest run (four a day); a domain quiet for 180 days has no file and reads as "not monitored".

When the FastAPI service is deployed, setting TELL_API_KEY and TELL_API_URL switches company and watchlist reads to it without any other change.

Full docs: docs/mcp.md. License: Apache-2.0.

來源：packages/tell-mcp/README.md，提交 cee1756