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