# Pine Script v6 Documentation (remote · pinescript-mcp.fly.dev)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `pinescript-mcp.fly.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp.md), [page](https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp)
- remote · `pinescript-mcp.fly.dev`: 23/100, [markdown](https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp-2.md), [page](https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp-2)
- pypi · `pinescript-mcp`: 21/100, [markdown](https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp-3.md), [page](https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp-3)

## Channel facts

- Endpoint: `https://pinescript-mcp.fly.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.17`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1134 tokens (~94/item across 12 items; 10 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (40% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http paulieb89-pinescript-mcp https://pinescript-mcp.fly.dev/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add paulieb89-pinescript-mcp --url https://pinescript-mcp.fly.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  paulieb89-pinescript-mcp:
    url: "https://pinescript-mcp.fly.dev/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +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.

### 2026-08-01 (score 68, +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.

### 2026-07-31 (score 67, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +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.

### 2026-07-28 (score 67, +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.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (10)

### `list_docs` (~89 tokens)

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.

### `list_sections` (~89 tokens)

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.

Input parameters:

- `path` (string, required): Documentation file path (e.g., 'reference/functions/ta.md').

### `get_doc` (~167 tokens)

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.

Input parameters:

- `limit` (integer): Maximum characters to return. Use 30000 for large files. 0 = no limit.
- `offset` (integer): Character offset to start reading from.
- `path` (string, required): Relative path to the documentation file (e.g., 'reference/functions/ta.md').

### `get_section` (~150 tokens)

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.

Input parameters:

- `header` (string, required): Header text to find (e.g., 'strategy.exit()' or '## strategy.exit()').
- `include_children` (boolean): Include nested subsections under the matched header.
- `path` (string, required): Documentation file path (e.g., 'reference/functions/strategy.md').

### `search_docs` (~115 tokens)

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.

Input parameters:

- `max_results` (integer): Maximum sections to return.
- `query` (string, required): Search terms (case-insensitive). Multi-word queries match sections containing ALL terms.

### `get_functions` (~114 tokens)

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.

Input parameters:

- `namespace` (string): Filter by namespace (e.g., 'ta', 'strategy', 'request'). Empty string returns all functions grouped by namespace.

### `validate_function` (~119 tokens)

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.

Input parameters:

- `fn_name` (string, required): Function name to validate (e.g., 'ta.sma', 'strategy.entry', 'plot').

Output parameters:

- `result` (string)

### `resolve_topic` (~130 tokens)

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.

Input parameters:

- `query` (string, required): Exact Pine Script term or known concept keyword (e.g., 'ta.rsi', 'strategy.entry', 'repainting').

Output parameters:

- `result` (string)

### `list_prompts` (~28 tokens)

List all available prompts.

Returns JSON with prompt metadata including name, description,
and optional arguments.

Output parameters:

- `result` (string)

### `get_prompt` (~66 tokens)

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.

Input parameters:

- `arguments`: Optional arguments for the prompt
- `name` (string, required): The name of the prompt to get

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 67
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://pinescript-mcp.fly.dev/mcp
- Repository: https://github.com/paulieb89/pinescript-mcp
- Website: https://bouch.dev/
- Changelog RSS feed: https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/paulieb89-pinescript-mcp/pinescript-mcp