_ registry / mcp http-sse · checked 1h ago

pinescript-docs

https://pinescript-mcp.fly.dev

Registry code: 681aa82037246dfb

api record

For skills that work with these tools see https://bouch.dev/products/pine-strategy-builder

endpoint
https://pinescript-mcp.fly.dev/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pinescript-docs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is pinescript-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does pinescript-docs have?
10 tools: get_doc, search_docs, validate_function, resolve_topic, get_prompt, get_section, list_sections, list_docs, ….
Is pinescript-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.8%· all time 99.8%

latency
275ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 600 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search pine script v6 documentation
  • read a pine script doc section
  • validate a pine script function name
  • list pine script functions
takes → gives
text → text
tools
10 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
3 open 7 never probed 3 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_docs reads open 4h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_functions reads open 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "namespace": {
          "type": "string",
          "default": "",
          "description": "Filter by namespace (e.g., 'ta', 'strategy', 'request'). Empty string returns all functions grouped by namespace."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • list_prompts reads open 15h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_doc reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Relative path to the documentation file (e.g., 'reference/functions/ta.md')."
        },
        "limit": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Maximum characters to return. Use 30000 for large files. 0 = no limit."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Character offset to start reading from."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • search_docs reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Search terms (case-insensitive). Multi-word queries match sections containing ALL terms."
        },
        "max_results": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum sections to return."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • validate_function reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "fn_name"
      ],
      "properties": {
        "fn_name": {
          "type": "string",
          "minLength": 1,
          "description": "Function name to validate (e.g., 'ta.sma', 'strategy.entry', 'plot')."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • resolve_topic reads unknown 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Exact Pine Script term or known concept keyword (e.g., 'ta.rsi', 'strategy.entry', 'repainting')."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_prompt reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The name of the prompt to get"
        },
        "arguments": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "default": null,
          "description": "Optional arguments for the prompt"
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • get_section reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "path",
        "header"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Documentation file path (e.g., 'reference/functions/strategy.md')."
        },
        "header": {
          "type": "string",
          "description": "Header text to find (e.g., 'strategy.exit()' or '## strategy.exit()')."
        },
        "include_children": {
          "type": "boolean",
          "default": true,
          "description": "Include nested subsections under the matched header."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • list_sections reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Documentation file path (e.g., 'reference/functions/ta.md')."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 681aa82037246dfb.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/681aa82037246dfb/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/681aa82037246dfb/badge.svg)](https://brick.blue/agent/681aa82037246dfb?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.