How to Give Claude and Cursor Web Diagnostic Tools

Short answer. Connect Claude Desktop or Cursor to the enterno.io MCP server and the assistant gains 49 diagnostic tools: SSL, DNS, HTTP headers, ping, WHOIS, a security scanner, and more. Setup takes a couple of minutes: add the URL https://enterno.io/mcp and your API key to the config, restart the client, and ask it to check a domain in plain text. Every tool call needs the key, but it's free on any plan and issued after sign-up.

Why this beats copy-pasting

Without tools, an assistant can't run a real check — it either refuses or guesses. The usual workaround is running utilities by hand and pasting the output into chat. That's slow and goes stale fast. An MCP server gives the assistant direct access to tools, so it runs the checks itself whenever they're needed to answer.

With an MCP server connected, Claude stops hallucinating about headers and SSL — it actually checks them and answers from facts.

Step 1. Open your client config

• Claude Desktop — the claude_desktop_config.json file (there's an "Edit Config" button in app settings).
• Cursor — the mcp.json file in your project directory or in global settings.
• Zed — the MCP settings section in the editor config.

Step 2. Add the server

First get an API key: it's free on any plan and issued after you sign up, in the Integrations section. Without a key the server answers 401 to any tool call. For Cursor, put a block with the server URL and a header into mcp.json — the key is read from the ENTERNO_API_KEY environment variable:

{
  "mcpServers": {
    "enterno": {
      "url": "https://enterno.io/mcp",
      "headers": { "Authorization": "Bearer ${env:ENTERNO_API_KEY}" }
    }
  }
}

Claude Desktop connects a remote server with a key through the mcp-remote bridge (requires Node.js). The block for claude_desktop_config.json — replace ent_your_key with your key:

{
  "mcpServers": {
    "enterno": {
      "command": "npx",
      "args": ["-y", "mcp-remote@0.15.1", "https://enterno.io/mcp", "--header", "Authorization:${ENTERNO_AUTH}"],
      "env": { "ENTERNO_AUTH": "Bearer ent_your_key" }
    }
  }
}

Configs for Zed and other clients are in the examples repository. Save the file and restart the client. After the restart, the server's tools appear in the list available to the assistant.

Step 3. Verify the tools connected

Ask the assistant which tools it has, or just hand it a task. If the server is connected, the response will include tool calls rather than invented text.

Check the SSL chain and DNS for example.com
and tell me if the security headers are fine.

This prompt makes the assistant call the SSL, DNS, and security tools and merge the results into a single analysis.

What the assistant actually gets

That's 49 tools in total. The server is free on any plan; all it needs is a free API key.

Programmatic access without a client

If you're building your own agent instead of using a ready client, call the server directly over JSON-RPC 2.0: POST https://enterno.io/mcp with an Authorization: Bearer ent_… header, methods tools/list and tools/call. The same checks are available through the REST API v4 — handy for scripts and CI integration.

Security rule: only give your agent servers you trust, and review the tool list before connecting. The enterno.io diagnostic tools make outbound checks only and never touch your data.

Common setup mistakes

• Forgot to restart the client — config changes apply only after a restart.
• Broken JSON — a stray comma or quote breaks the whole file; validate it.
• Wrong config path — every client has its own file; make sure you're editing the right one.
• Missing or mistyped API key — the server answers 401; check the Authorization: Bearer ent_… header.

What to try after connecting

Ask the assistant to check your site's HTTP headers, assess API security, or run an AI-readiness check. The assistant runs the real checks and explains the findings.

FAQ

Does this work only in Claude?

No. MCP is an open standard: Claude Desktop, Cursor, Zed, and other compatible clients connect the same way.

Do I need to install anything?

For Cursor and other clients with remote MCP support — no, just the URL and API key in the config. Claude Desktop runs the mcp-remote bridge via npx, which requires Node.js. Your own agent needs nothing installed: the server takes plain HTTP requests over JSON-RPC 2.0.

How much does it cost?

The server is free on any plan; you need a free API key. On top of that, enterno.io offers 10 free monitors and 68+ free on-site tools.

Is it safe to connect?

The diagnostic tools make outbound checks against third-party URLs only, with SSRF protection. They have no access to your code or data.

Can I use it in CI?

Yes — call the tools from scripts directly over JSON-RPC 2.0 (POST https://enterno.io/mcp, method tools/call) or through the REST API v4, for example to check SSL before a deploy. Keep the API key in your CI secrets.

Connect the enterno.io MCP server →