SearchCtrl+K

API Freaks MCP Server

The API Freaks MCP server connects your AI assistant directly to the API Freaks platform, giving it real-time access to the full range of API Freaks APIs, right inside your workflow. It's the official API Freaks MCP server, running locally over stdio and set up with a single API key, and it works with Claude, Cursor, VS Code, Gemini CLI, Codex CLI, Windsurf, and any MCP-compatible client.

Get your free API key View on GitHub

Why use API Freaks MCP?

One integration, the whole platform

Set it up once and your assistant can reach every API in our catalog, with new ones added as we ship them. There's nothing to wire up per data type and no extra keys to manage.

The official server, built and maintained by us

It stays in sync with every API Freaks endpoint, so it just works, no betting your key or your results on a third-party wrapper that breaks or falls behind.

No integration code to maintain

Your assistant makes the API calls for you from a plain request, so you skip writing and looking after client code just to pull data.

Before you start

Make sure you have these ready:

Node.js v20 or higher

The MCP server runs through npx, which ships with Node. Check with node -v.

An API Freaks API key

Create a free account and copy your API key from the APIFreaks Dashboard on your dashboard. You'll pass it to the server as APIFREAKS_API_KEY in every setup below.

Full API reference: APIFreaks Docs.

Create your free account

Supported Tools

The MCP server exposes everything from weather and DNS lookups to WHOIS, IP intelligence, currency conversion, SSL inspection, domain checks, and more. Each tool works on its own or combined with others in a single request. Browse all tools and examples.

Platform Integrations

The setup is the same idea everywhere: run the server with npx -y @apifreaks/mcp and pass your key as APIFREAKS_API_KEY. Pick your client below.

Claude

Claude Code (CLI)

Add it from the terminal (recommended):

claude mcp add apifreaks -e APIFREAKS_API_KEY=your_apikey_here -- npx -y @apifreaks/mcp

Or edit the config file at ~/.claude/settings.json:

{
  "mcpServers": {
    "apifreaks": {
      "command": "npx",
      "args": [
        "-y",
        "@apifreaks/mcp"
      ],
      "env": {
        "APIFREAKS_API_KEY": "your_apikey_here"
      }
    }
  }
}

Claude Desktop

Edit claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "apifreaks": {
      "command": "npx",
      "args": [
        "-y",
        "@apifreaks/mcp"
      ],
      "env": {
        "APIFREAKS_API_KEY": "your_apikey_here"
      }
    }
  }
}

Restart Claude Desktop after you save.

Codex CLI

codex mcp add apifreaks --env APIFREAKS_API_KEY=your_apikey_here -- npx -y @apifreaks/mcp

Start a new Codex session after you add the server.

Gemini CLI

Edit ~/.gemini/settings.json, or .gemini/settings.json in your project root for project-level config:

{
  "mcpServers": {
    "apifreaks": {
      "command": "npx",
      "args": [
        "-y",
        "@apifreaks/mcp"
      ],
      "env": {
        "APIFREAKS_API_KEY": "your_apikey_here"
      }
    }
  }
}

Cursor

Create or edit .cursor/mcp.json in your project root, or ~/.cursor/mcp.json for a global setup:

{
  "mcpServers": {
    "apifreaks": {
      "command": "npx",
      "args": [
        "-y",
        "@apifreaks/mcp"
      ],
      "env": {
        "APIFREAKS_API_KEY": "your_apikey_here"
      }
    }
  }
}

You can also add it through the UI under Cursor Settings → MCP.

VS Code (GitHub Copilot / Continue)

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "apifreaks": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@apifreaks/mcp"
      ],
      "env": {
        "APIFREAKS_API_KEY": "your_apikey_here"
      }
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "apifreaks": {
      "command": "npx",
      "args": [
        "-y",
        "@apifreaks/mcp"
      ],
      "env": {
        "APIFREAKS_API_KEY": "your_apikey_here"
      }
    }
  }
}

Glama

The APIFreaks MCP server is listed on Glama. Click Connect on the listing and follow the prompts. Glama generates the right config for your client and connects it for you.

Example prompts for API Freaks MCP

You don't call tools by name. Ask in plain language and your assistant picks the right one, runs it, and works the answer into its reply.

Try asking:

Profile stripe.com completely. Give me the full WHOIS record with history, all DNS records (A, AAAA, MX, NS, TXT, CNAME), the SSL certificate chain and expiry, known subdomains, and any typosquatting domains similar to stripe that could be phishing risks. Also tell me which IPs it resolves to and whether they're anycast.
I'm investigating 8.8.8.8. Geolocate it, tell me the ASN, route prefix, and owner organisation, and check for any VPN, proxy, Tor, or bot flags. Then look up the IP WHOIS for the abuse contact. Finally, give me the capital city of that country, the current weather there, and the local currency's exchange rate to USD.
I got an email from contact@example.com. Validate the address, run SMTP verification, check the domain's MX and SPF/DKIM/DMARC records, and pull the WHOIS record to see who registered it and when. Tell me if this looks legitimate or risky.
Map tesla.com's attack surface. List all known subdomains, resolve them to IPs, check for anycast, pull SSL certificates, run the IPs through threat intelligence, and do reverse IP lookups to find other hostnames sharing those IPs. Organise everything by risk level.
Start with AS15169. Give me the organisation name, country, and all route prefixes. For each prefix pick a representative IP and get its geolocation, WHOIS record, abuse contact, and threat score. Also find the upstream ASNs it peers with and their route prefixes.
Audit github.com's DNS. Pull all current DNS records and compare with history from 2 years ago. Check SPF, DKIM, and DMARC. Reverse DNS lookup on its IPs to see what else is hosted there. Verify the SSL chain is complete and unexpired.
Find domains similar to google that might be typosquatting. For each, check WHOIS, registrar, creation date, resolve IPs, geolocate them, and flag any registered recently or hosted on known malicious ASNs. Also check if google.io, google.org, and google.co are available.
I'm travelling to ZIP 94105. Tell me the city, state, timezone, and local time. Give the 3-day weather forecast, local currency with USD exchange rate, and nearby ZIP codes within 10 miles. Also check what IP range serves that area and whether any appear in threat databases.

For every tool the server exposes, see Supported Tools.

Troubleshooting

A tool call returns an authentication error.

The server lists its tools even without a key, but every request needs one. Open your config, confirm APIFREAKS_API_KEY is set to a valid key from your dashboard, and restart the client.

command not found, or the server won't start.

Check that Node.js v20 or higher is installed with node -v. The server runs through npx, which ships with Node.

Still stuck? Email support@apifreaks.com or open an issue on GitHub.

FAQs

MCP, the Model Context Protocol, is an open standard that lets AI assistants connect to outside tools and data. The API Freaks MCP server uses it to give your assistant access to our APIs.

Yes. The server uses your key to reach the API Freaks API. Create one free and paste it into your client config as APIFREAKS_API_KEY.

The MCP server is free. The data it fetches spends credits from your API Freaks plan, the same as any API call you would make yourself, so cost depends on your usage. You can track credits through the usage endpoint. See API Freaks pricing for plan details.

The API is for code you write. The MCP server lets your assistant make those same calls for you, from a plain-language request, with no integration to build. Same data, no code.

No. Describe what you want and the assistant picks the right tool, runs it, and answers.

The server runs locally on your machine and your key stays in your own client config. Requests go straight from your machine to the API Freaks API, with nothing routed through a third party.

Any MCP-compatible client, including Claude, Cursor, VS Code, Gemini CLI, Codex CLI, and Windsurf. Setup steps for each are above.

API Freaks MCP Server

Why use API Freaks MCP?

One integration, the whole platform

The official server, built and maintained by us

No integration code to maintain

Before you start

Supported Tools

Platform Integrations

Claude

Claude Code (CLI)

Claude Desktop

Codex CLI

Gemini CLI

Cursor

VS Code (GitHub Copilot / Continue)

Windsurf

Glama

Example prompts for API Freaks MCP

Troubleshooting

A tool call returns an authentication error.

command not found, or the server won't start.

FAQ

FAQs

What is MCP?

Do I need an API Freaks API key?

How does pricing work?

How is this different from calling the API Freaks API directly?

Do I have to tell it which tool to use?

Is my API key safe?

Which apps does it work with?

API Freaks MCP Server

Why use API Freaks MCP?

One integration, the whole platform

The official server, built and maintained by us

No integration code to maintain

Before you start

Supported Tools

Platform Integrations

Claude

Claude Code (CLI)

Claude Desktop

Codex CLI

Gemini CLI

Cursor

VS Code (GitHub Copilot / Continue)

Windsurf

Glama

Example prompts for API Freaks MCP

Troubleshooting

A tool call returns an authentication error.

command not found, or the server won't start.

FAQ

FAQs

What is MCP?

Do I need an API Freaks API key?

How does pricing work?

How is this different from calling the API Freaks API directly?

Do I have to tell it which tool to use?

Is my API key safe?

Which apps does it work with?