None of these tools is hard to write; having them all already there is the point — hash a file, count words, pull the emails out of a blob, check whether a URL resolves, without a script per task. It reads the local filesystem, environment variables and process list, so run it somewhere you are comfortable with an agent seeing all three.
A Python server carrying a wide set of small tools, grouped into date and time, local file handling, system information, text processing, and web operations.
- Date and time: current time, timestamp formatting, age from a birth date, days between two dates, a month calendar
- Files: read a file, detailed file information, list a directory, MD5/SHA256 hashing, pattern search
- System: general system information, CPU, memory, disks, network interfaces, running processes, environment variables
- Text: word and line counts, regex search and replace, email and URL extraction, text analysis, encode/decode, hashing, chunking
- Web: HTTP requests, URL parsing and building, URL encode/decode, format and reachability validation, domain extraction
- Async stdio communication, configurable logging, and a CLI
Python 3.10 or later and `uv`; installed from source. Everything except the web tools acts on the machine it runs on — the environment variables and process list tools read that machine's real environment and processes.
Build from source — clone the repository and build it, then point your client at the binary