accueil / serveurs / Recherche & Web / io.github.paulieb89/pinescript-mcp
io.github.paulieb89/pinescript-mcp
serveur MCP (Model Context Protocol) · pinescript-docs 3.3.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.paulieb89/pinescript-mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.paulieb89/pinescript-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 10 outils
- get_doc≈ 272 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.
Paramètres, retour & exemple (3)
Paramètrespath· string · requis
Relative path to the documentation file (e.g., 'reference/functions/ta.md').limit· integer · optionnel
Maximum characters to return. Use 30000 for large files. 0 = no limit.offset· integer · optionnel
Character offset to start reading from.
Exemple d'appel{"name": "get_doc", "arguments": {"path": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_functions≈ 192 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.
Paramètres, retour & exemple (1)
Paramètresnamespace· string · optionnel
Filter by namespace (e.g., 'ta', 'strategy', 'request'). Empty string returns all functions grouped by namespace.
Exemple d'appel{"name": "get_functions", "arguments": {"namespace": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_prompt≈ 176 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.
Paramètres, retour & exemple (2)
Paramètresname· string · requis
The name of the prompt to getarguments· ? · optionnel
Optional arguments for the prompt
Exemple d'appel{"name": "get_prompt", "arguments": {"name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - get_section≈ 252 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.
Paramètres, retour & exemple (3)
Paramètrespath· string · requis
Documentation file path (e.g., 'reference/functions/strategy.md').header· string · requis
Header text to find (e.g., 'strategy.exit()' or '## strategy.exit()').include_children· boolean · optionnel
Include nested subsections under the matched header.
Exemple d'appel{"name": "get_section", "arguments": {"path": "texte", "header": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_docs≈ 151 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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_docs", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_prompts≈ 96 tokens
List all available prompts. Returns JSON with prompt metadata including name, description, and optional arguments.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_prompts", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - list_sections≈ 162 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.
Paramètres, retour & exemple (1)
Paramètrespath· string · requis
Documentation file path (e.g., 'reference/functions/ta.md').
Exemple d'appel{"name": "list_sections", "arguments": {"path": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - resolve_topic≈ 248 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.
Paramètres, retour & exemple (1)
Paramètresquery· string · requis
Exact Pine Script term or known concept keyword (e.g., 'ta.rsi', 'strategy.entry', 'repainting').
Exemple d'appel{"name": "resolve_topic", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - search_docs≈ 218 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.
Paramètres, retour & exemple (2)
Paramètresquery· string · requis
Search terms (case-insensitive). Multi-word queries match sections containing ALL terms.max_results· integer · optionnel
Maximum sections to return.
Exemple d'appel{"name": "search_docs", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - validate_function≈ 232 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.
Paramètres, retour & exemple (1)
Paramètresfn_name· string · requis
Function name to validate (e.g., 'ta.sma', 'strategy.entry', 'plot').
Exemple d'appel{"name": "validate_function", "arguments": {"fn_name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».