Pine Script v6 Documentation
PYPI · PINESCRIPT-MCP · 3 COMPONENTS · SCANNED SEP 20
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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 3 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 125 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 1121 tokens (~70/item across 16 items; 14 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: two runs of the same published version returned different tool surfaces, so we cannot tell a change in the package from a difference in our own sandbox run.Unverified
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Pine Script v6 Documentation MCP server?
Pine Script v6 Documentation runs locally as a PyPI package, launched with uvx pinescript-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pinescript-mcp
claude mcp add paulieb89-pinescript-mcp -- uvx pinescript-mcp
{
"mcpServers": {
"paulieb89-pinescript-mcp": {
"command": "uvx",
"args": [
"pinescript-mcp"
]
}
}
} {
"servers": {
"paulieb89-pinescript-mcp": {
"command": "uvx",
"args": [
"pinescript-mcp"
]
}
}
} codex mcp add paulieb89-pinescript-mcp -- uvx pinescript-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"paulieb89-pinescript-mcp": {
"type": "local",
"command": [
"uvx",
"pinescript-mcp"
],
"enabled": true
}
}
} openclaw mcp add paulieb89-pinescript-mcp --command uvx --arg pinescript-mcp
mcp_servers:
paulieb89-pinescript-mcp:
command: "uvx"
args: ["pinescript-mcp"] {
"McpServers": {
"paulieb89-pinescript-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"pinescript-mcp"
]
}
}
} assistant mcp add paulieb89-pinescript-mcp -t stdio -c uvx -a pinescript-mcp
{
"mcpServers": {
"paulieb89-pinescript-mcp": {
"command": "uvx",
"args": [
"pinescript-mcp"
]
}
}
} 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.
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Sept 26 −12
- Stability: 0.90 → unverified ▼ security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 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.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed pypi/pinescript-mcp@0.6.17
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
edit_and_lint Edit And Lint ~108
Apply line edits to a previously linted script and re-lint. Use after lint_script() returns issues. Send only the changed lines instead of the full script — saves tokens on fix-and-re-lint cycles.
| Name | Type | Req | Description |
|---|---|---|---|
| edits | array | yes | List of line edits. Each specifies a 1-based line number, the old text expected on that line, and the new replacement text. |
| script_id | string | yes | The script_id returned by a previous lint_script() call. |
No output schema declared.
No examples provided.
get_doc Get Doc ~124
Read a specific Pine Script v6 documentation file. For large files (ta.md, strategy.md, collections.md, drawing.md, general.md) prefer list_sections() + get_section() to avoid loading 1000-2800 line files into context.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum characters to return. Use 30000 for large files to avoid token limits. |
| offset | integer | – | Character offset to start reading from (default: 0) |
| path | string | yes | Relative path to the documentation file (e.g., "reference/functions/ta.md") |
No output schema declared.
No examples provided.
get_functions Get Functions ~77
Get valid Pine Script v6 functions, optionally filtered by namespace. Use before writing Pine Script to see which functions exist. For checking a single function name, use validate_function() instead.
| 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 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 |
No output schema declared.
No examples provided.
get_section Get Section ~108
Get a specific section from a documentation file by its header. Use after list_sections() shows available headers, or after resolve_topic() / search_docs() identifies the relevant file.
| 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 header (default: True) |
| path | string | yes | Documentation file path (e.g., "reference/functions/strategy.md") |
No output schema declared.
No examples provided.
lint_script Lint Script ~61
Lint Pine Script for syntax and style issues. Static analysis checking syntax (ANTLR4), style patterns, and undeclared identifiers. Requires authorization on HTTP (free for local STDIO clients).
| Name | Type | Req | Description |
|---|---|---|---|
| script | string | yes | The Pine Script code to lint. |
No output schema declared.
No examples provided.
list_docs List Docs ~68
List all available Pine Script v6 documentation files with descriptions. Returns files organised by category with descriptions. For small files use get_doc(path). For large files (ta.md, strategy.md, collections.md, drawing.md, general.md) use list_sections(path) then get_section(path, header).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_prompts 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.
No output schema declared.
No examples provided.
list_resources List Resources ~49
List all available resources and resource templates. Returns JSON with resource metadata. Static resources have a 'uri' field, while templates have a 'uri_template' field with placeholders like {name}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sections List Sections ~78
List all section headers in a doc file. Use before get_section() to find the right header. Especially useful for large files like ta.md, strategy.md, collections.md, drawing.md, general.md which have 50-115 sections each.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Documentation file path (e.g., "reference/functions/ta.md") |
No output schema declared.
No examples provided.
read_resource Read Resource ~70
Read a resource by its URI. For static resources, provide the exact URI. For templated resources, provide the URI with template parameters filled in. Returns the resource content as a string. Binary content is base64-encoded.
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | The URI of the resource to read |
No output schema declared.
No examples provided.
resolve_topic Resolve Topic ~94
Fast lookup for exact Pine Script API terms and known concepts. Use for exact function names and Pine Script vocabulary (e.g., "ta.rsi", "strategy.entry", "repainting", "request.security"). For natural language questions, read the docs://manifest resource for routing guidance, then use get_doc() or list_sections() + get_section().
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Exact Pine Script term or known concept keyword. |
No output schema declared.
No examples provided.
search_docs Search Docs ~76
Search Pine Script v6 documentation and return matching sections. Finds sections containing the query and returns previews with get_section() call hints so you can read the full content.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Maximum sections to return (default: 5) |
| query | string | yes | Exact string to search for (case-insensitive). |
No output schema declared.
No examples provided.
validate_function Validate Function ~47
Check if a Pine Script v6 function name is valid.
| Name | Type | Req | Description |
|---|---|---|---|
| fn_name | string | yes | Function name to validate (e.g., "ta.sma", "strategy.entry", "plot") |
No output schema declared.
No examples provided.
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 PyPI package (pinescript-mcp).
Is the Pine Script v6 Documentation MCP server safe to use?
Pine Script v6 Documentation scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 14 tools: list_docs, list_sections, get_doc, get_section, search_docs, and 9 more. Their descriptions and schemas cost roughly 1,054 tokens of context every time the server is loaded.
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.