Tapeline

io.tapelinev1.0.0Updated Oct 9, 2026

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

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Lets an assistant scan stocks, score them and check picks through a remote stock screener with a claimed public track record.

What you can do
Tapeline is a remote stock screener exposed over streamable HTTP. According to the registry description it lets an assistant scan stocks, score them and check picks, and it advertises a public, verifiable track record. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to run stock screens, compare scored candidates or review past picks inside a conversation. It suits research and idea generation rather than order execution, since no trading or account actions are described. Skip it if you need documented tool names or a self-hosted screener.
Requirements
A remote MCP endpoint at over streamable HTTP. No packages, environment variables, headers or authentication are declared, so no local runtime or API key appears to be needed; network access to the endpoint is required.
Before you install
The description claims a public, verifiable track record, but no details of the scoring method, data sources or update frequency are given, so treat any scores or picks as unverified. No credentials, payments, wallet keys or write actions are declared, but the remote endpoint receives whatever queries you send it.

Installation

In SourceWeft

  1. Open Tapeline in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.tapeline%2Ftapeline/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.