Developer · Remote MCP server

Useful Utilities

63 tools an LLM can't do alone, in focused subsets: file edits, live data, real checksums.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.aksp200/useful-utilities
Version
1.2.1
Status
Active
Category
developer
Transport
Streamable HTTP, SSE (HTTP + Server-Sent Events)
Published
2026-09-22
Updated
2026-09-22
Publisher
aksp200 (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/aksp200) · how
Repository
github.com/aksp200/mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.usefulutils.in/mcpAuthorization (required, secret)
SSE (HTTP + Server-Sent Events)https://mcp.usefulutils.in/sseAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Endpoint
https://mcp.usefulutils.in/mcp (HTTP)
Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401
Checked on
2026-10-05
Endpoint
https://mcp.usefulutils.in/sse (SSE)
Reachable
Yes (HTTP 401)
SSE stream
Not opened: sign-in required
Sign-in required
Yes - HTTP 401
Checked on
2026-10-05

How the live check works

How to connect Useful Utilities

Useful Utilities is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.usefulutils.in/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

It also lists an endpoint on the older SSE transport https://mcp.usefulutils.in/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
URLpipeRead any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse.Remote · HTTPLive check: ✓ handshakeurlpipe.dev
URLs-LEExtract URLs from documentation, configuration and code, with their protocol and position.Local · stdionpm: urls-le-mcp
US Code of Federal RegulationsLook up, search, and track changes to the US Code of Federal Regulations (eCFR).Local · stdioPyPI: cfr-mcp
UsageMax public observabilityRead-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data.Remote · HTTPLive check: ✓ handshakeusagemax.com
UseMyContext.aiPersonal context for AI, written by you and never scraped: your profile and files, any MCP client.Remote · HTTPLive check: ✓ handshakemcp.usemycontext.ai
User PromptAn MCP server that enables AI agents to ask users clarifying questions via pop-up terminal windows.Local · stdioNuGet: UserPrompt
USGS Water MonitoringReal-time water levels and flow rates from USGS stream gauges.Remote · HTTPLive check: ✓ handshakemcp.olyport.com
Usitc EdisUSITC IDS (Investigations Database System, ids.usitc.gov) - the CASE.Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io