# Tapeline (remote · api.tapeline.io)

Transparent stock screener with a public, verifiable track record. Scan, score, and check picks.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `api.tapeline.io`: 81/100 (this document), [markdown](https://verifymcp.io/servers/io-tapeline-tapeline/api.md), [page](https://verifymcp.io/servers/io-tapeline-tapeline/api)

## Channel facts

- Endpoint: `https://api.tapeline.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 594 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Tapeline MCP server?

Tapeline is a hosted endpoint at https://api.tapeline.io/mcp, so there is nothing to install locally. 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 --transport http io-tapeline-tapeline 'https://api.tapeline.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-tapeline-tapeline": {
      "url": "https://api.tapeline.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-tapeline-tapeline": {
      "type": "http",
      "url": "https://api.tapeline.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-tapeline-tapeline]
url = "https://api.tapeline.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tapeline-tapeline": {
      "type": "remote",
      "url": "https://api.tapeline.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-tapeline-tapeline --url 'https://api.tapeline.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-tapeline-tapeline:
    url: "https://api.tapeline.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-tapeline-tapeline": {
      "Transport": "http",
      "Url": "https://api.tapeline.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-tapeline-tapeline -t streamable-http -u 'https://api.tapeline.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-tapeline-tapeline": {
      "type": "http",
      "url": "https://api.tapeline.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-22 (score 81, +1)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 80, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_ticker_score” rewrote its description, which is the text the model reads

### 2026-09-19 (score 79, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_ticker_score” rewrote its description, which is the text the model reads

### 2026-09-18 (score 79, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_ticker_score” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 92 → 111

### 2026-09-16 (score 78, +1)

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

### 2026-09-14 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_track_record” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 77 → 92

### 2026-09-13 (score 77, +1)

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

### 2026-09-11 (score 76, +1)

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

## MCP tools (5)

### `get_ticker_score` (~91 tokens)

Get a ticker's Tapeline score

Tapeline's current six-factor score (0-100), signal label, confidence and one-line reason for a single US ticker. It does not return a price or a daily move. Crypto scores come from daily closes, sometimes several days old. Use when asked what Tapeline says about a specific stock.

Input parameters:

- `symbol` (string, required): US ticker symbol, e.g. NVDA or BRK.B

### `get_daily_picks` (~60 tokens)

Get today's published top picks

Today's highest-scoring tickers as published on tapeline.io — the same rows an anonymous visitor sees, each with score, signal and the one-line reason.

Input parameters:

- `limit` (integer): How many rows (1-10, default 10).

### `get_track_record` (~64 tokens)

Get the published track record

Tapeline's public record (losses kept, corrections dated): how many picks have been logged, over how many sessions, the share that beat SPY the next session, and median alpha — with the sample-size qualifier. Call this before stating any Tapeline performance figure.

### `get_ticker_record` (~56 tokens)

Get one ticker's pick history

Every time Tapeline published this ticker in its daily top 10 and how each of those picks resolved against SPY the next session — losses included.

Input parameters:

- `symbol` (string, required): US ticker symbol, e.g. NVDA

### `search_tickers` (~47 tokens)

Find a ticker

Look up covered tickers by symbol or company name. Use it to resolve a company name to a symbol before calling the other tools.

Input parameters:

- `query` (string, required): Symbol or company name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-tapeline-tapeline/api#diagnostics

## Score history

- 2026-09-22: 81
- 2026-09-21: 80
- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 77
- 2026-09-12: 76
- 2026-09-11: 76
- 2026-09-10: 75
- 2026-09-09: 75
- 2026-09-08: 74
- 2026-09-07: 74
- 2026-09-06: 73
- 2026-09-05: 73
- 2026-09-04: 72
- 2026-09-03: 72
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 71
- 2026-08-30: 70
- 2026-08-29: 67
- 2026-08-28: 67
- 2026-08-27: 66
- 2026-08-26: 66
- 2026-08-25: 64
- 2026-08-24: 63

## Common questions

### What is the Tapeline MCP server?

Tapeline is an MCP server listed in the public MCP registry as io.tapeline/tapeline. Transparent stock screener with a public, verifiable track record. Scan, score, and check picks. This page covers its hosted endpoint (https://api.tapeline.io/mcp).

### Is the Tapeline MCP server safe to use?

Tapeline scores 81 out of 100 on VerifyMCP. 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 Tapeline MCP server expose?

Tapeline exposes 5 tools: get_ticker_score, get_daily_picks, get_track_record, get_ticker_record, search_tickers. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.

### Does the Tapeline MCP server require authentication?

No. We connected to Tapeline without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Tapeline MCP server still maintained?

Tapeline is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.tapeline.io/mcp
- Repository: https://github.com/cham-p24/tapeline
- Website: https://tapeline.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-tapeline-tapeline/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-tapeline-tapeline/api.json
- HTML version of this page: https://verifymcp.io/servers/io-tapeline-tapeline/api