mcpField
U
utility-grid

utility-grid

Remote
obfus.linkDeveloper Tools0Updated 18w ago
RepositoryVisit website

About utility-grid

utility-grid is a remote MCP server offering deterministic developer utilities for tasks such as schema conversion, regex creation, JWT hardening, and encoding. Its on-demand tool discovery keeps only one search tool advertised by default.

Key features

  1. 0131 deterministic developer tools
  2. 02JSON-to-Zod conversion
  3. 03Regex generation from examples
  4. 04JWT hardening and curl-to-fetch conversion
  5. 05Hashing, encoding, and link obfuscation
  6. 06On-demand tool discovery

Use cases

  1. 01Convert JSON into a typed Zod schema
  2. 02Create a regex from example strings
  3. 03Harden JWT settings or convert curl to fetch
  4. 04Hash, encode, or obfuscate data

MCP support

It is a Streamable HTTP MCP server at https://obfus.link/mcp. MCP clients can discover tools on demand; most connect through the mcp-remote bridge.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://obfus.link/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

obfus.link — MCP Server

31 deterministic developer tools on a lean, machine-payable MCP endpoint. The official MCP Registry manifest for obfus.link lives in this repo (server.json).

  • Endpoint: https://obfus.link/mcp
  • Registry name: link.obfus/utility-grid
  • Tools: obfuscators, encoders, converters, generators, analyzers, validators (JSON→Zod, regex-from-examples, JWT hardener, curl→fetch, AES-256 link obfuscator, hashing/encoding, and more).

Why this one

  • Lean by design. Most MCP servers front-load every tool definition into your agent's context (~21k tokens here) on every turn. obfus.link advertises one search tool by default and discovers the rest on demand — ~98% less resident context. Reproduce it: obfus.link/why.
  • Deterministic, not generative. A tool call returns the same correct answer, byte-identical, every time — no retries, no drift.
  • Machine-payable. 50 free calls per IP, then a 402 challenge an agent can complete on its own (MPP). Discovery is always free.

Add it to your agent

obfus.link is a remote (Streamable HTTP) MCP server. Most clients connect via the mcp-remote bridge — for example, in claude_desktop_config.json:

{
  "mcpServers": {
    "obfus-link": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://obfus.link/mcp"]
    }
  }
}

Full onboarding (Cursor, SPT auth for paid use, the error contract): obfus.link/docs/mcp.

Try it without an agent

A zero-dependency, clone-and-run example (messy LLM JSON → clean, typed Zod schema in two deterministic calls) lives at subether-labs/obfus-link-demo.

Links

A Subether Labs infrastructure project.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.