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.

Tidy Byte Tools API

REMOTE · TIDYBYTETOOLS.TIDYBYTETOOLS.WORKERS.DEV

Remote MCP for JSON repair, hashing, formatting, IDs, dates, units, and other small tools.

+10 this week 66 Trust /100

Last scanned (20 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 471 tokens (~24/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • 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 hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 19 Nov 26 +1

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

  • 18 Nov 26 +7
    • Authorization: unverified → partial ▲ security
    • Tool “base64” changed its title: Base64 encode or decode cosmetic
    • Tool “cron_parse” changed its title: Parse a cron expression cosmetic
    • Tool “date_timezone” changed its title: Normalize dates cosmetic
    • Tool “gtin_checksum” changed its title: GTIN / EAN / UPC checksum cosmetic
    • Tool “hash” changed its title: Hash text cosmetic
    • Tool “html_sanitize” changed its title: Sanitize HTML cosmetic
    • Tool “id_generate” changed its title: Make IDs cosmetic
    • Tool “json_format” changed its title: Format or minify JSON cosmetic
    • Tool “json_repair” changed its title: Repair JSON cosmetic
    • Tool “json_shaper” changed its title: Shape text into JSON cosmetic
    • Tool “jwt_decode” changed its title: Decode a JWT cosmetic
    • Tool “md_chunk” changed its title: Chunk Markdown cosmetic
    • Tool “sql_format” changed its title: Format SQL cosmetic
    • Tool “text_diff” changed its title: Diff two texts cosmetic
    • Tool “unicode” changed its title: Normalize Unicode cosmetic
    • Tool “unit_convert” changed its title: Convert units cosmetic
    • Tool “url_codec” changed its title: URL encode or decode cosmetic
    • Tool “xml_json” changed its title: XML ↔ JSON cosmetic
    • Tool “yaml_json” changed its title: YAML ↔ JSON cosmetic
  • 17 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.

  • 15 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.

  • 13 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.

  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 55

    First indexed and scored.

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 · Probed https://tidybytetools.tidybytetools.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tidybytetools.workers.dev CN=YE2,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA384 50db93b1bd1259cd0cc270cecda5759a7d4
SANs: *.tidybytetools.workers.dev, tidybytetools.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tidybytetools.tidybytetools.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tidybytetools.tidybytetools.workers.dev/mcp Verified 200
http (plaintext) http://tidybytetools.tidybytetools.workers.dev/mcp Inconclusive 405
MCP tools · 19 exposed · ~432 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 ~30

Turn text into Base64, or Base64 back into text. URL-safe and data URIs work too.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cron_parse ~28

Explain a 5- or 6-field cron string and list the next fire times in UTC.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

date_timezone ~21

Parse a messy date and convert it to a timezone you choose.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

gtin_checksum ~20

Check or fill the check digit on a barcode number.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hash ~27

SHA-256, SHA-1, MD5, and SHA-512 checksums of text.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

html_sanitize ~23

Strip scripts and unsafe markup. Keeps a short allow-list of tags.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

id_generate ~19

Create a UUID, ULID, or NanoID.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

json_format ~15

Pretty-print or shrink valid JSON.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

json_repair ~21

Fix broken or incomplete JSON, including text from language models.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

json_shaper ~24

Turn key-value lines, CSV, or a Markdown table into clean JSON.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

jwt_decode ~22

Read a JWT header and payload. This does not check the signature.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

md_chunk ~20

Split Markdown into heading-aware chunks for search and RAG.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sql_format ~26

Pretty-print a SQL query. This is a lightweight formatter, not a full SQL parser.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

text_diff ~20

Line-level diff of two strings, plus a unified patch.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

unicode ~27

NFC, NFD, NFKC, or NFKD normalization, plus a character count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

unit_convert ~28

Convert length, mass, temperature, volume, time, area, speed, and data-size units.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

url_codec ~19

Percent-encode or decode a string or query map.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

xml_json ~21

Convert XML to JSON, or a JSON object back to XML.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

yaml_json ~21

Convert a common YAML subset to JSON, or JSON to YAML.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Tidy Byte Tools API MCP server?

Tidy Byte Tools API is a hosted endpoint at https://tidybytetools.tidybytetools.workers.dev/mcp, 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 · tidybytetools.tidybytetools.workers.dev

# add to Claude Code
claude mcp add --transport http tidybytetools-api 'https://tidybytetools.tidybytetools.workers.dev/mcp'
Common questions

What is the Tidy Byte Tools API MCP server?

Tidy Byte Tools API is an MCP server listed in the public MCP registry as io.github.tidybytetools/api. Remote MCP for JSON repair, hashing, formatting, IDs, dates, units, and other small tools. This page covers its hosted endpoint (https://tidybytetools.tidybytetools.workers.dev/mcp).

Is the Tidy Byte Tools API MCP server safe to use?

Tidy Byte Tools API scores 66 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 Tidy Byte Tools API MCP server expose?

Tidy Byte Tools API exposes 19 tools: json_repair, base64, hash, json_shaper, json_format, and 14 more. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.

Does the Tidy Byte Tools API MCP server require authentication?

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

Is the Tidy Byte Tools API MCP server still maintained?

Tidy Byte Tools API 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 did VerifyMCP test on the Tidy Byte Tools API MCP server?

VerifyMCP ran 12 checks on Tidy Byte Tools API, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Tidy Byte Tools API: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.