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.

io.github.brentspore/buildutilities-mcp

NPM · BUILDUTILITIES-MCP · SCANNED SEP 24

Deterministic dev utilities: UUIDs, hashes, encoding, JWT, cron, regex. No network, no API key.

Available components

+3 this week 79 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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1641 tokens (~82/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 38% 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 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
Install

How do I install the io.github.brentspore/buildutilities-mcp server?

io.github.brentspore/buildutilities-mcp runs locally as an npm package, launched with npx -y buildutilities-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 · buildutilities-mcp

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

  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +9
    • Tool safety: pass → unverified ▼ security
    • Source repository: fail → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: unverified → fail ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.27 ▲ functional
    • First check of Schema quality: unverified functional
    • Schema quality: excellent → good functional
    • Package version: 0.1.0 → 0.1.2 functional
    • Package version: 0.1.0 → 0.1.1 functional
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 24 Sept 2026 · Analysed npm/buildutilities-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,571 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
analyze_text ~60

Exact counts for a text: characters, words, lines, sentences, paragraphs, bytes. Use this rather than estimating — counting long text is a classic model failure. Web version: https://buildutilities.com/word-counter

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

base64_decode ~62

Decode Base64 (standard or URL-safe) back to text. Reports whether the input was valid rather than returning mojibake. Web version: https://buildutilities.com/base64-codec

NameTypeReqDescription
encodedstringyesBase64 or base64url input

No output schema declared.

No examples provided.

base64_encode ~65

Encode text to Base64. Set urlSafe for the URL/filename-safe alphabet (-_ instead of +/, no padding). Web version: https://buildutilities.com/base64-codec

NameTypeReqDescription
textstringyesText to encode
urlSafeboolean––

No output schema declared.

No examples provided.

check_color_contrast ~99

Compute the exact WCAG 2.2 contrast ratio between two colours and report which AA/AAA thresholds it passes. This is a specific formula, not a judgement call — do not estimate it. Web version: https://buildutilities.com/color-contrast-checker

NameTypeReqDescription
backgroundstringyesHex colour, e.g. #ffffff
foregroundstringyesHex colour, e.g. #1a1a1a

No output schema declared.

No examples provided.

convert_timestamp ~96

Convert between Unix epoch and human-readable time, in any IANA timezone. Auto-detects seconds vs milliseconds. Use this rather than doing the arithmetic in your head. Web version: https://buildutilities.com/timestamp-converter

NameTypeReqDescription
timeZonestring–IANA timezone, e.g. "America/New_York"
valuestringyesEpoch seconds/ms, an ISO 8601 string, or "now"

No output schema declared.

No examples provided.

cron_next_runs ~127

Parse a standard 5-field cron expression and list its next run times in a timezone. Handles the Vixie rule that day-of-month and day-of-week are OR'd when both are restricted — the case models most often get wrong. Rejects non-standard syntax (L, W, #) rather than guessing. Web version: https://buildutilities.com/cron-expression-generator

NameTypeReqDescription
countinteger––
expressionstringyese.g. "*/15 9-17 * * mon-fri" or "@daily"
timeZonestring––

No output schema declared.

No examples provided.

decode_jwt ~93

Decode a JSON Web Token's header and payload and report expiry. This DECODES ONLY — it does not verify the signature, so never treat the contents as trusted on the strength of this output. Models asked to read a JWT tend to invent its claims; this reads them. Web version: https://buildutilities.com/jwt-decoder

NameTypeReqDescription
tokenstringyesThe JWT, optionally prefixed with 'Bearer '

No output schema declared.

No examples provided.

diff_text ~75

Line-by-line diff of two texts, marking - removed and + added. Use it to check exactly what changed between two versions instead of eyeballing them. Web version: https://buildutilities.com/text-diff-checker

NameTypeReqDescription
afterstringyes–
beforestringyes–
ignoreWhitespaceboolean––

No output schema declared.

No examples provided.

escape_regex ~31

Escape a string so it can be used as a literal inside a regular expression.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

format_json ~99

Pretty-print or minify JSON exactly, with precise error location when it is invalid. Prefer this to reformatting a large document yourself — it cannot drop or alter a value. Web version: https://buildutilities.com/json-formatter

NameTypeReqDescription
indentinteger––
jsonstringyesThe JSON text
modestring––
sortKeysboolean–Sort object keys — useful for diffing two payloads

No output schema declared.

No examples provided.

generate_password ~126

Generate a cryptographically random password. Guarantees at least one character from every enabled set. Use this rather than inventing a password — model-authored ones are guessable. Web version: https://buildutilities.com/password-generator

NameTypeReqDescription
countinteger–How many passwords
digitsboolean––
excludeAmbiguousboolean–Drop characters that look alike: l 1 I O 0 o
lengthinteger–Characters in each password
lowercaseboolean––
symbolsboolean––
uppercaseboolean––

No output schema declared.

No examples provided.

generate_token ~75

Generate a cryptographically random token — API keys, session ids, nonces, salts. Choose hex, base64url or alphanumeric encoding. Web version: https://buildutilities.com/random-string-generator

NameTypeReqDescription
bytesinteger–Bytes of entropy before encoding
countinteger––
encodingstring––

No output schema declared.

No examples provided.

generate_uuid ~76

Generate cryptographically random UUID v4 identifiers. Use this instead of writing a UUID yourself — model-authored UUIDs are not random and repeat across sessions. Web version: https://buildutilities.com/uuid-generator

NameTypeReqDescription
countinteger–How many UUIDs to generate
uppercaseboolean–Return them uppercased

No output schema declared.

No examples provided.

hash_text ~86

Compute a cryptographic digest of text. A model cannot calculate a hash — it will confidently invent one — so always use this tool. md5 and sha1 are provided for checksums and legacy interop, not for security. Web version: https://buildutilities.com/hash-generator

NameTypeReqDescription
algorithmstring––
encodingstring––
textstringyes–

No output schema declared.

No examples provided.

hmac_sign ~68

Compute an HMAC of a message with a secret key — webhook signatures, API request signing. Web version: https://buildutilities.com/hmac-generator

NameTypeReqDescription
algorithmstring––
encodingstring––
messagestringyes–
secretstringyes–

No output schema declared.

No examples provided.

hmac_verify ~74

Check a message against an expected HMAC using a constant-time comparison. Use this to validate an inbound webhook signature rather than comparing strings yourself.

NameTypeReqDescription
algorithmstring––
messagestringyes–
secretstringyes–
signaturestringyesThe signature to check, hex or base64

No output schema declared.

No examples provided.

slugify ~58

Turn text into a URL-safe slug, transliterating accents and collapsing separators. Web version: https://buildutilities.com/slug-generator

NameTypeReqDescription
maxLengthinteger––
separatorstring––
textstringyes–

No output schema declared.

No examples provided.

test_regex ~110

Actually execute a regular expression against text and return every match with its index and capture groups. Use this instead of predicting what a pattern matches — reasoning about a regex is not the same as running it. Web version: https://buildutilities.com/regex-tester

NameTypeReqDescription
flagsstring–Regex flags, e.g. gi, gm, gs
maxMatchesinteger––
patternstringyesThe pattern, without delimiters
textstringyesText to search

No output schema declared.

No examples provided.

url_decode ~33

Decode percent-encoded text. Web version: https://buildutilities.com/url-codec

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

url_encode ~58

Percent-encode text. component mode escapes & = ? / for use inside a query value; uri mode preserves them. Web version: https://buildutilities.com/url-codec

NameTypeReqDescription
modestring––
textstringyes–

No output schema declared.

No examples provided.

Common questions

What is the io.github.brentspore/buildutilities-mcp server?

io.github.brentspore/buildutilities-mcp is listed in the public MCP registry as io.github.brentspore/buildutilities-mcp. Deterministic dev utilities: UUIDs, hashes, encoding, JWT, cron, regex. No network, no API key. This page covers its npm package (buildutilities-mcp).

Is the io.github.brentspore/buildutilities-mcp server safe to use?

io.github.brentspore/buildutilities-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 io.github.brentspore/buildutilities-mcp server expose?

io.github.brentspore/buildutilities-mcp exposes 20 tools: generate_uuid, generate_password, generate_token, base64_encode, base64_decode, and 15 more. Their descriptions and schemas cost roughly 1,571 tokens of context every time the server is loaded.

Is the io.github.brentspore/buildutilities-mcp server still maintained?

io.github.brentspore/buildutilities-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 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 io.github.brentspore/buildutilities-mcp server under?

io.github.brentspore/buildutilities-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.