Utility Grid

link.obfusPublished by obfus.linkOfficial publisherv1.0.1Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint offering 31 deterministic developer utilities such as JSON-to-Zod, regex, JWT, curl-to-fetch, hashing, encoding and UUID generation.

What you can do
Convert and transform code and data: JSON to Zod schemas, curl commands to fetch calls, regex built from examples, JWT hardening, AES-256 link obfuscation, plus encoders and converters. Generate identifiers and hashes: UUIDs, hashing and encoding utilities. Analyze and validate inputs with deterministic tools that return the same byte-identical answer each time. Discover tools on demand: one search tool is advertised by default and the rest are found when needed, keeping context use low.
When to use it
Useful when an assistant needs quick, repeatable developer utilities — schema generation, token or regex work, encoding, hashing, UUIDs — without installing a local package, especially where low context overhead matters.
Requirements
A remote Streamable HTTP endpoint; many clients connect through the mcp-remote bridge, which needs Node.js and npx. No authentication is declared for basic use. Network access to the endpoint is required.
Before you install
The service is machine-payable: 50 free calls per IP, then a 402 payment challenge the agent can complete on its own, so paid usage may incur spending. Tools handle tokens, JWTs and encrypted links, so avoid sending secrets you would not share with a third party. Tool calls send your inputs to the remote service.

Installation

In SourceWeft

  1. Open Utility Grid in the dashboard and add it to a workspace.
  2. 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/link.obfus%2Futility-grid/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "utility-grid": {
      "type": "http",
      "url": "https://obfus.link/mcp"
    }
  }
}

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:

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.

Source: README.md at commit c330f98

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts