
Useful Utilities
io.github.aksp200Published by GitHub account aksp200v1.2.1Updated Oct 24, 2026
63 tools an LLM can't do alone, in focused subsets: file edits, live data, real checksums.
Overview
A remote MCP endpoint offering 63 focused utility tools, including file edits, live data lookups and real checksums, for tasks an assistant cannot do alone.
- What you can do
- Perform file edits through the server's utility tools, grouped in focused subsets rather than one large set. Retrieve live data from external sources. Compute real checksums rather than estimated or fabricated values. The full tool list is not published in the manifest, so exact capabilities should be confirmed with the provider.
- When to use it
- Useful when an assistant needs dependable utility operations such as checksum verification, file edits or live data lookups that it cannot perform reliably on its own, and a hosted endpoint is preferable to a local install.
- Requirements
- A remote streamable HTTP endpoint; no local runtime or package is needed. A bearer API key is required in the Authorization header, and a free key is obtained from the provider's site. Network access to the endpoint is required.
Installation
In SourceWeft
- Open Useful Utilities in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.aksp200%2Fuseful-utilities/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"useful-utilities": {
"type": "http",
"url": "https://mcp.usefulutils.in/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
2- v1.2.1LatestSep 22, 2026
- v1.2.0Sep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.