# RedBison (remote · mcp.redbison.dev)

500+ free tools over MCP: dev, text and security utilities, 230+ calculators. No sign-up.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.redbison.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-redbison-mcp/mcp.md), [page](https://verifymcp.io/servers/dev-redbison-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.redbison.dev`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 12887 tokens (~157/item across 82 items; 82 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_duplicate_lines" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 83 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RedBison MCP server?

RedBison is a hosted endpoint at https://mcp.redbison.dev/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-redbison-mcp 'https://mcp.redbison.dev/'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-redbison-mcp": {
      "url": "https://mcp.redbison.dev/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-redbison-mcp": {
      "type": "http",
      "url": "https://mcp.redbison.dev/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-redbison-mcp]
url = "https://mcp.redbison.dev/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-redbison-mcp": {
      "type": "remote",
      "url": "https://mcp.redbison.dev/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-redbison-mcp --url 'https://mcp.redbison.dev/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-redbison-mcp:
    url: "https://mcp.redbison.dev/"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-redbison-mcp": {
      "Transport": "http",
      "Url": "https://mcp.redbison.dev/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-redbison-mcp -t streamable-http -u 'https://mcp.redbison.dev/'
```

### Other

```json
{
  "mcpServers": {
    "dev-redbison-mcp": {
      "type": "http",
      "url": "https://mcp.redbison.dev/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 67, +1)

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

### 2026-11-03 (score 66, +1)

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

### 2026-11-01 (score 65, +1)

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

### 2026-10-31 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 64)

First indexed and scored.

## MCP tools (82)

### `search_tools` (~162 tokens)

Search RedBison tools

Search RedBison's 500+ tools by keyword: developer utilities, file and media converters, and finance, health, math and engineering calculators. Returns a ranked list with each tool's canonical URL and, when one exists, its in-depth guide. Use this when a user asks 'is there a tool for X?' or 'what RedBison tool should I use to Y?'

Returns: JSON with { query, count, results[] } where each result has { id, name, description, url, category }.
Example input: {"query":"json format","limit":5}

Input parameters:

- `limit` (number): Max results (default 10, max 25).
- `query` (string, required): Search term (name, keyword, or use case).

### `get_tool` (~81 tokens)

Get RedBison tool

Get full metadata for a specific RedBison tool by its id (slug).

Returns: Full JSON metadata for the tool: { id, name, description, url, category, subcategory?, keywords[] }.
Example input: {"id":"jwt-decoder"}

Input parameters:

- `id` (string, required): Tool id / URL slug, e.g. "jwt-decoder".

### `list_categories` (~44 tokens)

List categories

List all tool categories and subcategories available on RedBison.

Returns: JSON array of { category, count } entries covering the full RedBison catalog.
Example input: {}

### `health` (~47 tokens)

Server health

Return server status, name, version, and uptime info. Use this to monitor the MCP server.

Returns: JSON { status, name, version, startedAt, timestamp }.
Example input: {}

### `base64_encode` (~48 tokens)

Base64 encode

Base64-encode a UTF-8 string.

Returns: Base64-encoded string (UTF-8 safe).
Example input: {"text":"hello world"}

Input parameters:

- `text` (string, required)

### `base64_decode` (~55 tokens)

Base64 decode

Base64-decode a string back to UTF-8.

Returns: UTF-8 decoded plain text.
Example input: {"text":"aGVsbG8gd29ybGQ="}

Input parameters:

- `text` (string, required)

### `url_encode` (~48 tokens)

URL encode

Percent-encode a string for use in URLs.

Returns: Percent-encoded string suitable for URL query values.
Example input: {"text":"hello world & friends"}

Input parameters:

- `text` (string, required)

### `url_decode` (~50 tokens)

URL decode

Percent-decode a URL-encoded string.

Returns: Percent-decoded plain text.
Example input: {"text":"hello%20world%20%26%20friends"}

Input parameters:

- `text` (string, required)

### `json_format` (~123 tokens)

Format JSON

Pretty-print a JSON string with a chosen indent size.

Returns: Pretty-printed JSON string with the requested indent, or an error message if the input is invalid.
Example input: {"text":"{\"a\":1,\"b\":[2,3]}","indent":2}
On error, includes hint: Pass valid JSON as `text` (double-quoted keys/strings, no trailing commas). `indent` is an integer between 0 and 10.

Input parameters:

- `indent` (number): Indent spaces (default 2).
- `text` (string, required)

### `json_validate` (~67 tokens)

Validate JSON

Validate a JSON string. Returns { valid, error? }.

Returns: JSON { valid: boolean, error?: string }.
Example input: {"text":"{\"a\":1}"}
On error, includes hint: Pass the JSON string as `text`.

Input parameters:

- `text` (string, required)

### `csv_to_json` (~130 tokens)

CSV to JSON

Parse CSV text into JSON. Uses the first row as headers unless header=false.

Returns: JSON array of row objects keyed by the header row.
Example input: {"text":"name,age\nAda,36\nGrace,85","delimiter":","}
On error, includes hint: `text` must be CSV with a header row unless `header:false`. Escape embedded quotes as "".

Input parameters:

- `delimiter` (string): Field delimiter (default ",").
- `header` (boolean): First row is header (default true). If false, returns array of arrays.
- `text` (string, required): CSV input.

### `json_to_csv` (~129 tokens)

JSON to CSV

Convert an array of JSON objects to CSV. Columns are inferred from the union of keys.

Returns: CSV string with a header row derived from the first object's keys.
Example input: {"json":"[{\"name\":\"Ada\",\"age\":36},{\"name\":\"Grace\",\"age\":85}]","delimiter":","}
On error, includes hint: `json` must be a JSON-encoded array of objects (parameter name is `json`, not `text`).

Input parameters:

- `delimiter` (string): Field delimiter (default ",").
- `json` (string, required): JSON array of objects, as a string.

### `json_to_yaml` (~85 tokens)

JSON to YAML

Convert a JSON string to YAML.

Returns: YAML representation of the parsed JSON value.
Example input: {"json":"{\"name\":\"Ada\",\"skills\":[\"math\",\"logic\"]}"}
On error, includes hint: Pass the JSON as `json` (a stringified JSON value), not as a JS object.

Input parameters:

- `json` (string, required): JSON input as a string.

### `yaml_to_json` (~108 tokens)

YAML to JSON

Convert simple YAML (maps, lists, scalars, flow {} / []) to JSON. Anchors, tags, and complex block scalars are not supported.

Returns: Pretty-printed JSON built from the YAML input.
Example input: {"yaml":"name: Ada\nskills:\n  - math\n  - logic"}
On error, includes hint: Pass the YAML document as `yaml`; only 2-space indented block YAML is supported.

Input parameters:

- `yaml` (string, required): YAML input.

### `tsv_parse` (~103 tokens)

TSV parser

Parse tab-separated values into JSON. First row is treated as header unless header=false.

Returns: JSON array of row objects derived from the TSV header row.
Example input: {"text":"name\tage\nAda\t36\nGrace\t85"}
On error, includes hint: `text` must use real tab (\t) separators, not multiple spaces.

Input parameters:

- `header` (boolean): First row is header (default true).
- `text` (string, required): TSV input.

### `html_beautify` (~78 tokens)

HTML beautify

Pretty-print an HTML fragment.

Returns: Pretty-printed HTML string with normalized indentation.
Example input: {"html":"<div><p>hi</p><p>there</p></div>","indent":2}

Input parameters:

- `html` (string, required): HTML input.
- `indent` (number): Indent size (default 2).

### `xml_beautify` (~78 tokens)

XML beautify

Pretty-print an XML document.

Returns: Pretty-printed XML string with normalized indentation.
Example input: {"xml":"<root><a>1</a><b>2</b></root>","indent":2}

Input parameters:

- `indent` (number): Indent size (default 2).
- `xml` (string, required): XML input.

### `yaml_beautify` (~65 tokens)

YAML beautify

Normalize YAML indentation and whitespace.

Returns: Normalized YAML string (2-space indent, collapsed blank lines).
Example input: {"yaml":"a:    1\nb:  2\n\n\nc: 3"}

Input parameters:

- `yaml` (string, required): YAML input.

### `sql_beautify` (~65 tokens)

SQL beautify

Format a SQL query with keyword uppercasing and line breaks before major clauses.

Returns: Formatted SQL query with keywords on new lines.
Example input: {"sql":"select id,name from users where active=true order by name"}

Input parameters:

- `sql` (string, required): SQL query.

### `slugify` (~49 tokens)

Slugify text

Convert text to a URL-safe slug.

Returns: URL-safe slug (lowercase, dashes).
Example input: {"text":"Hello, World! 2026"}

Input parameters:

- `text` (string, required)

### `case_convert` (~96 tokens)

Convert case

Convert text between upper, lower, title, camel, pascal, snake, and kebab case.

Returns: String converted to the requested case.
Example input: {"text":"hello world example","style":"camel"}
On error, includes hint: `style` must be one of: upper, lower, title, camel, pascal, snake, kebab.

Input parameters:

- `style` (string, required)
- `text` (string, required)

### `escape_characters` (~122 tokens)

Escape / unescape characters

Escape or unescape a string for JSON, HTML, XML, JavaScript, or SQL.

Returns: Escaped or unescaped string for the chosen format.
Example input: {"text":"He said \"hi\"","format":"json","mode":"escape"}
On error, includes hint: `mode` is 'escape' or 'unescape'; `format` is one of: json, html, xml, js, sql.

Input parameters:

- `format` (string, required): Target format.
- `mode` (string, required): Direction.
- `text` (string, required): Input text.

### `remove_duplicate_lines` (~101 tokens)

Remove duplicate lines

Remove duplicate lines from text while preserving first-occurrence order.

Returns: Text with duplicate lines removed (order preserved).
Example input: {"text":"apple\nbanana\napple\ncherry","caseInsensitive":false,"trim":true}

Input parameters:

- `caseInsensitive` (boolean): Compare case-insensitively (default false).
- `text` (string, required): Multi-line text to deduplicate.
- `trim` (boolean): Trim each line before comparing (default true).

### `find_duplicate_entries` (~103 tokens)

Find duplicate entries

Return lines that appear more than once in the input, with their occurrence counts.

Returns: JSON array of { value, count } for lines appearing more than once.
Example input: {"text":"apple\nbanana\napple\ncherry\nbanana"}

Input parameters:

- `caseInsensitive` (boolean): Compare case-insensitively (default false).
- `text` (string, required): Multi-line text to scan.
- `trim` (boolean): Trim each line before comparing (default true).

### `remove_extra_spaces` (~59 tokens)

Remove extra spaces

Collapse runs of whitespace inside each line to a single space and trim ends.

Returns: Text with runs of whitespace collapsed to a single space.
Example input: {"text":"hello    world   foo"}

Input parameters:

- `text` (string, required): Text to normalize.

### `remove_empty_lines` (~53 tokens)

Remove empty lines

Strip blank / whitespace-only lines from the input.

Returns: Text with blank lines removed.
Example input: {"text":"one\n\ntwo\n\n\nthree"}

Input parameters:

- `text` (string, required): Multi-line text.

### `lines_to_comma` (~99 tokens)

Lines to comma-separated

Join lines with a separator (comma by default). Empty lines are skipped.

Returns: Single-line string with items joined by the chosen separator.
Example input: {"text":"apple\nbanana\ncherry","separator":", ","quote":false}

Input parameters:

- `quote` (boolean): Wrap each item in double quotes (default false).
- `separator` (string): Separator between items (default ", ").
- `text` (string, required): Multi-line input.

### `comma_to_lines` (~89 tokens)

Comma-separated to lines

Split a delimited string into one item per line.

Returns: Multi-line string, one item per line.
Example input: {"text":"apple, banana, cherry","separator":",","trim":true}

Input parameters:

- `separator` (string): Delimiter to split on (default ",").
- `text` (string, required): Delimited input.
- `trim` (boolean): Trim each item (default true).

### `jwt_decode` (~111 tokens)

Decode JWT

Decode a JWT and return its header + payload. Does NOT verify the signature.

Returns: JSON with decoded { header, payload, signature } sections of the JWT.
Example input: {"token":"eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjMifQ.abc"}
On error, includes hint: `token` must be a compact JWT with three base64url-encoded parts separated by dots.

Input parameters:

- `token` (string, required): The JWT string.

### `hash` (~100 tokens)

Hash text

Compute a cryptographic hash of a string.

Returns: Hex digest of the input using the requested algorithm.
Example input: {"text":"hello world","algorithm":"sha256"}
On error, includes hint: `algorithm` must be one of: md5, sha1, sha256, sha384, sha512.

Input parameters:

- `algorithm` (string, required): md5, sha1, sha256, sha384, or sha512
- `text` (string, required)

### `hash_compare` (~127 tokens)

Hash compare

Hash two inputs with the same algorithm and compare them in constant time. Useful for verifying file integrity.

Returns: JSON { match: boolean } computed with a constant-time comparison.
Example input: {"a":"hello","b":"hello","algorithm":"sha256"}
On error, includes hint: `algorithm` (optional, default sha256) must be one of: md5, sha1, sha256, sha384, sha512.

Input parameters:

- `a` (string, required): First input.
- `algorithm` (string): Hash algorithm (default sha256).
- `b` (string, required): Second input.

### `uuid_generate` (~74 tokens)

Generate UUID

Generate one or more v4 UUIDs.

Returns: JSON array of v4 UUID strings.
Example input: {"count":3}
On error, includes hint: `count` must be an integer between 1 and 100.

Input parameters:

- `count` (number): How many to generate (default 1, max 100).

### `password_generate` (~177 tokens)

Generate password

Generate a cryptographically random password. Choose length and character classes.

Returns: Randomly generated password string.
Example input: {"length":20,"uppercase":true,"lowercase":true,"digits":true,"symbols":true,"count":1}
On error, includes hint: `length` 4-256. Enable at least one character class (lowercase/uppercase/digits/symbols).

Input parameters:

- `count` (number): How many passwords to generate (default 1).
- `digits` (boolean): Include digits (default true).
- `length` (number): Password length (default 16).
- `lowercase` (boolean): Include lowercase letters (default true).
- `symbols` (boolean): Include symbols !@#$%^&*()-_=+ (default false).
- `uppercase` (boolean): Include uppercase letters (default true).

### `bcrypt_hash` (~96 tokens)

Bcrypt hash

Hash a password with bcrypt.

Returns: Bcrypt hash string (includes cost + salt).
Example input: {"password":"s3cret!","cost":10}
On error, includes hint: `cost` must be an integer between 4 and 12. Higher cost is exponentially slower.

Input parameters:

- `cost` (number): Bcrypt cost factor (4-12, default 10).
- `password` (string, required): Password to hash.

### `bcrypt_verify` (~103 tokens)

Bcrypt verify

Check whether a password matches a bcrypt hash.

Returns: JSON { match: boolean }.
Example input: {"password":"s3cret!","hash":"$2a$10$abcdefghijklmnopqrstuv"}
On error, includes hint: `hash` must be a full bcrypt string starting with $2a$, $2b$, or $2y$.

Input parameters:

- `hash` (string, required): Bcrypt hash to verify against.
- `password` (string, required): Plaintext password.

### `subnet_calculator` (~143 tokens)

Subnet calculator (IPv4)

Given a CIDR block (e.g. 10.0.0.0/24), return network, broadcast, netmask, first/last host, and host count.

Returns: JSON with network, broadcast, first/last host, host count, and mask for the CIDR.
Example input: {"cidr":"192.168.1.0/24"}
On error, includes hint: `cidr` must be IPv4 in `A.B.C.D/prefix` form, prefix 0-32.

Input parameters:

- `cidr` (string, required): IPv4 CIDR, e.g. 192.168.1.0/24.

### `ip_convert` (~151 tokens)

IPv4 converter

Convert an IPv4 address between dotted-decimal, integer, binary, and hex forms. Accepts any of those as input.

Returns: JSON { decimal, integer, hex, binary } representations of the IPv4 address.
Example input: {"value":"192.168.1.1"}
On error, includes hint: `value` accepts dotted (192.168.0.1), integer (3232235521), 32-bit binary, or 0x-prefixed hex.

Input parameters:

- `value` (string, required): IPv4 in dotted (192.168.0.1), integer (3232235521), binary (32 bits), or hex (0xC0A80001) form.

### `epoch_convert` (~121 tokens)

Convert epoch time

Convert between Unix epoch seconds/milliseconds and ISO 8601. Pass a number to convert to ISO, or an ISO string to convert to epoch.

Returns: JSON with ISO string, epoch seconds, epoch milliseconds, and a UTC-formatted representation.
Example input: {"value":"1700000000"}
On error, includes hint: `value` is a string: either an integer (seconds or ms since epoch) or an ISO 8601 timestamp.

Input parameters:

- `value` (string, required): A number (as string) or an ISO 8601 date string.

### `timezone_convert` (~198 tokens)

Timezone converter

Convert a timestamp between two IANA timezones. Returns the wall-clock time in the target zone.

Returns: JSON { utc, zone, local } with the timestamp rendered in the target IANA timezone.
Example input: {"timestamp":"2026-07-11T12:00:00Z","to":"America/Los_Angeles"}
On error, includes hint: `timestamp` must be ISO 8601 (e.g. 2026-07-11T12:00:00Z); `to` must be an IANA zone like America/New_York.

Input parameters:

- `timestamp` (string, required): ISO 8601 timestamp (e.g. 2025-01-15T14:30:00Z or 2025-01-15T09:30:00-05:00).
- `to` (string, required): Target IANA timezone (e.g. America/New_York, Asia/Tokyo).

### `date_diff` (~134 tokens)

Date difference

Compute the difference between two ISO 8601 timestamps in days, hours, minutes, and seconds.

Returns: JSON with milliseconds, totalSeconds/Minutes/Hours/Days, and a { days, hours, minutes, seconds } breakdown.
Example input: {"from":"2026-01-01T00:00:00Z","to":"2026-07-11T12:00:00Z"}
On error, includes hint: Both `from` and `to` must be ISO 8601 timestamps.

Input parameters:

- `from` (string, required): Start ISO timestamp.
- `to` (string, required): End ISO timestamp.

### `cron_validate` (~117 tokens)

Cron expression validator

Validate a standard 5-field cron expression (minute hour day month weekday). Returns a human-readable summary and any parse error.

Returns: JSON { valid: boolean, nextRuns?: string[], error?: string }.
Example input: {"expression":"*/5 * * * *"}
On error, includes hint: `expression` must be a 5-field cron (minute hour dom month dow). 6-field / Quartz syntax is not supported.

Input parameters:

- `expression` (string, required): Cron expression, e.g. '*/15 * * * *'.

### `regex_test` (~128 tokens)

Test regex

Test a regular expression against text. Returns all matches and capture groups.

Returns: JSON { matches: string[], count } of matches for the pattern.
Example input: {"pattern":"\\d+","flags":"g","text":"order 42 shipped on day 7"}
On error, includes hint: `pattern` is a JS RegExp source (double-escape backslashes in JSON). `flags` uses standard flags like g, i, m, s.

Input parameters:

- `flags` (string): e.g. "gi"
- `pattern` (string, required)
- `text` (string, required)

### `text_diff` (~95 tokens)

Text diff

Compute a line-level diff between two strings. Returns a unified-style patch and per-line change list.

Returns: JSON line-diff with { added, removed, unchanged } arrays.
Example input: {"a":"line 1\nline 2\nline 3","b":"line 1\nline 2 changed\nline 3"}

Input parameters:

- `a` (string, required): Original text.
- `b` (string, required): Modified text.

### `list_compare` (~129 tokens)

List comparison

Compare two newline-separated lists. Returns union, intersection, only-in-A, and only-in-B.

Returns: JSON { union, intersection, onlyInA, onlyInB } arrays.
Example input: {"a":"apple\nbanana\ncherry","b":"banana\ncherry\ndate"}

Input parameters:

- `a` (string, required): First list, one item per line.
- `b` (string, required): Second list, one item per line.
- `caseInsensitive` (boolean): Compare case-insensitively (default false).
- `trim` (boolean): Trim each line before comparing (default true).

### `color_convert` (~131 tokens)

Color converter

Convert a color between hex, rgb, and hsl. Accepts inputs like '#3B82F6', 'rgb(59,130,246)', or 'hsl(217,91%,60%)'.

Returns: JSON with hex, rgb, and hsl representations of the color.
Example input: {"color":"#3b82f6"}
On error, includes hint: `color` accepts #rgb, #rrggbb, rgb(r,g,b), or hsl(h,s%,l%).

Input parameters:

- `color` (string, required): Color in hex, rgb(), or hsl() form.

### `contrast_check` (~115 tokens)

WCAG contrast check

Compute the WCAG contrast ratio between two hex colors and report AA/AAA pass/fail for normal and large text.

Returns: JSON { ratio, AA, AAA, AALarge, AAALarge } for the two colors.
Example input: {"foreground":"#ffffff","background":"#3b82f6"}
On error, includes hint: Both colors must be hex (#rgb or #rrggbb).

Input parameters:

- `background` (string, required): Background color, hex.
- `foreground` (string, required): Foreground color, hex.

### `css_gradient` (~167 tokens)

CSS gradient builder

Build a CSS linear or radial gradient string from color stops.

Returns: CSS gradient string (linear or radial).
Example input: {"type":"linear","angle":45,"stops":["#3b82f6","#8b5cf6"]}
On error, includes hint: `type` is 'linear' or 'radial'; provide at least 2 color `stops`.

Input parameters:

- `angle` (number): Angle in degrees for linear gradients (default 90). Ignored for radial.
- `stops` (array, required): Color stops, e.g. ['#3B82F6', '#8B5CF6 50%', '#EC4899'] — hex, rgb(), hsl(), or named colors, with optional percentage.
- `type` (string, required): Gradient type.

### `random_name` (~47 tokens)

Random name generator

Generate random human names.

Returns: JSON array of random human name strings.
Example input: {"count":3}

Input parameters:

- `count` (number): Number of names to generate (default 5).

### `random_email` (~77 tokens)

Random email generator

Generate random-looking (non-deliverable) test email addresses.

Returns: JSON array of random email address strings.
Example input: {"count":3,"domain":"example.com"}

Input parameters:

- `count` (number): Number of emails (default 5).
- `domain` (string): Fixed domain for all emails (e.g. 'example.com').

### `random_number` (~102 tokens)

Random number generator

Generate cryptographically random numbers in a range.

Returns: JSON array of generated numbers.
Example input: {"min":1,"max":100,"count":5,"mode":"integer"}

Input parameters:

- `count` (number): Number of values (default 1).
- `max` (number, required): Maximum value (inclusive for integers, exclusive upper bound for floats).
- `min` (number, required): Minimum value (inclusive).
- `mode` (string): Result type (default 'integer').

### `lorem_ipsum` (~59 tokens)

Lorem ipsum generator

Generate placeholder lorem ipsum text.

Returns: Lorem ipsum text of the requested size.
Example input: {"unit":"paragraphs","count":2}

Input parameters:

- `count` (number, required): How many units to generate.
- `unit` (string, required): Unit type.

### `emi_calculate` (~103 tokens)

EMI calculator

Compute the equated monthly installment (EMI) for a loan.

Returns: JSON { emi, totalInterest, totalPayment } for the loan.
Example input: {"principal":500000,"annualRatePercent":8.5,"months":240}

Input parameters:

- `annualRatePercent` (number, required): Annual interest rate as a percent, e.g. 7.5.
- `months` (integer, required): Loan term in months.
- `principal` (number, required): Loan principal.

### `simple_interest` (~89 tokens)

Simple interest calculator

Compute simple interest: I = P × r × t.

Returns: JSON { interest, total } computed as P·r·t.
Example input: {"principal":10000,"annualRatePercent":5,"years":3}

Input parameters:

- `annualRatePercent` (number, required): Annual interest rate as a percent.
- `principal` (number, required): Principal amount.
- `years` (number, required): Time in years.

### `compound_interest` (~121 tokens)

Compound interest calculator

Compute compound interest: A = P(1 + r/n)^(nt).

Returns: JSON { interest, total } computed as P(1+r/n)^(nt).
Example input: {"principal":10000,"annualRatePercent":5,"years":10,"compoundsPerYear":12}

Input parameters:

- `annualRatePercent` (number, required): Annual interest rate as a percent.
- `compoundsPerYear` (integer): Compounding periods per year (default 12).
- `principal` (number, required): Principal amount.
- `years` (number, required): Time in years.

### `bmi_calculate` (~108 tokens)

BMI calculator

Calculate Body Mass Index in metric (kg/cm) or imperial (lb/in) units.

Returns: JSON { bmi, category } (Underweight / Normal / Overweight / Obese).
Example input: {"weight":70,"height":175,"units":"metric"}

Input parameters:

- `height` (number, required): Height (cm for metric, inches for imperial).
- `units` (string): Unit system (default 'metric').
- `weight` (number, required): Weight (kg for metric, lb for imperial).

### `list_calculators` (~141 tokens)

List RedBison calculators

List the calculators that run_calculator can execute (finance, health, maths, statistics, construction, science, everyday and engineering), with each one's inputs, units, defaults and an example. Filter with an optional search query.

Returns: JSON { total, calculators[] } where each has { id, title, summary, url, inputs (JSON Schema per field), example }.
Example input: {"query":"mortgage","limit":5}

Input parameters:

- `limit` (integer): Max results (default 25).
- `query` (string): Optional words to filter by, e.g. 'mortgage', 'beam', 'wire size', 'percentage'.

### `run_calculator` (~177 tokens)

Run a RedBison calculator

Run any RedBison calculator by id with named inputs and get the result as JSON: mortgages and loans, savings and investing, pay and tax, body and fitness, maths, statistics, geometry, construction, science and engineering (beams, bolts, wire size, PCB traces, pipe flow, rafters, sheet metal and more). Call list_calculators first to see ids, inputs and units.

Returns: JSON { id, title, url, inputs, result } with the calculator's outputs.
Example input: {"id":"percentage-calculator","inputs":{}}

Input parameters:

- `id` (string, required): Calculator id from list_calculators, e.g. 'mortgage-calculator' or 'beam-deflection-calculator'.
- `inputs` (object): Named inputs for that calculator. Omitted fields use the calculator's defaults.

### `ascii_art_text` (~226 tokens)

ASCII art text (FIGlet)

Render text as a FIGlet ASCII art banner in one of 7 bundled fonts (Standard, Slant, Small, Big, Doom, ANSI Shadow, Mini), optionally wrapped at a column width and inside code comment markers. Printable ASCII only. The page at redbison.dev/ascii-art-text-generator has more fonts.

Returns: Text: the banner (show it in a monospace code block). structuredContent { art, font, lines, columns, unsupported[] }.
Example input: {"text":"Hello","font":"Slant","layout":"default","width":80,"comment":"none"}

Input parameters:

- `comment` (string): Wrap the banner in // , # , /* */ , <!-- --> or -- comment markers.
- `font` (string): FIGlet font name.
- `layout` (string): Horizontal letter spacing: the font default, full width, fitted (touching) or smushed.
- `text` (string, required): Text to render. Line breaks start a new banner row.
- `width` (integer): Wrap at this many columns (0 for no wrapping).

### `barcode_check_digit` (~195 tokens)

Barcode check digit (EAN/UPC/GTIN)

Compute or validate the GS1 mod-10 check digit of an EAN-8, UPC-A, EAN-13 or ITF-14 (GTIN-8/12/13/14) number. Give the digits without the check digit to compute it, or the full code to validate it.

Returns: JSON { digits, checkDigit, fullCode, valid, gtin14, formats[] }. valid is true/false when a full code was checked and null when the check digit was computed.
Example input: {"code":"400638133393","mode":"compute"}

Input parameters:

- `code` (string, required): Digits of the barcode number. Spaces and dashes are ignored.
- `mode` (string): auto (default): full GTIN lengths 8, 12, 13 and 14 are validated, 7 and 11 digits get a check digit computed. compute or validate forces one reading.

### `chmod_convert` (~284 tokens)

chmod permission converter

Convert Unix permissions between octal (755, 4755), symbolic (rwxr-xr-x) and ls -l strings, or apply a chmod expression such as 'go-w,u+x' to a starting mode. Explains each class, setuid/setgid/sticky bits and risky modes, and gives umask defaults.

Returns: JSON { octal, symbolic, ls, description[], warnings[], command, symbolicArg, umaskDefaults{ umask, newFile, newDirectory } }.
Example input: {"mode":"rwxr-x---"}
On error, includes hint: Use 1-4 octal digits, nine rwx characters (optionally with a leading file type), or a symbolic expression like u+x,go-w.

Input parameters:

- `isDirectory` (boolean): Treat the target as a directory (affects X and the ls -l type). Default false.
- `mode` (string, required): Octal (644), symbolic or ls -l (-rwsr-xr-x), or a chmod expression (u+x, a=rX) applied to start.
- `start` (string): Starting octal mode for expressions. Default 644 for files, 755 for directories.
- `umask` (string): umask in octal, used for expressions without u/g/o/a and for new-file defaults. Default 022.

### `color_palette` (~414 tokens)

Color palette generator

Build a harmonious color palette from one base color (complementary, analogous, triadic, split-complementary, tetradic, square, monochromatic or tints and shades). Returns each color as HEX, RGB, HSL and OKLCH with WCAG contrast against white and black, an 11-step 50-950 scale of the base, and ready-to-paste CSS variables and Tailwind config. Same maths as https://redbison.dev/color-palette-generator.

Returns: JSON { base, rule, wheel, colors[] { role, hex, rgb, hsl, oklch, contrastOnWhite, contrastOnBlack, bestTextColor, wcagNormalText }, scale { '50'..'950': hex }, baseScaleStep, css, tailwindV3, tailwindV4 }.
Example input: {"base":"#3b82f6","rule":"triadic","wheel":"rgb","name":"brand"}
On error, includes hint: Pass the base color as hex like #3b82f6 (rgb(), hsl(), oklch() and CSS names also work). rule must be one of complementary, analogous, triadic, split-complementary, tetradic, square, monochromatic, shades.

Input parameters:

- `base` (string, required): Base color as hex (#3b82f6), rgb(59 130 246), hsl(217 91% 60%), oklch(62% 0.19 260) or a CSS color name.
- `name` (string): Name used in the CSS and Tailwind exports, e.g. 'brand'. Default 'brand'.
- `rule` (string): Harmony rule. Default 'complementary'.
- `wheel` (string): Color wheel for hue rotation: 'rgb' (screen/HSL wheel, default), 'ryb' (approximate painter's wheel, red opposite green) or 'oklch' (perceptual, keeps lightness).

### `cron_build` (~433 tokens)

Cron expression builder

Build a standard five-field cron expression from plain choices (every N minutes, hourly, daily, weekly, monthly, yearly) or explain an existing one. Returns the expression, an English description, the next run times in a time zone, and the same schedule for crontab, Kubernetes, GitHub Actions, Quartz and AWS EventBridge.

Returns: JSON { expression, description, nextRuns[], timezone, platforms[{ id, name, value, notes[] }], warnings[] }. value is null on Quartz/EventBridge when both day fields are restricted.
Example input: {"frequency":"weekly","daysOfWeek":["mon","wed","fri"],"hours":[9],"minute":30,"timezone":"America/New_York"}
On error, includes hint: Give either plain choices (frequency plus minute/hours/days) or a five-field expression. Days of week accept names or 0-6 with 0 = Sunday.

Input parameters:

- `count` (integer): How many upcoming runs to list. Default 5.
- `daysOfMonth` (array): For monthly or yearly: days of the month, e.g. [1, 15].
- `daysOfWeek` (array): For weekly: days as names (mon, fri) or numbers 0-6 with 0 = Sunday.
- `expression` (string): An existing five-field cron expression to explain and translate instead of building one.
- `frequency` (string): How often to run. Ignored when expression is given. Default daily.
- `hours` (array): Hours of the day in 24-hour time, e.g. [9] or [9, 17]. Default [0].
- `interval` (integer): For minutes: every N minutes (default 5). For hourly: every N hours (default 1).
- `minute` (integer): Minute past the hour, 0-59. Default 0.
- `months` (array): For yearly: months 1-12.
- `timezone` (string): IANA time zone for the next run times, e.g. Europe/London. Default UTC.

### `css_beautify` (~258 tokens)

CSS / SCSS / Less beautify, minify and sort

Pretty-print or minify CSS, SCSS or Less, optionally sorting declarations alphabetically. Sorting is cascade-safe: a shorthand and its longhands (border / border-top, margin / margin-top, font / line-height) keep their original relative order. Minify removes comments and whitespace only; values such as 0px or colours are never rewritten.

Returns: Text: the stylesheet. structuredContent { code, movedDeclarations, warnings[] }.
Example input: {"css":".a{z-index:1;color:red;border-top:1px solid;border:0}","mode":"beautify","syntax":"css","sort":true,"indent":2}
On error, includes hint: Unbalanced braces or an unterminated string or comment are reported as errors.

Input parameters:

- `css` (string, required): Stylesheet source.
- `indent` (integer): Spaces per indent level when beautifying (0 = tabs).
- `mode` (string): beautify = one declaration per line, minify = smallest output.
- `sort` (boolean): Sort declarations inside each rule alphabetically (vendor-prefixed copies first, override pairs kept in order).
- `syntax` (string): Input syntax; scss and less also accept // line comments.

### `curl_to_code` (~248 tokens)

cURL to code

Convert a curl command (bash/zsh quoting, $'...' strings, \ line continuations, or Windows cmd ^ escaping from 'Copy as cURL') into JavaScript fetch, Node Axios, Python requests, Go net/http or PHP ext-curl. Follows curl semantics: -d implies POST with application/x-www-form-urlencoded, repeated -d joins with &, --json sets JSON headers, -G moves data to the query string, -F is multipart, -u is Basic auth, no redirects without -L. Nothing is sent over the network.

Returns: Text: the generated code, followed by notes on anything not translated. structuredContent { code, method, url, headers[{ name, value }], hasBody, warnings[] }.
Example input: {"command":"curl -X POST https://api.example.com/v1/items -H 'Content-Type: application/json' -d '{\"name\":\"Ada\"}'","target":"python"}
On error, includes hint: Send the command exactly as copied, including quotes. The word curl must be present.

Input parameters:

- `command` (string, required): The full curl command line.
- `target` (string): Language/library to generate.

### `docker_run_to_compose` (~218 tokens)

docker run to Compose converter

Convert one or more 'docker run' commands into a Compose file (services, ports, volumes, environment, networks, healthcheck, GPUs, limits), or convert a compose.yaml back into docker run commands. Unsupported flags are reported as warnings.

Returns: run_to_compose: JSON { compose (YAML text), services[], warnings[] }. compose_to_run: JSON { commands[], warnings[] }.
Example input: {"input":"docker run -d --name web -p 8080:80 -v html:/usr/share/nginx/html --restart unless-stopped nginx:alpine"}
On error, includes hint: Each command must start with 'docker run' (or 'docker container run'). Separate several commands with new lines.

Input parameters:

- `direction` (string): Default run_to_compose.
- `input` (string, required): docker run command(s), or compose YAML when direction is compose_to_run.
- `project` (string): Compose project name used to prefix volume and network names in compose_to_run. Default myproject.

### `gitignore_generate` (~276 tokens)

.gitignore generator

Combine .gitignore templates (based on github/gitignore) for languages, frameworks, tools, editors and operating systems into one deduplicated file, optionally test paths against it. Template ids: node, python, django, jupyter, java, maven, gradle, kotlin, android, go, rust, ruby, rails, php, laravel, dotnet, c, cpp, swift, flutter, elixir, scala, r, nextjs, terraform, unity, docker, secrets, vscode, jetbrains, visualstudio, eclipse, vim, emacs, sublime, macos, windows, linux.

Returns: JSON { content (.gitignore text), unknownTemplates[], duplicatesRemoved, tests[{ path, ignored, rule{pattern,line,negate}, via }] }.
Example input: {"templates":["node","macos","vscode"],"testPaths":[".env","node_modules/x.js",".vscode/settings.json"]}

Input parameters:

- `extra` (string): Extra lines to append, one pattern per line.
- `templates` (array, required): Template ids or names, e.g. ['node', 'python', 'macos', 'vscode'].
- `testPaths` (array): Repository-relative paths to check, e.g. ['.env', 'dist/']. End with / for a directory.

### `hmac` (~368 tokens)

HMAC signature

Compute an HMAC (RFC 2104) with SHA-256, SHA-1, SHA-384 or SHA-512 and return it in hex, Base64 and Base64url. Optionally build a GitHub, Stripe or Slack webhook signature, and check an expected signature with a constant-time comparison.

Returns: JSON { algorithm, hex, base64, base64url, bits, key_bytes, message_bytes, signed_string, header, match } where match is null unless `expected` was given.
Example input: {"message":"The quick brown fox jumps over the lazy dog","key":"key","algorithm":"SHA-256"}
On error, includes hint: `algorithm` is SHA-256, SHA-1, SHA-384 or SHA-512; `key_encoding` and `message_encoding` are utf8, hex or base64; `preset` is plain, github, stripe or slack.

Input parameters:

- `algorithm` (string): Hash function (default SHA-256). Webhook presets always use SHA-256.
- `expected` (string): Optional signature to verify, in hex or Base64, with or without a sha256= / v0= / v1= prefix.
- `key` (string, required): The secret key.
- `key_encoding` (string): How the key is written (default utf8).
- `message` (string, required): The message or raw request body to sign.
- `message_encoding` (string): How the message is written (default utf8). Ignored for webhook presets.
- `preset` (string): plain (default), github (X-Hub-Signature-256), stripe (t.payload) or slack (v0:ts:body).
- `timestamp` (string): Unix timestamp used by the stripe and slack presets.

### `http_status` (~204 tokens)

HTTP status code lookup

Look up HTTP status codes: meaning, defining RFC section (RFC 9110 and others from the IANA registry), when to send it and common pitfalls. Pass a code (404), a class (5xx) or words (rate limit). Unofficial nginx and Cloudflare codes are included and flagged.

Returns: JSON { query, count, results[] } where each result has { code, name, class, spec, official, deprecated, cacheableByDefault, summary, usage, note }, plus unknownCode text when a 3-digit code is not registered.
Example input: {"query":"429"}

Input parameters:

- `includeUnofficial` (boolean): Include vendor codes such as nginx 499 and Cloudflare 522. Default true.
- `limit` (integer): Maximum results to return. Default 20.
- `query` (string, required): A status code such as 429, a class such as 3xx, or search words such as 'redirect keep method'.

### `js_beautify` (~302 tokens)

JavaScript / TypeScript beautify or minify

Format JavaScript, TypeScript or JSX with js-beautify, or minify JavaScript/TypeScript by removing comments and whitespace (no renaming, no rewriting; line breaks are kept where automatic semicolon insertion needs them). The output is re-lexed and compared token by token with the input.

Returns: Text: the formatted or minified code. structuredContent { code, mode, inputBytes, outputBytes, savedPercent, warnings[] }.
Example input: {"code":"function add(a,b){return a+b}","mode":"beautify","language":"javascript","indent":2,"brace_style":"collapse","keep_license":true}
On error, includes hint: Pass the whole file as `code`. An unterminated string, comment or regex is reported with its line and column.

Input parameters:

- `brace_style` (string): Brace placement when beautifying: collapse = K&R (same line), expand = Allman (own line).
- `code` (string, required): Source code to format or minify.
- `indent` (integer): Spaces per indent level when beautifying (0 = tabs).
- `keep_license` (boolean): When minifying, keep /*! ... */ and @license comments.
- `language` (string): Language of the code. TypeScript gets generic and optional-marker fix-ups; JSX cannot be minified.
- `mode` (string): beautify = pretty-print, minify = strip comments and whitespace.

### `json_schema_validate` (~330 tokens)

JSON Schema validate or generate

Validate a JSON document against a JSON Schema (drafts 06, 07, 2019-09 and 2020-12, via Ajv, all errors reported with JSON Pointer paths and formats such as date-time, email, uuid, ipv4/ipv6 checked), or infer a starter schema from sample JSON. Leave `schema` empty to infer.

Returns: Validate: text summary plus structuredContent { mode, valid, draft, errors[{ path, message, keyword, schemaPath, params }], warnings[] }. Infer: the schema as JSON text and structuredContent { mode, schema }.
Example input: {"data":"{\"name\":\"Ada\",\"age\":-1}","schema":"{\"type\":\"object\",\"properties\":{\"age\":{\"type\":\"integer\",\"minimum\":0}},\"required\":[\"name\",\"email\"]}","draft":"auto"}
On error, includes hint: Both `data` and `schema` are JSON text, not objects. Send an empty `schema` to generate one from `data`.

Input parameters:

- `data` (string, required): The JSON document (as text) to validate, or the sample to infer a schema from.
- `draft` (string): Draft for validation; auto reads $schema and defaults to 2020-12.
- `infer_draft` (string): Draft of the generated schema when inferring.
- `infer_required` (string): When inferring: all = keys present in every sampled object are required.
- `schema` (string): The JSON Schema as text. Empty = infer a schema from `data` instead of validating.

### `markdown_table` (~269 tokens)

Markdown table from CSV, TSV or Markdown

Turn CSV, TSV (spreadsheet paste) or an existing Markdown table into a GitHub Flavored Markdown table. The first row is the header; pipes are escaped as \|, line breaks inside cells become <br>, and columns can be padded so the pipes line up (CJK-width aware).

Returns: Text: the Markdown table. structuredContent { markdown, rows (including header), columns, detected ('csv' | 'tsv' | 'markdown' | 'other'), errors[] }.
Example input: {"text":"Item,Qty,Price\nApple,3,$1.20\nKiwi,12,$0.50","align":"none","pretty":true,"outer_pipes":true,"bold_header":false}
On error, includes hint: Put the header in the first row. Quote CSV fields that contain commas or line breaks.

Input parameters:

- `align` (string): Alignment for every column (none keeps alignment from a Markdown input).
- `bold_header` (boolean): Wrap header cells in **bold**.
- `outer_pipes` (boolean): Start and end each row with |.
- `pretty` (boolean): Pad cells so the columns line up in plain text.
- `text` (string, required): CSV, TSV or Markdown table text. The delimiter is detected automatically.

### `mime_lookup` (~147 tokens)

MIME type lookup

Find the MIME (media) type for a file extension or file name, or the extensions for a MIME type. Returns the type, whether it is IANA-registered, aliases, notes and the Content-Type header to send.

Returns: JSON { query, matchedBy: 'extension'|'mime'|'text', count, results[] } with { mime, extensions[], name, category, registered, aliases[], spec, note, contentType }.
Example input: {"query":"woff2"}

Input parameters:

- `query` (string, required): An extension (webp or .webp), a file name (report.docx, archive.tar.gz) or a MIME type (application/json, image/*).

### `morse_code` (~246 tokens)

Morse code translator

Translate text to International Morse code (ITU-R M.1677-1) or Morse back to text. Letters are separated by spaces and words by ' / '. Wrap prosigns in angle brackets (<SOS>, <AR>, <SK>). Also returns the transmission time at a given speed in words per minute, with optional Farnsworth spacing. Same rules as redbison.dev/morse-code-translator.

Returns: Text: the Morse or decoded text. structuredContent { direction, morse | text, unsupported[] | unknownCodes[], durationSeconds, unitMs }.
Example input: {"input":"SOS at 18 wpm","direction":"encode","wpm":18}

Input parameters:

- `direction` (string): auto decodes when the input contains only dots, dashes, slashes and spaces.
- `effectiveWpm` (number): Farnsworth overall speed in wpm, lower than wpm. Omit for standard spacing.
- `input` (string, required): Text to encode, or Morse to decode (dots and dashes; '/' or two spaces between words).
- `wpm` (number): Character speed in words per minute (PARIS standard) for the timing figures.

### `nato_phonetic` (~266 tokens)

NATO phonetic alphabet

Spell text with the ICAO/NATO radiotelephony alphabet (Alfa, Bravo, Charlie...), with ICAO number words (Tree, Fower, Fife, Niner) or plain ones, optional Capital/Lowercase markers for passwords, or decode code words back to text. Same rules as redbison.dev/nato-phonetic-alphabet.

Returns: Text: code words, ' / ' between input words. structuredContent { spelled, tokens[{char, word, pronunciation}] } or, for decode, { text, unknown[] }.
Example input: {"text":"Gate B12","direction":"spell","spelling":"icao","digits":"icao","markCase":false}

Input parameters:

- `digits` (string): icao says Tree, Fower, Fife, Niner; plain says Three, Four, Five, Nine.
- `direction` (string): spell turns text into code words; decode turns code words back into text.
- `markCase` (boolean): Prefix each letter with Capital or Lowercase.
- `spelling` (string): icao prints Alfa and Juliett as published; common prints Alpha and Juliet.
- `text` (string, required): Text to spell, or code words to decode (e.g. 'Alfa Bravo / Charlie').

### `password_strength` (~256 tokens)

Password strength

Estimate how guessable a password is with zxcvbn pattern matching (dictionary words, common passwords, keyboard walks, sequences, dates, l33t). Returns a 0-4 score, estimated guesses, entropy in bits, crack times for online and offline attacks, warnings, suggestions and NIST SP 800-63B-4 length checks. The password is not echoed back.

Returns: JSON { score 0-4, label, length, guesses, guesses_log10, entropy_bits, character_pool_entropy_bits, character_classes[], crack_times[{scenario, seconds, display}], warning, suggestions[], patterns[{pattern, start, end, description}], nist_sp800_63b{...} }. The password itself is never included.
Example input: {"password":"Tr0ub4dor&3","user_inputs":["alice"]}
On error, includes hint: `password` must be a string of at most 256 characters; `user_inputs` is an optional array of strings.

Input parameters:

- `password` (string, required): The password to analyse (up to 256 characters).
- `user_inputs` (array): Optional personal words (name, username, site name) that make the password easier to guess if it contains them.

### `readability` (~301 tokens)

Readability scores

Score English text with Flesch Reading Ease, Flesch-Kincaid Grade, Gunning Fog, SMOG, Coleman-Liau and the Automated Readability Index, and list hard sentences, passive voice, -ly adverbs and wordy phrases with plainer alternatives. Syllables are estimated with rules plus an exception list. Same rules as redbison.dev/readability-checker.

Returns: JSON { counts, wordsPerSentence, syllablesPerWord, fleschReadingEase, fleschBand, fleschKincaidGrade, gunningFog, smog, smogShortSample, colemanLiau, automatedReadabilityIndex, averageGrade, hardSentences, veryHardSentences, passiveVoice[], adverbs[], plainerWords[{found,try}], hardest[{sentence,words,grade,level}] }.
Example input: {"text":"The committee utilized a methodology that was developed in order to facilitate a comprehensive assessment of the program. We read it twice.","lineBreaksEndSentences":true,"maxSentences":5}

Input parameters:

- `lineBreaksEndSentences` (boolean): Treat each line break as a sentence end (true for headings and lists; false for hard-wrapped plain text).
- `maxSentences` (integer): How many hard sentences to list, hardest first.
- `text` (string, required): English text to score. 100+ words gives stable results; SMOG expects 30 sentences.

### `redirect_rules` (~274 tokens)

Redirect rules generator

Generate 301/302/307/308 redirect rules for Apache .htaccess (mod_rewrite), nginx, Netlify _redirects or vercel.json from a list of 'source destination [code]' lines. A source ending in /* moves a whole folder. Also checks for loops, chains and duplicates and can add HTTPS and www/non-www rules.

Returns: JSON { platform, config (file text), ruleCount, issues[{ line, level, message }], notes[] }.
Example input: {"rules":"/old-page /new-page\n/blog/* /news/:splat 301","platform":"nginx"}

Input parameters:

- `canonicalHost` (string): Redirect the other host variant to www or to the bare domain.
- `defaultCode`: Status code for lines without one. Default 301.
- `domain` (string): Apex domain for host rules, e.g. example.com.
- `forceHttps` (boolean): Add an HTTP to HTTPS redirect (Apache, nginx).
- `keepQuery` (boolean): Keep the incoming query string. Default true.
- `platform` (string, required): Target server or host.
- `rules` (string, required): One redirect per line: '/old /new', '/old /new 302' or '/blog/* /news/:splat'. Destinations may be absolute URLs.

### `toml_convert` (~280 tokens)

TOML / JSON / YAML convert

Convert between TOML 1.0, JSON and YAML, validating the input. TOML dates become RFC 3339 strings in JSON; nulls are dropped when writing TOML (it has no null) and reported; integers beyond 2^53 are kept exact; inf and nan become strings in JSON. Use from=toml,to=toml to validate and normalise a TOML file.

Returns: Text: the converted document. structuredContent { output, warnings[] } where warnings list dropped nulls, large integers and non-finite numbers.
Example input: {"text":"[package]\nname = \"demo\"\nversion = \"0.1.0\"\n\n[dependencies]\nserde = \"1.0\"","from":"toml","to":"json","indent":2}
On error, includes hint: TOML output needs an object at the top level; wrap arrays in a key.

Input parameters:

- `detect_dates` (boolean): When writing TOML, turn RFC 3339 date/date-time strings into native TOML dates.
- `from` (string): Input format.
- `indent` (integer): Indent for JSON and YAML output.
- `sort_keys` (boolean): Sort keys alphabetically.
- `text` (string, required): The document to convert.
- `to` (string): Output format.

### `user_agent_parse` (~195 tokens)

User-Agent parser

Parse a User-Agent header into browser, engine, OS, device type, vendor, model and CPU (ua-parser-js), and detect search, AI, social, SEO and monitoring bots and HTTP libraries. Notes explain User-Agent reduction limits such as Windows 11 reporting as Windows NT 10.0.

Returns: JSON { summary, browser{name,version,major}, engine{name,version}, os{name,version}, device{type,vendor,model}, cpu{architecture}, isBot, bot{name,category,owner}|null, notes[] }.
Example input: {"userAgent":"Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1"}

Input parameters:

- `userAgent` (string, required): The full User-Agent header value.

### `utm_build` (~334 tokens)

Build a UTM campaign URL

Add Google Analytics UTM parameters (utm_source, utm_medium, utm_campaign, utm_id, utm_term, utm_content) to a landing page URL. Keeps existing query parameters and the #fragment, lowercases values by default, and predicts the GA4 default channel group.

Returns: JSON { url, params, predictedChannel, warnings[] }: the tagged URL, the UTM values used, the likely GA4 default channel group (approximation) and any naming warnings.
Example input: {"url":"https://example.com/pricing?plan=pro","source":"newsletter","medium":"email","campaign":"October Launch","content":"hero_button"}

Input parameters:

- `campaign` (string): utm_campaign: campaign, product or promotion name.
- `content` (string): utm_content: which link or creative, e.g. header_button.
- `id` (string): utm_id: campaign ID used for GA4 data import.
- `lowercase` (boolean): Lowercase every value (default true; GA4 values are case sensitive).
- `medium` (string): utm_medium: marketing medium, e.g. email, social, cpc, referral, affiliate.
- `source` (string, required): utm_source: who sends the traffic, e.g. newsletter, linkedin, google.
- `spaces` (string): How to write spaces inside values: dash (default), underscore, plus (+) or keep (%20).
- `term` (string): utm_term: paid search keyword.
- `url` (string, required): Landing page URL. https:// is added if the scheme is missing.

### `word_count` (~262 tokens)

Word and character count

Count words, characters (with and without spaces), sentences, paragraphs and lines in text, estimate reading and speaking time, list the most frequent words and check the text against common platform limits (X post weighted length, Bluesky, LinkedIn, SMS segments, meta description). Same rules as redbison.dev/word-counter.

Returns: JSON { words, characters, charactersNoSpaces, sentences, paragraphs, lines, uniqueWords, utf8Bytes, averageWordLength, averageSentenceLength, readingTime, readingSeconds, speakingTime, speakingSeconds, topWords[{word,count,percent}], platformLimits[{platform,limit,used,remaining,over,detail}] }.
Example input: {"text":"Short sentences help. Long ones, full of clauses that wander, do not.","readingWpm":238,"speakingWpm":150,"topWords":5}

Input parameters:

- `readingWpm` (number): Silent reading speed in words per minute (238 is the adult non-fiction average).
- `speakingWpm` (number): Speaking speed in words per minute for the speech-time estimate.
- `text` (string, required): The text to count.
- `topWords` (integer): How many frequent words to return, stop words excluded. 0 to skip.

### `help` (~175 tokens)

Help for RedBison MCP tools

Explain how to use any RedBison MCP tool, with its input schema, a sample input and the sample output it produces. Call with no arguments for the list of tools; pass `tool` for one tool, and `calculator` with tool 'run_calculator' for one calculator.

Returns: JSON with a tool's { usage, returns, inputSchema, sampleInput, sampleOutput }, or the list of tools when called with no arguments.
Example input: {"tool":"list_calculators"}

Input parameters:

- `calculator` (string): With tool 'run_calculator': a calculator id such as 'mortgage-calculator' for its inputs and a worked sample.
- `tool` (string): Tool name, e.g. 'run_calculator', 'hash' or 'list_calculators'. Omit to list all tools.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-redbison-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 65
- 2026-11-01: 65
- 2026-10-31: 64
- 2026-10-30: 64

## Common questions

### What is the RedBison MCP server?

RedBison is an MCP server listed in the public MCP registry as dev.redbison/mcp. 500+ free tools over MCP: dev, text and security utilities, 230+ calculators. No sign-up. This page covers its hosted endpoint (https://mcp.redbison.dev).

### Is the RedBison MCP server safe to use?

RedBison scores 67 out of 100 on VerifyMCP. 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 RedBison MCP server expose?

RedBison exposes 82 tools: search_tools, get_tool, list_categories, health, base64_encode, and 77 more. Their descriptions and schemas cost roughly 12,539 tokens of context every time the server is loaded.

### Does the RedBison MCP server require authentication?

No. We connected to RedBison without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RedBison MCP server still maintained?

RedBison is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.redbison.dev/
- Website: https://redbison.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-redbison-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-redbison-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-redbison-mcp/mcp
