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.

services.gera/mcp-geratools

NPM · @GERA-SERVICES/MCP-GERATOOLS

base64, hashing, regex, word count, JWT decode and CSS unit conversion. Deterministic, offline.

0 this week 74 Trust /100

Last scanned (18 hours ago)

Scores higher than 49% of npm servers

Category Developer Tools

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 150 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 788 tokens (~131/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 0
    • Stability: 0.97 → pass security
  • 19 Nov 26 +1

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

  • 18 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 10 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 4 Nov 26 0
    • Stability: 0.97 → pass security
  • 3 Nov 26 0
    • Stability: pass → 0.97 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 21 Nov 2026 · Analysed npm/@gera-services/mcp-geratools@1.0.1

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~788 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
base64 ~203

Encode text or hex bytes to Base64, or decode Base64 / Base64url back to text. Binary-safe via UTF-8 so emoji and non-ASCII round-trip correctly. Supports standard (+ / with = padding) and URL-safe (- _ no padding) variants. Decoding auto-restores padding and falls back to raw hex if the bytes are not valid UTF-8. Runs entirely offline — same logic as the GeraTools Base64 tool.

NameTypeReqDescription
inputstringyesThe text/hex to encode, or the Base64 string to decode.
input_kindstring–When encoding, treat input as UTF-8 "text" (default) or "hex" bytes.
modestringyes"encode" text→Base64, or "decode" Base64→text.
variantstring–Encode output: "std" (default) or "url" (URL-safe Base64url). Ignored when decoding.

No output schema declared.

No examples provided.

css_unit_convert ~152

Convert a CSS length value from one unit to every other CSS unit (px, rem, em, pt, pc, in, cm, mm, Q). Absolute units use 1in = 96px; rem depends on root font size and em on parent font size (both default 16px). Offline — same logic as the GeraTools CSS Unit Converter.

NameTypeReqDescription
fromstringyesThe unit of the input value.
parent_font_pxnumber–Parent font size in px, used for em. Default 16.
root_font_pxnumber–Root font size in px, used for rem. Default 16.
valuenumberyesThe numeric length value.

No output schema declared.

No examples provided.

hash ~150

Compute a cryptographic digest of the input using Node crypto — the same algorithms a browser SubtleCrypto produces. Input can be utf8 (default), hex, or base64; output as hex (default) or base64. Deterministic and offline. Note: MD5 and SHA-1 are provided for checksums/legacy interop only, not for security.

NameTypeReqDescription
algorithmstringyesHash algorithm: md5, sha1, sha256, sha384, or sha512.
inputstringyesThe data to hash.
input_encodingstring–How to interpret the input bytes. Default utf8.
output_encodingstring–Digest output encoding. Default hex.

No output schema declared.

No examples provided.

jwt_decode ~89

Base64url-decode a JWT into its header and payload JSON, list the iat/nbf/exp time claims as ISO timestamps, and report whether the token is expired. Does NOT verify the signature — never trust an unverified payload for authorization. Offline — same logic as the GeraTools JWT Decoder.

NameTypeReqDescription
tokenstringyesThe JWT, e.g. "header.payload.signature".

No output schema declared.

No examples provided.

regex_test ~129

Run a JavaScript regular expression against a test string and return every match (with index, capture groups and named groups), the match count, and a plain-English, token-by-token explanation of the pattern. Invalid patterns return the engine error rather than throwing. Offline — same logic as the GeraTools Regex Tester.

NameTypeReqDescription
flagsstring–Regex flags, e.g. "gi". Default "g". (g is forced internally for enumeration.)
patternstringyesThe regular expression source (no surrounding slashes).
test_stringstringyesThe string to run the regex against.

No output schema declared.

No examples provided.

word_count ~65

Analyse a block of text: word count, characters (with and without spaces), sentence count, paragraph count, line count, and estimated reading time (200 wpm). Offline — same logic as the GeraTools Word Counter.

NameTypeReqDescription
textstringyesThe text to analyse.

No output schema declared.

No examples provided.

Install

How do I install the services.gera/mcp-geratools server?

services.gera/mcp-geratools runs locally as an npm package, launched with npx -y @gera-services/mcp-geratools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @gera-services/mcp-geratools

# add to Claude Code
claude mcp add services-gera-mcp-geratools -- npx -y @gera-services/mcp-geratools
Common questions

What is the services.gera/mcp-geratools server?

services.gera/mcp-geratools is listed in the public MCP registry as services.gera/mcp-geratools. base64, hashing, regex, word count, JWT decode and CSS unit conversion. Deterministic, offline. This page covers its npm package (@gera-services/mcp-geratools).

Is the services.gera/mcp-geratools server safe to use?

services.gera/mcp-geratools scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 services.gera/mcp-geratools server expose?

services.gera/mcp-geratools exposes 6 tools: base64, hash, regex_test, word_count, jwt_decode, css_unit_convert. Their descriptions and schemas cost roughly 788 tokens of context every time the server is loaded.

Is the services.gera/mcp-geratools server still maintained?

services.gera/mcp-geratools is still listed as active in the MCP registry. We last reached this channel on 21 November 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 services.gera/mcp-geratools server under?

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

What did VerifyMCP test on the services.gera/mcp-geratools server?

VerifyMCP ran 15 checks on services.gera/mcp-geratools, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about services.gera/mcp-geratools: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.