Bragproof

← Reports

@spartan-ng/mcp

Starts with no setup1.9.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing

17tools listed
0hosts contacted
1file written
0.2 sto start
96dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @spartan-ng/mcp@1.9.0

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 5 returned a result.

spartan_components_listReturned a result under 0.1 s · 6,647 characters
spartan_health_checkReturned a result 3.5 s · 1,917 characters
spartan_health_instructionsReturned a result under 0.1 s · 482 characters
spartan_cache_statusReturned a result under 0.1 s · 351 characters
spartan_cache_list_versionsReturned a result under 0.1 s · 104 characters

During the calls (not necessarily because of them) it first contacted: www.spartan.ng.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

1 tool with commands in capitals or very long text
  • Gives the agent orders in spartan_components_get: cumentation page for a given component (e.g., 'accordion'). IMPORTANT: The response contains comprehensive API information including Brain API (Brn*) and Helm API (Hlm*)

Common and usually harmless: it is how many makers stress how a tool should be used.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

spartan_components_list
Returns a list of known Spartan Angular UI components with their documentation URLs. Use this to discover available components, then call spartan_components_get with specific component names to get detailed API documentation.
spartan_components_get name, extract, noCache, spartanVersion
Fetch the Spartan UI documentation page for a given component (e.g., 'accordion'). IMPORTANT: The response contains comprehensive API information including Brain API (Brn*) and Helm API (Hlm*) components with their inputs, outputs, selectors, and examples. Always parse and present the API tables, code examples, and component specifications from the response. Look for structured sections like 'Brain API', 'Helm API', and 'Examples' in the response.
spartan_docs_get topic, format, extract, noCache, spartanVersion
Fetch an official Spartan documentation section by topic (introduction, changelog, about, installation, components-json, theming, styles, dark-mode, cli, rtl, typography, figma, version-support, health-checks, update-guide, mcp, skills).
spartan_health_check topics, components
Check availability and response times for selected Spartan docs and component pages. This validates the docs site, not your local workspace health check.
spartan_health_instructions
Return official instructions and commands for running the Spartan CLI health check in Angular CLI or Nx workspaces.
12 more tools
spartan_health_command tool, dryRun
Return the exact command to run the Spartan health check for Angular CLI or Nx. Optionally append --dry-run.
spartan_meta
Return known docs topics, components, and blocks for client autocomplete.
spartan_components_dependencies componentName, includeTransitive
Analyze what other components, packages, or dependencies a Spartan UI component requires. Includes Angular CDK dependencies, peer components, and installation requirements.
spartan_accessibility_check componentName, checkType
Analyze accessibility features, ARIA support, keyboard navigation, and screen reader compatibility for a Spartan UI component. Provides accessibility best practices and implementation guidance.
spartan_cache_status
Get current cache status, including version, cached components, and statistics
spartan_cache_clear allVersions
Clear cached documentation for the current Spartan UI version
spartan_cache_rebuild components, blocks, includeDocs
Rebuild cache by fetching fresh documentation from spartan.ng for all components and blocks
spartan_cache_switch_version version
Switch to a different Spartan UI version for caching and retrieval
spartan_cache_list_versions
List all cached Spartan UI versions
spartan_blocks_list
Returns a list of known Spartan Angular UI blocks (pre-built UI patterns) with their documentation URLs. Blocks are higher-level compositions of components like sidebars, login forms, signup forms, calendars, and steppers. Use this to discover available blocks, then call spartan_blocks_get with specific block names to get detailed code.
spartan_blocks_get name, format, noCache, spartanVersion
Fetch the Spartan UI documentation page for a given block (e.g., 'sidebar', 'login'). Blocks are pre-built UI patterns that combine multiple components. The response includes complete code examples showing how to use the block.
spartan_blocks_dependencies blockName
Analyze what components and packages a Spartan UI block requires. Blocks are compositions of multiple components, so this shows all underlying dependencies.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseMIT
Needsnot stated
Sourcegithub.com/spartan-ng/spartan
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-KNibX6Kp3bcUvycMfCgwxVJLfYJsJmguB4y8qiJbhCLFkh65Kmaax3+/67nWP5USkw6GPkmX4CvG/7QB4bGkAQ==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@spartan-ng/mcp.svg)](https://bragproof.smaverk.com/r/%40spartan-ng/mcp)

New version out? Ask for a fresh report.