MTA:SA Documentation MCP Server

NPM · MTASA-DOCS-MCP · SCANNED AUG 3

MCP server for MTA:SA documentation with intelligent search and caching

Available components

+29 this week 82 82 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security88

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency97

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 111 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability85

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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · mtasa-docs-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add luminaire1337-mtasa-docs-mcp -- npx -y mtasa-docs-mcp

# add to Codex CLI

codex mcp add luminaire1337-mtasa-docs-mcp -- npx -y mtasa-docs-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "luminaire1337-mtasa-docs-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mtasa-docs-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add luminaire1337-mtasa-docs-mcp --command npx --arg -y --arg mtasa-docs-mcp

# ~/.hermes/config.yaml

mcp_servers:
  luminaire1337-mtasa-docs-mcp:
    command: "npx"
    args: ["-y", "mtasa-docs-mcp"]

// mcp.json

{
  "mcpServers": {
    "luminaire1337-mtasa-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mtasa-docs-mcp"
      ]
    }
  }
}

Changelog

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 Aug 26 +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.
2 Aug 26 +15
- Known CVEs: partial → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: partial → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
1 Aug 26 +35
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- The attested source repository moved: Luminaire1337/mtasa-docs-mcp security
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Licence: GPL-3.0 functional
31 Jul 26 −22
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 53

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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:: https://slsa.dev/provenance/v1
Subject digest:: sha512:307d107b9a44f404c8dd682284f2f3792cef7d3dffd8a96c668d8ca6918f0813a90cb28dc7e153935695bbd28c91fbca2f380e92a5046724738505f5c
Discovery method:: attestation_endpoint

Dependencies 102 packages

102 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 11 exposed · ~780 tokens

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.

Tool Tokens

clear_cache ~46

Clear the MTA:SA documentation cache for a specific function or all functions.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug