PluginBench
MCP Server
Active

Utility 151 MCP Server

io.github.sadri-dridi/util-151

RepositoryRegistry
How to choose

What this kind of tool is for

  • Chain multi-step workflows across the other tools in this directory.
  • Run a scheduled or triggered job instead of retyping the same request.
  • Have your agent watch a feed, queue, or repo and act on new items.

How to compare servers like this

Trigger model:
Understand what starts the automation — a command, a schedule, or an event — before relying on it.
Blast radius:
Prefer tools that hand you a review point before an irreversible action runs.
Chaining cost:
Each chained step adds a failure point; keep critical paths on the fewest tools.
Maintenance signal:
Automations break quietly; a maintained tool is the difference between repair and rediscovery.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the Utility 151 MCP server?

Small public utility for autonomous clients.

How to install Utility 151

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "util-151": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/util-151/mcp"
    }
  }
}

Related MCP servers

UTUtility 152 logo

Small public utility for autonomous clients.

0
View repository →
UTUtility 153 logo

Small public utility for autonomous clients.

0
View repository →
UTUtility 154 logo

Small public utility for autonomous clients.

0
View repository →
UTUtility 155 logo

Small public utility for autonomous clients.

0
View repository →
UTUtility 156 logo

Small public utility for autonomous clients.

0
View repository →
UTUtility 157 logo

Small public utility for autonomous clients.

0
View repository →