mcp-bytesmith
Related Servers
Alternatives to mcp-bytesmith
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that exposes the python-bitcoinlib API. It provides tools for Bitcoin key management, address generation, transaction building, script operations, and cryptography.2024 PyPIMIT
- FlicenseNot gradedqualityBmaintenanceA free, zero-dependency Model Context Protocol (MCP) server for AI agents providing Web3/crypto toolkit (balances, ENS, token info, tx decode, Chainlink price feed, payment verification) plus encoding, hashing, and data transformation utilities.-
- AlicenseAqualityCmaintenanceA lightweight MCP server providing common utility tools such as unit conversion, password generation, date calculation, hashing, Base64 encoding/decoding, UUID generation, text case conversion, and text statistics, with no external dependencies.8MIT
- FlicenseNot gradedqualityDmaintenanceA production-ready MCP server providing file, system, math, and text utilities through a simple CLI client.-
- AlicenseNot gradedqualityFmaintenanceA lightweight, fast MCP server that provides onchain capabilities for the LLMs and Agents.37 npm253MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive math utility server implementing the Model Context Protocol (MCP) for reverse engineering and general-purpose arithmetic, bitwise, conversion, and encoding tasks via streamable HTTP.MIT
TDQS
Scored across 40 tools
Most tools target clearly different operations, and descriptions cross-reference likely alternatives, e.g. encode vs. string_escape, hash vs. hash_file/hmac, and password_hash vs. derive_key. Some overlaps remain, notably abi_codec vs. eth_calldata for ABI encoding/decoding and the broader hash/eth_hash/hmac cluster, but context in the descriptions usually resolves them.
Names are uniformly snake_case and use good domain prefixes such as eth_*, bip*, and abi_*, plus clear inverse pairs like encode/decode and string_escape/string_unescape. Minor deviations are single-word or noun-phrase names such as random, hash, info, codepoints, and bip39 rather than a strict verb_noun pattern throughout.
At 40 tools, this is well above the practical 3-15 range and crosses the 25-tool threshold that typically signals an overloaded surface. The broad domain partly justifies the breadth, but the selection burden for an agent is high and the server would benefit from consolidation or clearer grouping into toolsets.
The surface covers an unusually wide range: encoding/decoding, hashing/HMAC, KDFs/password hashing, Ethereum ABI/calldata/logs/tx/signing/storage/addresses, BIP-32/39, ENS, time, IDs, and Unicode. A few minor gaps exist, such as no explicit private-key generation and no OTP code computation, but core workflows are covered end-to-end.