Pine Script v6 Documentation
REMOTE · PINESCRIPT-MCP.FLY.DEV · 3 COMPONENTS · SCANNED AUG 3
Pine Script v6 documentation lookup, function validation, and linting for AI code generation
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · pinescript-mcp.fly.dev
claude mcp add --transport http paulieb89-pinescript-mcp https://pinescript-mcp.fly.dev/mcp
[mcp_servers.paulieb89-pinescript-mcp] url = "https://pinescript-mcp.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"paulieb89-pinescript-mcp": {
"type": "remote",
"url": "https://pinescript-mcp.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add paulieb89-pinescript-mcp --url https://pinescript-mcp.fly.dev/mcp --transport streamable-http
mcp_servers:
paulieb89-pinescript-mcp:
url: "https://pinescript-mcp.fly.dev/mcp" {
"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.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 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 66
First indexed and scored.
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 3 Aug 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=YE2,O=Let's Encrypt,C=US | 21 Jun 2026 | 19 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 503153e73302e4a0c89ebb83c4a741aac04 |
| SANs: *.fly.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
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 |
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 |
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.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Maximum characters to return. Use 30000 for large files. 0 = no limit. |
| offset | integer | — | Character offset to start reading from. |
| path | string | yes | Relative 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.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | — | Filter 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.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | — | — | Optional arguments for the prompt |
| name | string | yes | The name of the prompt to get |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | Header text to find (e.g., 'strategy.exit()' or '## strategy.exit()'). |
| include_children | boolean | — | Include nested subsections under the matched header. |
| path | string | yes | Documentation 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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Documentation 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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Exact Pine Script term or known concept keyword (e.g., 'ta.rsi', 'strategy.entry', 'repainting'). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | — | Maximum sections to return. |
| query | string | yes | Search 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.
| Name | Type | Req | Description |
|---|---|---|---|
| fn_name | string | yes | Function name to validate (e.g., 'ta.sma', 'strategy.entry', 'plot'). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.