Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tapeline

REMOTE · API.TAPELINE.IO · SCANNED SEP 22

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

Available components

+4 this week 81 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 594 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

remote · api.tapeline.io

# add to Claude Code
claude mcp add --transport http io-tapeline-tapeline 'https://api.tapeline.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-tapeline-tapeline": {
      "url": "https://api.tapeline.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-tapeline-tapeline": {
      "type": "http",
      "url": "https://api.tapeline.io/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add io-tapeline-tapeline --url 'https://api.tapeline.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-tapeline-tapeline:
    url: "https://api.tapeline.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-tapeline-tapeline": {
      "Transport": "http",
      "Url": "https://api.tapeline.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-tapeline-tapeline -t streamable-http -u 'https://api.tapeline.io/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1
    • 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 security
  • 19 Sept 26 0
    • 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 security
  • 18 Sept 26 +1
    • 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 security
    • Schema quality: 92 → 111 functional
  • 16 Sept 26 +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.

  • 14 Sept 26 0
    • 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 security
    • Schema quality: 77 → 92 functional
  • 13 Sept 26 +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.

  • 11 Sept 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Probed https://api.tapeline.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.tapeline.io CN=YE1,O=Let's Encrypt,C=US 31 Aug 2026 29 Nov 2026 ECDSA 256 ECDSA-SHA384 6f5fb271ee01b643d1abb4bb15a0935e9d4
SANs: api.tapeline.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.tapeline.io. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
tapeline.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.tapeline.io/mcp Verified 200
http (plaintext) http://api.tapeline.io/mcp HTTPS enforced 301 https://api.tapeline.io/mcp
MCP tools · 5 exposed · ~318 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_daily_picks ~60

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.

NameTypeReqDescription
limitintegerHow many rows (1-10, default 10).

No output schema declared.

No examples provided.

get_ticker_record ~56

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.

NameTypeReqDescription
symbolstringyesUS ticker symbol, e.g. NVDA

No output schema declared.

No examples provided.

get_ticker_score ~91

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.

NameTypeReqDescription
symbolstringyesUS ticker symbol, e.g. NVDA or BRK.B

No output schema declared.

No examples provided.

get_track_record ~64

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_tickers ~47

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

NameTypeReqDescription
querystringyesSymbol or company name.

No output schema declared.

No examples provided.

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.