RedBison
REMOTE · MCP.REDBISON.DEV
500+ free tools over MCP: dev, text and security utilities, 230+ calculators. No sign-up.
Available components
Last scanned (2 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 83 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
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 64
First indexed and scored.
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 5 Nov 2026 · Probed https://mcp.redbison.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.redbison.dev | CN=YR1,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | RSA 2048 | SHA256-RSA | 65c812375b17171f86cbff58b24d14ae608 |
| SANs: mcp.redbison.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.redbison.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| redbison.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.redbison.dev | Verified | 200 | |
| http (plaintext) | http://mcp.redbison.dev | HTTPS enforced | 308 | https://mcp.redbison.dev/ |
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 →
morse_code Morse code translator ~246
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}
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
nato_phonetic NATO phonetic alphabet ~266
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}
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Text to spell, or code words to decode (e.g. 'Alfa Bravo / Charlie'). |
No output schema declared.
No examples provided.
password_generate Generate password ~177
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
password_strength Password strength ~256
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.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | yes | 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. |
No output schema declared.
No examples provided.
random_email Random email generator ~77
Generate random-looking (non-deliverable) test email addresses. Returns: JSON array of random email address strings. Example input: {"count":3,"domain":"example.com"}
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of emails (default 5). |
| domain | string | – | Fixed domain for all emails (e.g. 'example.com'). |
No output schema declared.
No examples provided.
random_name Random name generator ~47
Generate random human names. Returns: JSON array of random human name strings. Example input: {"count":3}
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of names to generate (default 5). |
No output schema declared.
No examples provided.
random_number Random number generator ~102
Generate cryptographically random numbers in a range. Returns: JSON array of generated numbers. Example input: {"min":1,"max":100,"count":5,"mode":"integer"}
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of values (default 1). |
| max | number | yes | Maximum value (inclusive for integers, exclusive upper bound for floats). |
| min | number | yes | Minimum value (inclusive). |
| mode | string | – | Result type (default 'integer'). |
No output schema declared.
No examples provided.
readability Readability scores ~301
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}
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | English text to score. 100+ words gives stable results; SMOG expects 30 sentences. |
No output schema declared.
No examples provided.
redirect_rules Redirect rules generator ~274
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"}
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Target server or host. |
| rules | string | yes | One redirect per line: '/old /new', '/old /new 302' or '/blog/* /news/:splat'. Destinations may be absolute URLs. |
No output schema declared.
No examples provided.
regex_test Test regex ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | string | – | e.g. "gi" |
| pattern | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
remove_duplicate_lines Remove duplicate lines ~101
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}
| Name | Type | Req | Description |
|---|---|---|---|
| caseInsensitive | boolean | – | Compare case-insensitively (default false). |
| text | string | yes | Multi-line text to deduplicate. |
| trim | boolean | – | Trim each line before comparing (default true). |
No output schema declared.
No examples provided.
remove_empty_lines Remove empty lines ~53
Strip blank / whitespace-only lines from the input. Returns: Text with blank lines removed. Example input: {"text":"one\n\ntwo\n\n\nthree"}
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Multi-line text. |
No output schema declared.
No examples provided.
remove_extra_spaces Remove extra spaces ~59
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"}
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to normalize. |
No output schema declared.
No examples provided.
run_calculator Run a RedBison calculator ~177
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":{}}
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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. |
No output schema declared.
No examples provided.
search_tools Search RedBison tools ~162
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}
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 10, max 25). |
| query | string | yes | Search term (name, keyword, or use case). |
No output schema declared.
No examples provided.
simple_interest Simple interest calculator ~89
Compute simple interest: I = P × r × t. Returns: JSON { interest, total } computed as P·r·t. Example input: {"principal":10000,"annualRatePercent":5,"years":3}
| Name | Type | Req | Description |
|---|---|---|---|
| annualRatePercent | number | yes | Annual interest rate as a percent. |
| principal | number | yes | Principal amount. |
| years | number | yes | Time in years. |
No output schema declared.
No examples provided.
slugify Slugify text ~49
Convert text to a URL-safe slug. Returns: URL-safe slug (lowercase, dashes). Example input: {"text":"Hello, World! 2026"}
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
sql_beautify SQL beautify ~65
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"}
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | SQL query. |
No output schema declared.
No examples provided.
subnet_calculator Subnet calculator (IPv4) ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cidr | string | yes | IPv4 CIDR, e.g. 192.168.1.0/24. |
No output schema declared.
No examples provided.
text_diff Text diff ~95
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"}
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | Original text. |
| b | string | yes | Modified text. |
No output schema declared.
No examples provided.
timezone_convert Timezone converter ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| timestamp | string | yes | ISO 8601 timestamp (e.g. 2025-01-15T14:30:00Z or 2025-01-15T09:30:00-05:00). |
| to | string | yes | Target IANA timezone (e.g. America/New_York, Asia/Tokyo). |
No output schema declared.
No examples provided.
toml_convert TOML / JSON / YAML convert ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The document to convert. |
| to | string | – | Output format. |
No output schema declared.
No examples provided.
tsv_parse TSV parser ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| header | boolean | – | First row is header (default true). |
| text | string | yes | TSV input. |
No output schema declared.
No examples provided.
url_decode URL decode ~50
Percent-decode a URL-encoded string. Returns: Percent-decoded plain text. Example input: {"text":"hello%20world%20%26%20friends"}
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
url_encode URL encode ~48
Percent-encode a string for use in URLs. Returns: Percent-encoded string suitable for URL query values. Example input: {"text":"hello world & friends"}
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
user_agent_parse User-Agent parser ~195
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"}
| Name | Type | Req | Description |
|---|---|---|---|
| userAgent | string | yes | The full User-Agent header value. |
No output schema declared.
No examples provided.
utm_build Build a UTM campaign URL ~334
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"}
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Landing page URL. https:// is added if the scheme is missing. |
No output schema declared.
No examples provided.
uuid_generate Generate UUID ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many to generate (default 1, max 100). |
No output schema declared.
No examples provided.
word_count Word and character count ~262
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}
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The text to count. |
| topWords | integer | – | How many frequent words to return, stop words excluded. 0 to skip. |
No output schema declared.
No examples provided.
xml_beautify XML beautify ~78
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}
| Name | Type | Req | Description |
|---|---|---|---|
| indent | number | – | Indent size (default 2). |
| xml | string | yes | XML input. |
No output schema declared.
No examples provided.
yaml_beautify YAML beautify ~65
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"}
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | YAML input. |
No output schema declared.
No examples provided.
yaml_to_json YAML to JSON ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | YAML input. |
No output schema declared.
No examples provided.
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.
remote · mcp.redbison.dev
claude mcp add --transport http dev-redbison-mcp 'https://mcp.redbison.dev/'
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.