tell: buying signals with receipts MCP server
io.github.karank2512/tell-mcp·v0.1.0Ask tell which accounts are in market and why, with a receipt URL behind every claim.
0 stars157 downloads/wk
Reviews
Write oneNobody has reviewed tell: buying signals with receipts yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
tell: buying signals with receipts tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
coverageOne row per requested domain, in request order.
eventsContributions and counted postings for ``domain`` (the v0 stand-in for raw events).
explainThe full company object, plus ``account_page``; ``monitored: false`` on a 404.
in_marketThe in-market accounts of a public watchlist, highest score first.
watch_accountsv0: the prefilled intake link; v1 will create the watchlist through the API.
Public scan report
scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How tell: buying signals with receipts compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 157
- more than 71% of 12,191 servers with a package
What its tools let an agent do: 5 read
Install tell: buying signals with receipts in Claude Code, Cursor or VS Code
claude mcp add tell-mcp -- uvx tell-mcp
What the publisher says
From the tell: buying signals with receipts repository's README, as published. We do not edit it. Read it on GitHub
tell
Explainable buying signals from public job boards, SEC filings and news: every score is a list of dated events, each linked to the posting or filing behind it.
<!-- 30-second GIF: an account page with its receipts visible. Not recorded yet; see docs/launch/README.md ("Recording the README GIF"). Add the image here when it exists; do not commit a placeholder image. -->
The 30-second demo GIF (an account page with receipts) is still to be recorded. Recording steps are in docs/launch/README.md.
Why it exists
I built a tool to watch companies' job boards for my own job search. Around week two I noticed that hiring velocity is a buying signal: a company that opens several sales-engineer roles in a week is about to buy sales-engineering tools. The postings are public, timestamped and free, and so are the SEC Form D filings a company files when it raises money. tell reads those public sources, resolves them to a company domain, and turns them into scores that decompose into named, dated events with receipts.
What it does, and what it does not
It does:
- Poll public job-board JSON (Greenhouse, Lever, Ashby, SmartRecruiters), SEC EDGAR filings (Form D, 8-K, S-1) and news feeds, once per source at polite rates.
- Resolve every event to a company domain (rules R1-R6, with a review queue for the unsure cases) and classify postings into ten role families.
- Compute hiring velocity (new postings in 7 days against a four-week baseline, with repost and stale-posting handling) and an additive score with per-signal exponential decay.
- Publish static pages, JSON, a Slack digest and a CSV in which every row links to its receipt.
- Send a Slack nudge to a watchlist's own webhook on the ingest run that scores a threshold crossing, with the receipts (method, ADR 0036). Each nudge says whether the account is worth an enrichment credit: yes, skip or hold, with the reason (ADR 0038).
- Write the score, a receipt note and an optional task onto the company in the customer's own HubSpot (docs/crm/hubspot.md, ADR 0037). A watchlist with a HubSpot token in its tell-private record gets that push on each enrich verdict, before its nudge (ADR 0040).
- Collect ratings: with a feedback form configured, rating links on nudges, account pages and the CSV open it prefilled (docs/intake/feedback-form.md). A nightly tell intake feedback-sync turns the responses into feedback labels (ADR 0039).
- Publish a weekly digest of Form D filings: every original Form D filed in the last two complete weeks by a company with an account page and a trusted link to the issuer, newest first, with the offering and sold amounts as filed. No customer's private list can be read off it. Each row's receipt is its filing on sec.gov (page, api/v0/form-d-filings.json, method, ADR 0044).
It does not:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
tell: buying signals with receipts: common questions
- Is tell: buying signals with receipts MCP server safe?
- Mostly: it is graded B (83/100). Read the tell: buying signals with receipts safety report
- How do I install tell: buying signals with receipts?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does tell: buying signals with receipts need an API key?
- Yes. The registry entry asks for
TELL_API_KEY. - Is tell: buying signals with receipts maintained?
- The last commit was 12 days ago (2026-10-23). The latest release is v0.1.0.
- How does tell: buying signals with receipts compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.