I Built an MCP Server with 36 Developer Tools. Now Claude Does My Site Audits.

Source: Dev.to

Introduction

I got tired of juggling browser tabs to check SSL certificates, DNS records, security headers, and broken links. So I built an MCP server that lets Claude handle all of that with a single configuration block and 36 developer tools.

How It Works

Claude receives a simple prompt, calls three APIs behind the scenes (SSL certificate check, security headers analysis, and email authentication – SPF, DKIM, DMARC), and returns a report with actual findings in about ten seconds. I didn’t write any orchestration logic; I just gave Claude atomic tools and it figured out how to chain them together.

Example Use Cases

• Bulk SSL monitoring – Claude loops through a list, calls check_ssl for each domain, compares expiry dates, and returns a summary table.
• Screenshot comparison – Claude captures two screenshots, uses its vision model to spot visual differences, without any Playwright setup or test scripts.
• Email list cleaning – Claude reads a CSV, calls validate_email per row, and writes a cleaned output (≈ 15 s for 200 rows).
• DNS migration check – Claude calls dns_lookup, checks the A record, and tells you if it matches the expected value.

MCP Client Configuration

{
  "mcpServers": {
    "apixies": {
      "command": "npx",
      "args": ["-y", "@apixies/mcp-server"],
      "env": {
        "APIXIES_API_KEY": "your-key-here"
      }
    }
  }
}

Config File Locations

After restarting the client, all 36 tools appear and are ready to use.

Available Tools

Inspectors

• SSL checker
• Security headers
• DNS lookup
• Email inspector
• WHOIS
• Link checker
• Redirect tracer
• Meta tag extractor
• robots.txt parser
• Favicon fetcher
• URL validator
• Email auth validator
• User‑agent parser
• IP geolocation
• Website performance
• JWT decoder

Converters

• HTML → PDF
• Markdown → HTML
• JSON formatter / JSON → CSV
• Base64 encode/decode
• URL encode/decode
• Color converter
• Timestamp converter
• Phone formatter
• JSON schema validator

Generators

• QR code
• Screenshot
• Password
• UUID
• Hash
• Lorem ipsum
• URL shortener

Each tool includes a description that tells the AI when to use it, so you never pick tools manually—just describe what you want and Claude decides which ones to call.

Sample Prompts

Simple requests

• Check the SSL certificate for github.com
• What DNS records does google.com have?
• Generate a 24‑character password with symbols

Multi‑tool workflows

• Check SSL, headers, and performance for these 5 client sites. Give me a comparison table.
• Take a screenshot of example.com and check if their OpenGraph meta tags are set up correctly.
• Decode this JWT and tell me when it expires: eyJhbG...
• Scan all markdown files in ./docs/ for URLs and check if any are broken.

The last example is a personal favorite: Claude extracts every URL from your docs, calls the link checker for each, and reports dead links—a task that would have taken me an hour to script.

MCP Protocol Overview

MCP (Multi‑Tool Communication Protocol) is an open protocol from Anthropic. You define tools with a name, description, and parameter schema. The AI reads the descriptions and invokes the appropriate tool when relevant.

Server Implementation

The server is a small TypeScript package. Each of the 36 API endpoints is registered as a tool with a Zod schema for input validation. When Claude calls a tool, the server forwards the request to the Apixies API and returns the JSON response.

• npm package: @apixies/mcp-server

Getting Started

1. Install the server:

   npm i -g @apixies/mcp-server

2. Add the configuration block above to your client config file.

3. Restart the client to load the tools.

A free API key can be obtained at . The service also works in sandbox mode (20 requests/day) without a key.

API Platform

All tools are powered by the Apixies API platform: .