# tell: buying signals with receipts (pypi · tell-mcp)

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

- Trust score: 71/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `tell-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/karank2512-tell-mcp/tell-mcp.md), [page](https://verifymcp.io/servers/karank2512-tell-mcp/tell-mcp)

## Channel facts

- Registry: `pypi`
- Package: `tell-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to karank2512/tell-ai).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 751 tokens (~150/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the tell: buying signals with receipts MCP server?

tell: buying signals with receipts runs locally as a PyPI package, launched with uvx tell-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add karank2512-tell-mcp -- uvx tell-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "karank2512-tell-mcp": {
      "command": "uvx",
      "args": [
        "tell-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "karank2512-tell-mcp": {
      "command": "uvx",
      "args": [
        "tell-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add karank2512-tell-mcp -- uvx tell-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "karank2512-tell-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "tell-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add karank2512-tell-mcp --command uvx --arg tell-mcp
```

### Hermes

```yaml
mcp_servers:
  karank2512-tell-mcp:
    command: "uvx"
    args: ["tell-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "karank2512-tell-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "tell-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add karank2512-tell-mcp -t stdio -c uvx -a tell-mcp
```

### Other

```json
{
  "mcpServers": {
    "karank2512-tell-mcp": {
      "command": "uvx",
      "args": [
        "tell-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-04 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 85, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 70, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-01 (score 84, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 69, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 83, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `watch_accounts` (~125 tokens)

Ask tell to start watching company domains for buying signals, as a named watchlist. v0 cannot create watchlists directly: this returns the intake form link prefilled with the domains (at most 50 per request). Give the user the link to submit; the watchlist appears after the next scheduled (nightly) job picks the request up. Cite the `url` of every contribution, posting or signal you mention, and call `explain` for an account before writing any outreach copy about it.

Input parameters:

- `domains` (array, required)
- `watchlist` (string, required)

### `in_market` (~162 tokens)

Accounts on a public tell watchlist that are in market now: score at least min_score (default 6.0) and a top signal within since_days (default 7) of the data date. families narrows to hiring_velocity in those role families (for example sales, engineering). Returns [{domain, name, score, heat, top_contributions[:3]}] sorted by score; heat is the 0-100 percentile within the watchlist. Cite the `url` of every contribution, posting or signal you mention, and call `explain` for an account before writing any outreach copy about it.

Input parameters:

- `families`
- `min_score` (number)
- `since_days` (integer)
- `watchlist` (string, required)

Output parameters:

- `result` (array)

### `explain` (~106 tokens)

Why an account scores what it does: every contribution with its type, decayed value, date, summary and receipt url (hiring_velocity includes the counted postings), plus why_not_higher, the signals that decayed to zero in the last 30 days. Use it before writing outreach copy. Cite the `url` of every contribution, posting or signal you mention, and call `explain` for an account before writing any outreach copy about it.

Input parameters:

- `domain` (string, required)

### `events` (~152 tokens)

Dated events behind an account's signals, newest first, at most 200, each with its url: the scored contributions and the counted job postings. since (YYYY-MM-DD) keeps events on or after that date; types filters by signal type (hiring_velocity, funding, leadership, launch, expansion, tech_adoption) or by kind (posting). v0 limitation: no raw event endpoint exists yet, so events tell saw but did not score are not listed. Cite the `url` of every contribution, posting or signal you mention, and call `explain` for an account before writing any outreach copy about it.

Input parameters:

- `domain` (string, required)
- `since`
- `types`

### `coverage` (~104 tokens)

What tell can see for each domain: has_board (a supported job board), has_cik (an SEC CIK for Form D filings), has_feed (news), or status 'not monitored' when tell has no data, which is the honest answer: do not guess about those. Cite the `url` of every contribution, posting or signal you mention, and call `explain` for an account before writing any outreach copy about it.

Input parameters:

- `domains` (array, required)

Output parameters:

- `result` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/karank2512-tell-mcp/tell-mcp#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 86
- 2026-11-03: 85
- 2026-11-02: 70
- 2026-11-01: 84
- 2026-10-31: 69
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 68
- 2026-10-27: 67
- 2026-10-26: 67
- 2026-10-25: 66
- 2026-10-24: 66
- 2026-10-23: 65
- 2026-10-22: 65
- 2026-10-21: 64
- 2026-10-20: 64

## Common questions

### What is the tell: buying signals with receipts MCP server?

tell: buying signals with receipts is an MCP server listed in the public MCP registry as io.github.karank2512/tell-mcp. Ask tell which accounts are in market and why, with a receipt URL behind every claim. This page covers its PyPI package (tell-mcp).

### Is the tell: buying signals with receipts MCP server safe to use?

tell: buying signals with receipts scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the tell: buying signals with receipts MCP server expose?

tell: buying signals with receipts exposes 5 tools: watch_accounts, in_market, explain, events, coverage. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

### Is the tell: buying signals with receipts MCP server still maintained?

tell: buying signals with receipts is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the tell: buying signals with receipts MCP server under?

tell: buying signals with receipts declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/tell-mcp/
- Socket report: https://socket.dev/pypi/package/tell-mcp
- Repository: https://github.com/karank2512/tell-ai
- Website: https://github.com/karank2512/tell-ai/blob/main/docs/mcp.md
- Changelog RSS feed: https://verifymcp.io/servers/karank2512-tell-mcp/tell-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/karank2512-tell-mcp/tell-mcp.json
- HTML version of this page: https://verifymcp.io/servers/karank2512-tell-mcp/tell-mcp