Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bestax

NPM · BESTAX-MCP · SCANNED OCT 4

Props, examples, CSS variables and Agent Skills for bestax-bulma React components (Bulma v1)

Available components

82 Trust /100
Trust breakdown (7 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 → 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
  • 31 of 97 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 allxsmith/bestax). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 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 928 tokens (~84/item across 11 items; 10 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 78% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the Bestax MCP server?

Bestax runs locally as an npm package, launched with npx -y bestax-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 · bestax-mcp

# add to Claude Code
claude mcp add allxsmith-bestax-mcp -- npx -y bestax-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "allxsmith-bestax-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bestax-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "allxsmith-bestax-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bestax-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add allxsmith-bestax-mcp -- npx -y bestax-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "allxsmith-bestax-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "bestax-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add allxsmith-bestax-mcp --command npx --arg -y --arg bestax-mcp
# ~/.hermes/config.yaml
mcp_servers:
  allxsmith-bestax-mcp:
    command: "npx"
    args: ["-y", "bestax-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "allxsmith-bestax-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "bestax-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add allxsmith-bestax-mcp -t stdio -c npx -a -y bestax-mcp
// mcp.json
{
  "mcpServers": {
    "allxsmith-bestax-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bestax-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.

  • 4 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Oct 26 67

    First indexed and scored.

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 7 Oct 2026 · Analysed npm/bestax-mcp@1.14.0

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 allxsmith/bestax
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/allxsmith/bestax/.github/workflows/ci.yml@refs/heads/main
Rekor log index 3067498467
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8e99d9b33b0782da112f6e1712013f2c3f9cde95a47b0fdf1e99387fd379fe65311664b667c625224f5b05dbd62a917162b271999099ee33d81c8b2ce

Background: How many MCP packages publish verified provenance →

Dependencies 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 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. 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 →

Tool Tokens
get_component ~69

Import statement, summary and prop table for one component. Add `include` for examples, CSS variables, accessibility notes or related components.

NameTypeReqDescription
includearray–Extra sections. Defaults to ["props"].
namestringyesComponent name, e.g. "Button" or "Navbar"

No output schema declared.

No examples provided.

get_css_variables ~82

The --bulma-* custom properties a component reads, with their Sass names and defaults. This is how you restyle bestax — reach for these before writing custom CSS. Omit `component` to search across all of them.

NameTypeReqDescription
componentstring––
querystring–Substring of a variable name, e.g. "radius"

No output schema declared.

No examples provided.

get_examples ~66

Working examples from the component's documentation page. Every one is executed on the docs site, so they compile against this version.

NameTypeReqDescription
componentstringyes–
limitinteger––
querystring–Filter by example heading or code, e.g. "loading"

No output schema declared.

No examples provided.

get_helper_props ~79

The helper props every bestax component accepts — spacing, colour, typography, flexbox, visibility — and their valid values. Call this BEFORE writing an inline style or a utility class by hand; this library expects those to be props.

NameTypeReqDescription
groupstring–Filter to one area, e.g. "spacing", "flex", "color"

No output schema declared.

No examples provided.

get_props ~81

The prop table for a component, or for one part of a compound family (pass a dot-path like "Navbar.Brand"). Cheaper than get_component when the props are all you need.

NameTypeReqDescription
componentstringyesComponent name, e.g. "Navbar"
pathstring–Dot-path of a subcomponent, e.g. "Navbar.Brand"

No output schema declared.

No examples provided.

get_skill ~80

A skill's instructions, or one of its reference documents. Load the skill first; pull a reference only when you need that depth.

NameTypeReqDescription
namestringyesSkill name, e.g. "bestax-theming" or "theming"
referencestring–Reference id from list_skills, e.g. "css-variables"

No output schema declared.

No examples provided.

list_components ~55

Every documented component with a one-line purpose, grouped by category. Cheap — use it to find the right name before calling get_component.

NameTypeReqDescription
categorystring–elements, components, form, columns, grid, layout, helpers

No output schema declared.

No examples provided.

list_skills ~48

The bestax Agent Skills — task-level guides for forms, theming, layout scaffolding, icons, custom components, migration and CSS size. Read one with get_skill when a task matches.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_bulma_classes ~123

The bestax component and props for a Bulma class string, one row per class: "button is-primary", "columns is-mobile", "has-text-centered mt-4". Call this BEFORE writing a Bulma class by hand, and when converting existing Bulma markup. Pass the tag the classes sit on when there is one.

NameTypeReqDescription
classesstringyesThe class string, e.g. "button is-primary is-large"
tagstring–The lowercase tag the classes are on, e.g. "a" or "h2"

No output schema declared.

No examples provided.

search_bestax ~97

Search components, props, usage examples, CSS variables and agent skills at once. The entry point — each hit names the tool to call for the full thing. Use this before guessing a component name.

NameTypeReqDescription
kindstring–Restrict to one kind of result. Defaults to all.
limitinteger––
querystringyesWhat you are looking for, e.g. "date picker" or "spacing"

No output schema declared.

No examples provided.

Common questions

What is the Bestax MCP server?

Bestax is an MCP server listed in the public MCP registry as io.github.allxsmith/bestax-mcp. Props, examples, CSS variables and Agent Skills for bestax-bulma React components (Bulma v1). This page covers its npm package (bestax-mcp).

Is the Bestax MCP server safe to use?

Bestax scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 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 Bestax MCP server expose?

Bestax exposes 10 tools: search_bestax, list_components, get_component, get_props, get_examples, and 5 more. Their descriptions and schemas cost roughly 780 tokens of context every time the server is loaded.

Is the Bestax MCP server still maintained?

Bestax is still listed as active in the MCP registry. We last reached this channel on 4 October 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 Bestax MCP server under?

Bestax declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.