Tidy Byte Tools
PYPI · TIDY-BYTE-TOOLS
One local MCP server: repair JSON, PDF tables to CSV, docs to Markdown, hashes and more. No API key.
Available components
Last scanned (15 hours ago)
Scores higher than 75% of PyPI servers
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 47 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to tidybytetools/tidy-byte-tools). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4356 tokens (~290/item across 15 items; 15 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
- Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 +25
- Malware scan: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- The attested source repository moved: tidybytetools/tidy-byte-tools security
- 18 Nov 26 54
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 21 Nov 2026 · Analysed pypi/tidy-byte-tools@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | tidybytetools/tidy-byte-tools |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/tidybytetools/tidy-byte-tools/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 3956759272 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:bdb5422004c77341013ed97ad1d45125419b709b5a83cc13101d885c409dd857 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 47 packages
| Packages resolved | 47 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
base64_convert_file Encode or decode a local file as Base64 ~292
Read a local file and encode its bytes to Base64, or decode a Base64 text file. Use this when the data is in a file on this computer, so you don't have to paste it. The file is only read, never changed. Files larger than 5 MB are rejected; use the Apify version for bigger jobs. For decode, the file must be UTF-8 text containing Base64 (or a data URI), not a binary file. path: full path to a file, up to 5 MB. Returns the same result object as convert_text. If the decoded bytes are not UTF-8 text, "isText" is false and "text" is null.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | What to do. "auto" (default) decodes if the input looks like Base64, otherwise it encodes. Use "encode" or "decode" when you already know the direction. |
| data_uri | boolean | – | If true, encoded results also include a data: URI. The MIME type is guessed from the file name when we can. |
| path | string | yes | Full path to a local file, up to 5 MB. For decode, the file must be UTF-8 text of Base64. |
| url_safe | boolean | – | If true, encode with - and _ instead of + and /. Decoding always accepts both. |
No output schema declared.
No examples provided.
base64_convert_text Encode or decode Base64 text ~296
Encode pasted text to Base64, or decode Base64 (or a data URI) back to text. Use this when you have text or a Base64 string in the conversation. It is plain code, not an AI model, so the same input always gives the same output and nothing is made up. Do not use it for a file on disk (use convert_file for files), and do not use auto on short or unusual strings if you already know the direction — pass encode or decode instead. Returns a result object. Encoded results include "action", "base64", "bytesIn", and "dataUri" plus "mime" when data_uri is true. Decoded results include "action", "bytesOut", "isText", and "text" (UTF-8 text, or null if the bytes are not text).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | What to do. "auto" (default) decodes if the input looks like Base64, otherwise it encodes. Use "encode" or "decode" when you already know the direction. |
| data_uri | boolean | – | If true, encoded results also include a data: URI. |
| text | string | yes | The text to encode, or the Base64 (or data URI) to decode. |
| url_safe | boolean | – | If true, encode with - and _ instead of + and /. Decoding always accepts both. |
No output schema declared.
No examples provided.
check_links Check links ~210
Check web links and follow their redirects. Use this when you have a list of URLs and need to know which ones work, which are broken (404, 500, timeouts, bad hosts) and where redirects end up, for example to clean up docs, a README, a sitemap list or bookmarks. It does not crawl a site or read page content; pass the exact links you want checked. Links that are not http or https come back with ok false and an error. urls: up to 200 http(s) links. timeout: seconds to wait for each link. Returns one result per link: {url, status, ok, final_url, redirects, error, ms}. status is the HTTP code of the last hop (null if it could not connect). ok is true for 200-399. redirects lists each hop as "CODE url". ms is how long the check took, in milliseconds.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout | number | – | – |
| urls | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
chunk_markdown Split Markdown into chunks ~425
Split a Markdown file or Markdown text into chunks by heading, for search, embeddings or RAG. Use this when you need a long Markdown document (docs, notes, a README) broken into pieces that each know where they came from. A chunk never mixes two sections. Each chunk has heading_path (like ["Guide", "Install"]), anchor (the GitHub-style #link), start_line and end_line (1-based, in the file), part and parts (when a big section had to be split), chars and text. Code blocks and tables are kept whole when they fit; when they don't, each piece gets the fence or table header again. Plain code, not AI: same input, same chunks. Do not use it for PDF or Word files (convert them to Markdown first), to just see the headings (use outline_markdown), or to read one section (use get_section). Sizes are characters, not tokens. Returns {"source", "total", "start", "chunks": [...], "next_start"}. next_start is null when there are no more chunks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most chunks to return in one call. Default 100. |
| max_chars | integer | – | Biggest chunk size in characters (not tokens). Default 1500. |
| overlap_chars | integer | – | Characters repeated from the end of one part at the start of the next, only when a section is split. Must be at most half of max_chars. Default 0. |
| path | string | – | Full path to a local Markdown or text file (UTF-8, up to 10 MB). Leave empty if you pass text. |
| prefix_path | boolean | – | If true, each chunk text starts with its heading path, like "Guide > Install". |
| start | integer | – | First chunk number to return (1 = the first). Use next_start from the last call to get more. |
| text | string | – | Markdown text to use instead of a file. Leave empty if you pass path. |
No output schema declared.
No examples provided.
convert_to_markdown Convert PDF or HTML to Markdown ~248
Turn a local text PDF or saved HTML file into clean Markdown. Use this when you want to read, quote, summarize or index a document as text, for example before RAG chunking or pasting into a prompt. Tables are kept as Markdown tables. Do not use it for scanned PDFs or photos (there is no OCR), for live web URLs (save the page as .html first), or when you only need the tables as CSV data (use a PDF table extractor instead). path: full path to a .pdf or .html file on this computer. tables: PDF tables. "lines" (default) finds tables with border lines, "text" also tries tables lined up by spaces, "off" gives plain text. output_path: optional. If set, the Markdown is saved there and that path is returned. An existing file at that path is replaced. If empty, nothing is written and the Markdown text is returned. Tables come back as Markdown tables. Scanned (image-only) PDF pages have no text and are skipped.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | – |
| path | string | yes | – |
| tables | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
extract_pdf_tables Extract PDF tables to CSV ~286
Pull the tables out of a local text PDF. Use this when you need the rows and columns of a table from a PDF on this computer, for example to load them into a spreadsheet, pandas or a database. Do not use it for scanned PDFs or photos (there is no OCR), for PDFs on the web (download the file first), or when you want the whole document as text (use a PDF-to-Markdown or text tool instead). path: full path to a PDF on this computer. pages: optional, like "1,3-5". Empty means all pages. strategy: "auto" (default, tries borders first, then spacing), "lines" (tables with ruled borders) or "text" (tables lined up by spacing). Try "text" if "auto" misses a table that has no border lines. output_dir: optional. If set, each table is saved there as a CSV and the file paths are returned. Files named pageN_tableM.csv that already exist there are replaced. If empty, nothing is written and the CSV text of each table is returned. Scanned (image-only) pages have no text and are skipped. Returns [] if no tables.
| Name | Type | Req | Description |
|---|---|---|---|
| output_dir | string | – | – |
| pages | string | – | – |
| path | string | yes | – |
| strategy | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_section Get one Markdown section ~288
Return the text of one section of a Markdown file or text, found by heading title or anchor. Use this when you only need one part of a long document, like the "Install" section of a README, so you don't have to read the whole file. If two headings have the same title, the first one is returned and "matches" tells you how many there are; use the anchor (from outline_markdown) to pick another. Do not use it to split the whole document (use chunk_markdown). Returns {"title", "heading_path", "level", "anchor", "start_line", "end_line", "chars", "matches", "text"}. If nothing matches, the error lists the headings.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | string | – | Anchor to find, like "install" or "install-1" for the second "Install". Wins over heading. |
| heading | string | – | Heading title to find, like "Install". Not case sensitive. Leave empty if you pass anchor. |
| include_subsections | boolean | – | If true (default), include the smaller headings under it. |
| path | string | – | Full path to a local Markdown or text file (UTF-8, up to 10 MB). Leave empty if you pass text. |
| text | string | – | Markdown text to use instead of a file. Leave empty if you pass path. |
No output schema declared.
No examples provided.
hash_file Hash a local file ~317
Hash a local file's raw bytes with SHA-256, SHA-1, MD5, and optional SHA-512. Use this when the data is in a file on this computer, so you don't have to paste it. The file is only read, never changed. Files larger than 5 MB are rejected; use the Apify version for bigger jobs. This tool does not look the hash up in a malware list or a password list. path: full path to a file, up to 5 MB. algorithms: a list from sha256, sha1, md5, sha512. Default is sha256, sha1 and md5. MD5 and SHA-1 are not safe for new security work; prefer SHA-256 or SHA-512 when you can. Returns {"ok", "bytes", "hashes", and a hex field for each algorithm, plus a Base64 field when include_base64 is true}.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithms | – | – | Hash algorithms to compute. Default: sha256, sha1, md5. SHA-512 is optional. MD5 and SHA-1 are provided because people still need them for checks; they are not safe for new security work. |
| include_base64 | boolean | – | If true (default), each hash is returned as hex and as Base64. Hex is always included. |
| path | string | yes | Full path to a local file, up to 5 MB. The raw file bytes are hashed, not a decoded string. |
No output schema declared.
No examples provided.
hash_text Hash a text string ~309
Hash pasted text with SHA-256, SHA-1, MD5, and optional SHA-512. Use this when you have text in the conversation and need its checksum. The text is hashed as UTF-8 bytes. It is plain code, not an AI model, so the same text always gives the same hashes. This tool does not look the hash up in a malware list or a password list. Do not use it for a file on disk (use hash_file for files). algorithms: a list from sha256, sha1, md5, sha512. Default is sha256, sha1 and md5. MD5 and SHA-1 are not safe for new security work; prefer SHA-256 or SHA-512 when you can. Returns {"ok", "bytes", "encoding": "utf-8", "hashes", and a hex field for each algorithm, plus a Base64 field when include_base64 is true}.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithms | – | – | Hash algorithms to compute. Default: sha256, sha1, md5. SHA-512 is optional. MD5 and SHA-1 are provided because people still need them for checks; they are not safe for new security work. |
| include_base64 | boolean | – | If true (default), each hash is returned as hex and as Base64. Hex is always included. |
| text | string | yes | The text to hash. It is hashed as UTF-8 bytes. |
No output schema declared.
No examples provided.
outline_markdown List Markdown headings ~222
List every heading in a Markdown file or text, with its level, path, anchor, line number and size. Use this when you want a quick map of a long document before you read or chunk it, or to find the exact heading or anchor to pass to get_section. Headings inside code blocks and YAML front matter are ignored. Both "# Title" and underlined (=== / ---) headings are found. Do not use it to get the text itself (use get_section or chunk_markdown). Returns {"source", "count", "headings": [{"level", "title", "path", "anchor", "line", "end_line", "chars"}]}. chars is the size of that heading's own text, not counting the sections under it.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Full path to a local Markdown or text file (UTF-8, up to 10 MB). Leave empty if you pass text. |
| text | string | – | Markdown text to use instead of a file. Leave empty if you pass path. |
No output schema declared.
No examples provided.
repair_json_file Repair JSON in a local file ~194
Read a local JSON file and repair it if it is broken or incomplete. Use this when the JSON is in a file on this computer, so you don't have to paste it. The file is only read, never changed. Files larger than 5 MB are rejected; use the Apify version for bigger jobs. Do not use it for files that are not JSON text. path: full path to a UTF-8 text file, up to 5 MB. json_lines: if true, each non-empty line is a separate document. If false (default), the whole text is tried as one JSON value first. Returns the same object as repair_json_text.
| Name | Type | Req | Description |
|---|---|---|---|
| json_lines | boolean | – | If true, treat each non-empty line as its own JSON document. |
| path | string | yes | Full path to a UTF-8 .json or .jsonl file, up to 5 MB. |
No output schema declared.
No examples provided.
repair_json_text Repair broken JSON text ~249
Repair broken or incomplete JSON, including output from language models. Use this when you have JSON in the conversation that may be missing quotes, have trailing commas, or be cut off. It is plain code, not an AI model: it can close missing brackets and fix common syntax issues, but it cannot invent the data you meant to write. Already-valid JSON is returned as-is, with wasValid true and repaired false. Do not use it for a file on disk (use repair_json_file for files). json_lines: if true, each non-empty line is a separate document. If false (default), the whole text is tried as one JSON value first. If that cannot be repaired and there are several lines, each line is then tried on its own. For one document, returns {"wasValid", "repaired", "value", "text"}. For several documents, returns {"count", "failed", "documents": [...]}.
| Name | Type | Req | Description |
|---|---|---|---|
| json_lines | boolean | – | If true, treat each non-empty line as its own JSON document. |
| text | string | yes | The JSON text to repair. May be one value, or several JSON Lines. |
No output schema declared.
No examples provided.
save_chunks_jsonl Save chunks to a JSONL file ~281
Split a Markdown file into chunks and save them as a JSONL file (one chunk per line). Use this when the chunks are going into a search index, vector database or another program, and you want a file instead of a long chat reply. The chunks are the same as chunk_markdown gives. It writes only the one .jsonl file and replaces it if it is already there. It never changes the Markdown file. Do not use it to look at chunks in the chat (use chunk_markdown). Returns {"output_path", "chunks", "bytes", "biggest_chunk_chars"}.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | Biggest chunk size in characters (not tokens). Default 1500. |
| output_path | string | – | Where to save. Must end in .jsonl. Default: next to the input, as NAME.chunks.jsonl. |
| overlap_chars | integer | – | Characters repeated from the end of one part at the start of the next, only when a section is split. Must be at most half of max_chars. Default 0. |
| path | string | yes | Full path to the local Markdown file to split (UTF-8, up to 10 MB). |
| prefix_path | boolean | – | If true, each chunk text starts with its heading path, like "Guide > Install". |
No output schema declared.
No examples provided.
shape_file_to_json Turn a text file into JSON ~284
Read a local text file (key: value notes, .csv, .tsv or a Markdown table) and return typed JSON. Use this when the data is in a file on this computer, so you don't have to paste it. The file is only read, never changed. Do not use it for Excel (.xlsx), PDF or other binary files, for files that are already JSON, or for app logs. path: full path to a UTF-8 text file, up to 5 MB. format: "auto" (default) picks for you. Or force "kv" (key: value or key=value lines, a blank line starts a new record), "csv" (comma, semicolon, tab or | separated, first row is the header) or "markdown" (a | pipe | table, first row is the header). Returns {"format": <format used>, "data": <JSON>}, the same as shape_text_to_json.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Input format. "auto" picks for you; "kv" = key: value lines, "csv" = CSV/TSV, "markdown" = a pipe table. |
| path | string | yes | Full path to a UTF-8 text file (.txt, .csv, .tsv, .md), up to 5 MB. |
No output schema declared.
No examples provided.
shape_text_to_json Turn text into JSON ~342
Turn pasted text (key: value notes, CSV/TSV or a Markdown table) into typed JSON. Use this when you have plain-text records or a table in the conversation and need clean JSON you can trust, without guessing values yourself. It is plain code, not an AI model, so the same text always gives the same JSON and nothing is made up. Do not use it when the text is already JSON, is nested data, is app logs, or is a file on disk (use shape_file_to_json for files). format: "auto" (default) picks for you. Or force "kv" (key: value or key=value lines, a blank line starts a new record), "csv" (comma, semicolon, tab or | separated, first row is the header) or "markdown" (a | pipe | table, first row is the header). Returns {"format": <format used>, "data": <JSON>}. data is a list of records for CSV and tables. For key: value text it is one object, or a list when blank lines split it into several records. Keys become lower_snake_case. Numbers become numbers, yes/no and true/false become booleans, empty or "null" becomes null.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Input format. "auto" picks for you; "kv" = key: value lines, "csv" = CSV/TSV, "markdown" = a pipe table. |
| text | string | yes | The text to turn into JSON: key: value lines, CSV/TSV or a Markdown table. |
No output schema declared.
No examples provided.
How do I install the Tidy Byte Tools MCP server?
Tidy Byte Tools runs locally as a PyPI package, launched with uvx tidy-byte-tools mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · tidy-byte-tools
claude mcp add tidybytetools-tidy-byte-tools -- uvx tidy-byte-tools mcp
What is the Tidy Byte Tools MCP server?
Tidy Byte Tools is an MCP server listed in the public MCP registry as io.github.tidybytetools/tidy-byte-tools. One local MCP server: repair JSON, PDF tables to CSV, docs to Markdown, hashes and more. No API key. This page covers its PyPI package (tidy-byte-tools).
Is the Tidy Byte Tools MCP server safe to use?
Tidy Byte Tools scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 MCP server expose?
Tidy Byte Tools exposes 15 tools: repair_json_text, repair_json_file, shape_text_to_json, shape_file_to_json, base64_convert_text, and 10 more. Their descriptions and schemas cost roughly 4,243 tokens of context every time the server is loaded.
Is the Tidy Byte Tools MCP server still maintained?
Tidy Byte Tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Tidy Byte Tools MCP server under?
Tidy Byte Tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Tidy Byte Tools MCP server?
VerifyMCP ran 15 checks on Tidy Byte Tools, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Tidy Byte Tools: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.