bestax-mcp

MCPattested
v1.14.4Alex SmithMITUpdated 2d agonpmGitHub

MCP server for @allxsmith/bestax-bulma — component props, examples, CSS variables and agent skills, served offline from a version-pinned index

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
975Downloads/wk
12GitHub stars
2d agoLast update
Package
AuthorAlex Smith
LicenseMIT
Version1.14.4
Sourcenpm+mcp-registry
npmbestax-mcp
GitHuballxsmith/bestax
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 54d0eea
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv1.14.4 · 1d agoHow well does this scan work?
EvalsNone
IndexedOct 10, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev1.14.4 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

search_bestaxSearch components, props, usage examples, CSS variables and agent

Search components, props, usage examples, CSS variables and agent

No input schema was published for this tool.

list_componentsEvery documented component with a one-line purpose, grouped by

Every documented component with a one-line purpose, grouped by

No input schema was published for this tool.

get_componentImport statement, summary and prop table for one component. Add

Import statement, summary and prop table for one component. Add

No input schema was published for this tool.

get_propsThe prop table for a component, or for one part of a compound family

The prop table for a component, or for one part of a compound family

No input schema was published for this tool.

get_examplesWorking examples from the component's documentation page. Every one

Working examples from the component's documentation page. Every one

No input schema was published for this tool.

get_css_variablesThe --bulma-* custom properties a component reads, with their Sass

The --bulma-* custom properties a component reads, with their Sass

No input schema was published for this tool.

get_helper_propsThe helper props every bestax component accepts — spacing, colour,

The helper props every bestax component accepts — spacing, colour,

No input schema was published for this tool.

lookup_bulma_classesThe bestax component and props for a Bulma class string, one row per

The bestax component and props for a Bulma class string, one row per

No input schema was published for this tool.

list_skillsThe bestax Agent Skills — task-level guides for forms, theming,

The bestax Agent Skills — task-level guides for forms, theming,

No input schema was published for this tool.

get_skillA skill's instructions, or one of its reference documents. Load the

A skill's instructions, or one of its reference documents. Load the

No input schema was published for this tool.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for @allxsmith/bestax-bulma — component props, examples, CSS variables and agent skills, served offline from a version-pinned index

Keywords
bestaxbulmareactmcpmodel-context-protocolaiagentsllmscomponentsdocumentation
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-11 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

56 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+44 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.