mcpField
A
Aparajithn/agent Utils

Aparajithn/agent Utils

Local
github.com/aparajithnAI & Agents5Updated 7w ago

About Aparajithn/agent Utils

Agent Utils is an MCP server and REST API for common data and text utilities, aimed at AI agents and applications that need reusable transformations. Its 18 tools cover formats, identifiers, time, text analysis, and related tasks.

Key features

  1. 01Validate and format JSON
  2. 02Encode, decode, and hash strings
  3. 03Generate UUIDs and URL slugs
  4. 04Parse URLs, regexes, and cron schedules
  5. 05Convert Markdown, HTML, CSV, and JSON
  6. 06Analyze text, compare diffs, and decode JWTs

Use cases

  1. 01Check or reformat JSON data
  2. 02Convert CSV records to JSON or back
  3. 03Calculate text statistics or compare two texts
  4. 04Inspect a URL, cron expression, or JWT payload

MCP support

Exposes 18 tools through an MCP endpoint using Streamable HTTP, with a matching REST API. MCP clients can connect to the server URL shown in the README.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Agent Utils MCP Server 🛠️

A Swiss-army-knife utility server for AI agents — 18 tools via MCP (Streamable HTTP) + REST API.

Smithery Glama

Live at: https://agent-utils-mcp.onrender.com

Add to Your MCP Client

Claude Desktop / Cursor / Windsurf

Add to your MCP config:

{
  "mcpServers": {
    "agent-utils": {
      "url": "https://agent-utils-mcp.onrender.com/mcp"
    }
  }
}
Smithery
smithery mcp add aparajithn/agent-utils

Tools (18)

ToolDescription
tool_json_validateValidate JSON string, return parsed or error
tool_json_formatPretty-print or minify JSON
tool_base64_encodeEncode string to base64
tool_base64_decodeDecode base64 string
tool_hash_generateMD5, SHA256, SHA512 hash
tool_uuid_generateUUID v4 or v7
tool_url_parseParse URL into components
tool_regex_testTest regex pattern, return matches
tool_markdown_to_htmlMarkdown → HTML
tool_html_to_markdownHTML → Markdown
tool_text_statsWord count, char count, reading time
tool_slug_generateURL-safe slug from text
tool_datetime_convertConvert between timezones/formats/Unix timestamps
tool_cron_parseHuman-readable cron description + next N runs
tool_diff_textUnified diff between two texts
tool_csv_to_jsonCSV → JSON array
tool_json_to_csvJSON array → CSV
tool_jwt_decodeDecode JWT payload (no verification)

REST API

All tools also available as REST endpoints at /api/v1/{tool_name}.

# Hash a string
curl -X POST https://agent-utils-mcp.onrender.com/api/v1/hash_generate \
  -H "Content-Type: application/json" \
  -d '{"text": "hello world", "algorithm": "sha256"}'

# Generate UUID
curl -X POST https://agent-utils-mcp.onrender.com/api/v1/uuid_generate \
  -H "Content-Type: application/json" \
  -d '{"version": 4}'

# Convert datetime
curl -X POST https://agent-utils-mcp.onrender.com/api/v1/datetime_convert \
  -H "Content-Type: application/json" \
  -d '{"dt_string": "2025-01-01 12:00", "from_tz": "UTC", "to_tz": "America/New_York"}'

OpenAPI docs: https://agent-utils-mcp.onrender.com/docs

Discovery

  • Google A2A: /.well-known/agent-card.json
  • Smithery: /.well-known/mcp/server-card.json
  • OpenAPI: /openapi.json

Pricing

  • Free tier: 100 requests per IP per 24 hours
  • Paid tier: x402 protocol — $0.001/request in USDC (Base network)
Paying with x402

When you exhaust the free tier, the server replies with HTTP 402 carrying machine-readable payment requirements (x402 v1). Any x402-aware client pays and retries automatically:

from x402_fetch import x402_fetch  # pip install x402-fetch
response = x402_fetch("https://agent-utils-mcp.onrender.com/api/v1/hash_generate", method="POST",
                      body={"text": "hello", "algorithm": "sha256"})

Or attach the payment header yourself: the X-Payment header must be a base64-encoded JSON envelope containing an EIP-3009 TransferWithAuthorization (USDC on Base) signed with the payer's EIP-712 key for the exact price, addressed to the server's wallet, with an unused nonce. Payments are verified cryptographically (signature recovery + amount/recipient/deadline/replay checks) before the request is served.

Payment configuration (environment variables)
VariableDefaultPurpose
X402_WALLET_ADDRESS(unset — paywall disabled)Wallet that receives payments
X402_PRICE_MICROUSD1000 ($0.001)Price per request in USDC atomic units
X402_NETWORK / X402_CHAIN_ID / X402_USDC_CONTRACTbase / 8453 / Base USDCPayment network
X402_MAX_TIMEOUT_SECONDS60Payment validity window
RATE_LIMIT_FREE100Free requests per IP per 24h
Collecting revenue (on-chain settlement)

With X402_SETTLER_PRIVATE_KEY set, every verified payment is executed on-chain within seconds: the EIP-3009 transferWithAuthorization is submitted to the USDC contract on Base and the USDC moves from the payer to X402_WALLET_ADDRESS. The settler key does not need to be the receiving wallet's key — EIP-3009 authorizations can be executed by any address, so a dedicated gas-only burner key can do the submitting while the funds land in your main wallet. It only needs a small ETH balance on Base for gas.

VariableDefaultPurpose
X402_SETTLER_PRIVATE_KEY(unset — verify only, no funds move)Key that submits settlement transactions
X402_RPC_URLhttps://mainnet.base.orgBase JSON-RPC endpoint
X402_SETTLE_MIN_MICROUSD0 (settle each payment immediately)Batch payments until pending value reaches this

Failed settlements are retried with exponential backoff; if all retries fail, the full payment authorization is written to the logs (CRITICAL) so it can be redeemed manually — no payment is silently lost.

Tech Stack

License

MIT

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.