MCP servers › ai.cleartape › clear-tape
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
ai.cleartape/clear-tape
Free trading calculators, trading-system rules, a glossary and lesson search. No market data. — the publisher's description
Summary
ai.cleartape/clear-tape is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 11 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Tools
- 11
- Described as changing data
- 0 of 11 toolsAI-classified
- Mainly works on
- nothing outside itself: it only answers questionsAI-classified
- Topic
- finance-and-paymentsAI-classified
- Last tested
- 2026-10-23
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-10-14 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-14 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-22
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-14).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.
None of its 11 tools are described as changing anything.
“Position size from the stop: how many shares to buy (or short) so that a stop-out loses a set percentage of the account.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 4 required
accountnumberrequired“Account size in USD.”riskPctnumberrequired“Risk per trade, percent of the account (1 = 1%).”entrynumberrequired“Entry price per share in USD.”stopnumberrequired“Stop price per share in USD.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- calculate_risk_rewardcalculates or converts
“Risk/reward ratio of a planned trade, the win rate it needs to break even, and (optionally) an exit expressed as an R multiple.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 3 required
entrynumberrequired“Entry price per share in USD.”stopnumberrequired“Stop price per share in USD; not equal to the entry.”targetnumberrequired“Target price per share in USD, on the other side of the entry from the stop.”exitnumber“Optional: an actual or planned exit price in USD, returned as an R multiple.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- calculate_expectancycalculates or converts
“Expectancy per trade, per 100 trades, payoff ratio, break-even win rate and profit factor from a win rate and average win and loss.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 3 required
winRatenumberrequired“Win rate in percent (40 = 40%).”avgWinnumberrequired“Average winning trade as a positive amount, in USD or in R.”avgLossnumberrequired“Average losing trade as a positive amount, in the same unit as avgWin.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- calculate_atr_stopcalculates or converts
“A volatility (ATR) stop: entry minus (long) or plus (short) a multiple of the average true range.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 2 required
entrynumberrequired“Entry price per share in USD.”atrnumber“Average true range in USD (e.g.”rangesarray“Alternative to atr: 5 to 500 recent daily ranges (high minus low) in USD; their average stands in for the ATR.”multiplenumberrequired“ATR multiple for the stop distance, commonly 1.5 to 3.”sidestring“Trade direction: "long" (default) or "short".”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- calculate_drawdown_recoverycalculates or converts
“The gain needed to recover from a drawdown and, optionally, how many losing trades in a row at a fixed risk per trade cause it.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
lossnumberrequired“Drawdown in percent of the account (20 = 20%).”riskPctnumber“Optional: risk per trade in percent of the account.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- calculate_kelly_criterioncalculates or converts
“Full and fractional Kelly risk per trade from a win rate and payoff ratio, with the edge per 1R and the break-even win rate.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 3 required
winRatenumberrequired“Win rate in percent.”payoffnumberrequired“Payoff ratio: average win divided by average loss (2 = winners twice the size of losers).”fractionnumberrequired“Share of full Kelly to use, in percent: 25 = quarter Kelly, 50 = half, 100 = full.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
“The cost of one round trip (commissions, bid-ask spread, slippage) in USD, in R, as a share of the target move and of the position, and over a year of trades.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
9 inputs, 6 required
entrynumberrequired“Entry price per share in USD.”stopnumberrequired“Stop price per share in USD; not equal to the entry.”targetnumber“Optional: target price per share in USD, on the other side of the entry from the stop.”sharesnumberrequired“Number of shares.”commissionnumberrequired“Commission per order (each side) in USD; 0 if none.”spreadnumberrequired“Bid-ask spread per share in USD (paid once per round trip, half on each side).”slippagenumberrequired“Slippage per share per side in USD.”tradesnumber“Optional: round trips per year, for the annual cost.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- calculate_losing_streakcalculates or converts
“The exact probability of at least one losing streak of a given length over a number of independent trades, the expected longest streak and the streak 95% of sequences stay within.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 3 required
winRatenumberrequired“Win rate in percent.”tradesintegerrequired“Number of trades, a whole number from 1 to 2000.”streakintegerrequired“Losing streak length to test, a whole number no larger than trades.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- get_trading_system_rulesreads or searches
“Without id: lists Clear Tape's eleven preset trading systems (trend, breakout, momentum and volume) with their style, holding period and one-line entry, stop and exit.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
idstring“The system to describe; leave out to list them all.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- lookup_glossary_termreads or searches
“Looks up a trading term in Clear Tape's bilingual (English and Simplified Chinese) glossary of about 70 terms, such as "R multiple", "ATR", "drawdown" or "止损".”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
termstringrequired“The term to look up, in English or Chinese.”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
- search_learningreads or searches
“Searches Clear Tape's free trading education by keyword: the Learn articles, the Academy lessons, the trading-strategy pages and the calculators, in English or Chinese.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
querystringrequired“Keywords, e.g.”limitinteger“Most results to return (1 to 20, default 8).”langstring“Language of the returned text: "en" (default) or "zh" (Simplified Chinese).”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 11 tools
- Says what it returns
- 100% of 11 tools
- States limits, defaults or errors
- 100% of 9 tools
- Items covered per tool
- 4.0 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 47
- Tools with a description
- 100% of 11
- Typical description length
- 374 characters
The tool set
Counted from the listing
- Tools
- 11
- Size of the list
- about 3,708 tokens for an agent to load (characters ÷ 4)
- Naming
- 11 of 11 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 11 of 11 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://app.cleartape.ai/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"clear-tape": {
"url": "https://app.cleartape.ai/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"clear-tape": {
"type": "http",
"url": "https://app.cleartape.ai/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"clear-tape","type":"http","url":"https://app.cleartape.ai/mcp"}'Claude Code
claude mcp add --transport http clear-tape https://app.cleartape.ai/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://app.cleartape.ai/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint app.cleartape.ai/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about ai.cleartape/clear-tape
Answered from the data aboveDoes ai.cleartape/clear-tape need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has ai.cleartape/clear-tape been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.
What can ai.cleartape/clear-tape do?
It lists 11 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.
Can ai.cleartape/clear-tape change or delete data?
None of its 11 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.mnemox-ai/tradememory-protocolalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.YichengYang-Ethan/oracle3Oracle3 prediction-market arbitrage checksalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.DeHor-Labs/mcp-fiscal-brasilMCP Fiscal Brasilalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.nirholas/threews-pumpfunthree.ws pump.fun MCPalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.nirholas/pumpfun-solana-mcppump.fun Solana Dataalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.longsizhuo/openinvestopenInvestalso has tools that calculates or converts, reads or searchescompare with this one
Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,402 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 11 tools, 0 resources, 0 prompts.
- 5,001 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “ai.cleartape/clear-tape: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/ai.cleartape/clear-tape
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/ai.cleartape/clear-tape)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology