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.

Pine Script v6 Documentation

REMOTE · PINESCRIPT-MCP.FLY.DEV · 3 COMPONENTS · SCANNED SEP 20

Pine Script v6 documentation lookup, function validation, and linting for AI code generation

0 this week 80 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 Security57
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1134 tokens (~94/item across 12 items; 10 tools + 2 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
  • Structured output schemas are declared (40% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Pine Script v6 Documentation MCP server?

Pine Script v6 Documentation is a hosted endpoint at https://pinescript-mcp.fly.dev/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 · pinescript-mcp.fly.dev

# add to Claude Code
claude mcp add --transport http paulieb89-pinescript-mcp 'https://pinescript-mcp.fly.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "paulieb89-pinescript-mcp": {
      "url": "https://pinescript-mcp.fly.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "paulieb89-pinescript-mcp": {
      "type": "http",
      "url": "https://pinescript-mcp.fly.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.paulieb89-pinescript-mcp]
url = "https://pinescript-mcp.fly.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "paulieb89-pinescript-mcp": {
      "type": "remote",
      "url": "https://pinescript-mcp.fly.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add paulieb89-pinescript-mcp --url 'https://pinescript-mcp.fly.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  paulieb89-pinescript-mcp:
    url: "https://pinescript-mcp.fly.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "paulieb89-pinescript-mcp": {
      "Transport": "http",
      "Url": "https://pinescript-mcp.fly.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add paulieb89-pinescript-mcp -t streamable-http -u 'https://pinescript-mcp.fly.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "paulieb89-pinescript-mcp": {
      "type": "http",
      "url": "https://pinescript-mcp.fly.dev/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.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

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 20 Sept 2026 · Probed https://pinescript-mcp.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 21 Aug 2026 19 Nov 2026 ECDSA 256 ECDSA-SHA384 688c4daf5300c51e0a5c1f6837a3a67a868
SANs: *.fly.dev
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 pinescript-mcp.fly.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
fly.dev. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pinescript-mcp.fly.dev/mcp Verified 200
http (plaintext) http://pinescript-mcp.fly.dev/mcp HTTPS enforced 301 https://pinescript-mcp.fly.dev/mcp
MCP tools · 10 exposed · ~1,067 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_doc ~167

USE WHEN reading the full content of a Pine Script v6 documentation file. Returns the file content; when limit is set, a header shows the char range and offset to continue reading. AFTER calling this tool, use offset=<end> to continue if the header indicates more content is available. For large files (ta.md, strategy.md, collections.md, drawing.md, general.md), prefer list_sections() + get_section() instead. Data sourced from bundled Pine Script v6 documentation.

NameTypeReqDescription
limitintegerMaximum characters to return. Use 30000 for large files. 0 = no limit.
offsetintegerCharacter offset to start reading from.
pathstringyesRelative path to the documentation file (e.g., 'reference/functions/ta.md').

No output schema declared.

No examples provided.

get_functions ~114

USE WHEN browsing valid Pine Script v6 functions, optionally filtered to a namespace. Returns function names grouped by namespace (e.g. ta.*, strategy.*) or filtered to the requested namespace. AFTER calling this tool, call validate_function(fn_name) to check a specific name, or get_section() to read its documentation. Data sourced from bundled pine_v6_functions.json.

NameTypeReqDescription
namespacestringFilter by namespace (e.g., 'ta', 'strategy', 'request'). Empty string returns all functions grouped by namespace.

No output schema declared.

No examples provided.

get_prompt ~66

Get a prompt by name with optional arguments. Returns the rendered prompt as JSON with a messages array. Arguments should be provided as a dict mapping argument names to values.

NameTypeReqDescription
argumentsOptional arguments for the prompt
namestringyesThe name of the prompt to get
NameTypeReqDescription
resultstringyes

No examples provided.

get_section ~150

USE WHEN reading a specific named section from a Pine Script v6 documentation file. Returns the section content from the matched header to the next same-level header, with file path and line range. AFTER calling this tool, call list_sections(path) if the header was not found, or get_section() again with a child header for a narrower subsection. Data sourced from bundled Pine Script v6 documentation.

NameTypeReqDescription
headerstringyesHeader text to find (e.g., 'strategy.exit()' or '## strategy.exit()').
include_childrenbooleanInclude nested subsections under the matched header.
pathstringyesDocumentation file path (e.g., 'reference/functions/strategy.md').

No output schema declared.

No examples provided.

list_docs ~89

USE WHEN discovering what Pine Script v6 documentation is available. Returns a categorised list of doc file paths with one-line descriptions. AFTER calling this tool, call get_doc(path) for small files or list_sections(path) then get_section(path, header) for large files (ta.md, strategy.md, collections.md, drawing.md, general.md). Data sourced from bundled Pine Script v6 documentation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_prompts ~28

List all available prompts. Returns JSON with prompt metadata including name, description, and optional arguments.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

list_sections ~89

USE WHEN navigating a large documentation file before reading a specific section. Returns a newline-separated list of # and ## headers (### excluded) in the file. AFTER calling this tool, call get_section(path, header) with a header from this list. Data sourced from bundled Pine Script v6 documentation.

NameTypeReqDescription
pathstringyesDocumentation file path (e.g., 'reference/functions/ta.md').

No output schema declared.

No examples provided.

resolve_topic ~130

USE WHEN looking up an exact Pine Script API term or known concept keyword. Returns the best-matching doc paths with matched keywords and a retrieval suggestion (get_doc or list_sections + get_section). AFTER calling this tool, follow the suggestion: call get_doc() for small files or list_sections() + get_section() for large files. For natural language questions use search_docs() instead. Data sourced from bundled TOPIC_MAP and doc file content scan.

NameTypeReqDescription
querystringyesExact Pine Script term or known concept keyword (e.g., 'ta.rsi', 'strategy.entry', 'repainting').
NameTypeReqDescription
resultstringyes

No examples provided.

search_docs ~115

USE WHEN finding documentation sections that match specific terms across all Pine Script v6 docs. Returns up to max_results sections ranked by match count, each with a preview and a get_section() call hint. AFTER calling this tool, call get_section(file, header) for each result you want to read in full. Data sourced from bundled Pine Script v6 documentation.

NameTypeReqDescription
max_resultsintegerMaximum sections to return.
querystringyesSearch terms (case-insensitive). Multi-word queries match sections containing ALL terms.

No output schema declared.

No examples provided.

validate_function ~119

USE WHEN confirming a Pine Script v6 function name is valid before using it in code. Returns a valid/invalid verdict with namespace suggestions or known replacement hints (e.g. ta.adx → ta.dmi, security → request.security). AFTER calling this tool, call get_functions(namespace) to list all valid functions in the relevant namespace if the function is invalid. Data sourced from bundled pine_v6_functions.json.

NameTypeReqDescription
fn_namestringyesFunction name to validate (e.g., 'ta.sma', 'strategy.entry', 'plot').
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the Pine Script v6 Documentation MCP server?

Pine Script v6 Documentation is an MCP server listed in the public MCP registry as io.github.paulieb89/pinescript-mcp. Pine Script v6 documentation lookup, function validation, and linting for AI code generation. This page covers its hosted endpoint (https://pinescript-mcp.fly.dev/mcp).

Is the Pine Script v6 Documentation MCP server safe to use?

Pine Script v6 Documentation scores 80 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 Pine Script v6 Documentation MCP server expose?

Pine Script v6 Documentation exposes 10 tools: list_docs, list_sections, get_doc, get_section, search_docs, and 5 more. Their descriptions and schemas cost roughly 1,067 tokens of context every time the server is loaded.

Does the Pine Script v6 Documentation MCP server require authentication?

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

Is the Pine Script v6 Documentation MCP server still maintained?

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