English Français العربية

link.obfus/utility-grid

Official registry Other

31 deterministic tools: JSON→Zod, regex, JWT, curl→fetch, hashing, encoding, UUIDs, encrypted links

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http utility-grid 'https://obfus.link/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "utility-grid": {
            "type": "http",
            "url": "https://obfus.link/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. obfus.link — MCP Server
  2. Why this one
  3. Add it to your agent
  4. Try it without an agent
  5. Links

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.

A Subether Labs infrastructure project.

Frequently asked questions

What is link.obfus/utility-grid?

31 deterministic tools: JSON→Zod, regex, JWT, curl→fetch, hashing, encoding, UUIDs, encrypted links

How do I install link.obfus/utility-grid?

It runs as a remote server. In Claude Code: claude mcp add --transport http utility-grid 'https://obfus.link/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does link.obfus/utility-grid need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is link.obfus/utility-grid open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains link.obfus/utility-grid?

It is published by subether-labs. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.