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.

Related MCP server: mcp-server-devutils

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

• Site — https://obfus.link

• Why deterministic + lean — https://obfus.link/why

• MCP docs — https://obfus.link/docs/mcp

• Pricing — https://obfus.link/pricing

A Subether Labs infrastructure project.