MTA:SA Documentation MCP Server
NPM · MTASA-DOCS-MCP
MCP server for MTA:SA documentation with intelligent search and caching
Available components
Last scanned (16 hours ago)
Scores higher than 99% of npm servers
Category Code Search and Documentation
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Luminaire1337/mtasa-docs-mcp). View diagnostics → Pass
- Clear OSI-approved license (GPL-3.0).Pass
- Actively maintained (last published 204 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
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 780 tokens (~70/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 4 Nov 2026 · Analysed npm/mtasa-docs-mcp@1.0.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Luminaire1337/mtasa-docs-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Luminaire1337/mtasa-docs-mcp/.github/workflows/release.yml@refs/tags/v1.0.3 |
| Rekor log index | 1285923952 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:307d107b9a44f404c8dd682284f2f3792cef7d3dffd8a96c668d8ca6918f0813a90cb28dc7e153935695bbd28c91fbca2f380e92a5046724738505f5c |
Background: How many MCP packages publish verified provenance →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Stale | 30 |
| 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 →
clear_cache ~46
Clear the MTA:SA documentation cache for a specific function or all functions.
| Name | Type | Req | Description |
|---|---|---|---|
| function_name | string | yes | Function name to clear cache for, or 'all' to clear everything |
No output schema declared.
No examples provided.
find_events_for_task ~105
Task-to-events matcher. Use when you need event names for handlers/triggers (e.g., resource lifecycle, player joins, marker hits). Returns ranked MTA:SA events only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of suggestions |
| side | string | – | Filter by client-side or server-side events |
| task_description | string | yes | Description of the event workflow you need (e.g., 'when player joins', 'resource start', 'on marker hit') |
No output schema declared.
No examples provided.
find_functions_for_task ~93
Task-to-functions matcher. Use this FIRST when user intent is high-level (e.g., 'vehicle dealership', 'login panel'). Returns ranked MTA:SA functions/events optimized for follow-up documentation retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of suggestions |
| task_description | string | yes | Description of what you want to accomplish (e.g., 'login system', 'spawn vehicle', 'create gui window') |
No output schema declared.
No examples provided.
get_cache_stats ~20
Get statistics about the MTA:SA documentation cache.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_function_docs ~90
Fetch authoritative docs for exactly ONE MTA:SA function/event by canonical name. Preferred over manual web browsing. For multiple names, use get_multiple_function_docs in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| function_name | string | yes | Function/event name (case-insensitive) |
| include_optional_arguments | boolean | – | Whether to include optional arguments in the parameters section |
| use_cache | boolean | – | Whether to use cached documentation |
No output schema declared.
No examples provided.
get_function_examples ~44
Get only code examples for one function/event after docs lookup. Use when writing implementation snippets and tests.
| Name | Type | Req | Description |
|---|---|---|---|
| function_name | string | yes | Function/event name (case-insensitive) |
No output schema declared.
No examples provided.
get_multiple_function_docs ~85
Batch docs retrieval for implementation phase. Provide exact function/event names (ideally from search/find tools) and get combined authoritative docs in one response.
| Name | Type | Req | Description |
|---|---|---|---|
| function_names | array | yes | Array of function/event names to fetch |
| include_examples | boolean | – | Whether to include code examples |
| include_optional_arguments | boolean | – | Whether to include optional arguments in each parameters section |
No output schema declared.
No examples provided.
list_functions_by_category ~55
Enumerate canonical function/event names in a category. Useful for discovery when query terms are vague.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The category to list functions from |
| limit | integer | – | Maximum number of results to return |
No output schema declared.
No examples provided.
recommend_doc_workflow ~77
Planner tool that tells LLMs exactly which mtasa-docs tools to call next for a given task. Use this to enforce MCP-first workflows and avoid manual wiki scraping.
| Name | Type | Req | Description |
|---|---|---|---|
| known_function_names | array | – | Function names already known in the conversation |
| task_description | string | yes | What the user wants to build or debug |
No output schema declared.
No examples provided.
search_events ~76
Event discovery tool. Search MTA:SA client/server events only (not regular functions), then chain into docs tools with exact event names.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results |
| query | string | yes | Event name or keyword to search for |
| side | string | – | Filter by client-side or server-side events |
No output schema declared.
No examples provided.
search_functions ~89
Primary discovery tool. Search MTA:SA functions and events by name or keyword before coding. Returns canonical function names with side/category so LLMs can reliably chain into docs tools.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results |
| query | string | yes | Function name or partial name to search for |
| side | string | – | Filter by client-side, server-side, or shared functions |
No output schema declared.
No examples provided.
How do I install the MTA:SA Documentation MCP Server server?
MTA:SA Documentation MCP Server runs locally as an npm package, launched with npx -y mtasa-docs-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mtasa-docs-mcp
claude mcp add luminaire1337-mtasa-docs-mcp -- npx -y mtasa-docs-mcp
What is the MTA:SA Documentation MCP Server server?
MTA:SA Documentation MCP Server is listed in the public MCP registry as io.github.Luminaire1337/mtasa-docs-mcp. MCP server for MTA:SA documentation with intelligent search and caching. This page covers its npm package (mtasa-docs-mcp).
Is the MTA:SA Documentation MCP Server server safe to use?
MTA:SA Documentation MCP Server scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 MTA:SA Documentation MCP Server server expose?
MTA:SA Documentation MCP Server exposes 11 tools: search_functions, search_events, find_functions_for_task, find_events_for_task, get_function_docs, and 6 more. Their descriptions and schemas cost roughly 780 tokens of context every time the server is loaded.
Is the MTA:SA Documentation MCP Server server still maintained?
MTA:SA Documentation MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MTA:SA Documentation MCP Server server under?
MTA:SA Documentation MCP Server declares the GPL-3.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.