Safe filename charset, name discarded
MCP serverRemote MCP endpoint reporting whether a filename uses a safe charset, input not kept
Not checked yet- Remote
- Open source
- Developer tools
Remote MCP endpoint reporting whether a filename uses a safe charset, input not kept
Not checked yetRemote MCP endpoint for checking git tag name safety without keeping the name
Not checked yetRemote MCP endpoint for checking git branch name safety without keeping the name
Not checked yetRemote MCP endpoint for checking git tag name safety without keeping the name
Not checked yetRemote MCP endpoint that checks the shape of an HTML heading level 1-6
Not checked yetRemote MCP utility that checks whether a URL uses an http or https scheme
Not checked yetRemote MCP endpoint for checking hex encoding without storing the input
Not checked yetRemote MCP endpoint that checks an RTF header and discards the body
Not checked yetRemote MCP endpoint that reports the shape of a heading level from 1 to 6
Not checked yetRemote MCP endpoint named range-ok that checks the shape of a Range header
Not checked yetRemote MCP endpoint offering a Punycode host check for autonomous clients
Not checked yetRemote MCP endpoint that checks a 32-character hex string, from a set of small utility
Not checked yetThe closest alternatives to Safe header name check are Safe filename charset, name discarded, Git tag name safety, name discarded, Git branch name safety, name discarded, Git tag name safety, name discarded and Heading level 1-6 shape.
Yes. Safe filename charset, name discarded, Hex encode, input discarded, 32 hex chars have a free or open-source option.