Skip to content
Back to search

mcp

Run website and network tests from locations around the world, straight from Claude, Cursor, VS Code and other AI assistants that support the Model Context Protocol.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dotcom-tools--mcp/badge.svg)](/listings/dotcom-tools--mcp)

HTML

<a href="/listings/dotcom-tools--mcp"><img src="/api/listings/dotcom-tools--mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Dotcom-Tools hosts the MCP server at `https://www.dotcom-tools.com/mcp`. Clients that support remote (HTTP) servers can connect to it directly; this package is for clients that run local (stdio) servers. Both give you the same tools.

Claude Code

claude mcp add --transport http dotcom-tools https://www.dotcom-tools.com/mcp --header "X-Api-Key: YOUR_KEY"

Claude Desktop

In `claude_desktop_config.json`:

{
  "mcpServers": {
    "dotcom-tools": {
      "command": "npx",
      "args": ["-y", "@dotcom-tools/mcp"],
      "env": { "DOTCOM_TOOLS_API_KEY": "YOUR_KEY" }
    }
  }
}

Cursor

In `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project):

{
  "mcpServers": {
    "dotcom-tools": {
      "url": "https://www.dotcom-tools.com/mcp",
      "headers": { "X-Api-Key": "YOUR_KEY" }
    }
  }
}

VS Code

In `.vscode/mcp.json`; VS Code asks for the key once and stores it securely:

{
  "inputs": [
    { "type": "promptString", "id": "dotcom-tools-key", "description": "Dotcom-Tools API key", "password": true }
  ],
  "servers": {
    "dotcom-tools": {
      "type": "http",
      "url": "https://www.dotcom-tools.com/mcp",
      "headers": { "X-Api-Key": "${input:dotcom-tools-key}" }
    }
  }
}

Any other client

Remote: `https://www.dotcom-tools.com/mcp` (Streamable HTTP) with the header `X-Api-Key: YOUR_KEY`. Local: run `npx -y @dotcom-tools/mcp` with the environment variable `DOTCOM_TOOLS_API_KEY`.

| Environment variable | | |---|---| | `DOTCOM_TOOLS_API_KEY` | Required. Your API key. | | `DOTCOM_TOOLS_URL` | Optional. The server address, default `https://www.dotcom-tools.com/mcp`. |

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 131 lines
  1. # Dotcom-Tools MCP server
  2. Run website and network tests from locations around the world, straight from Claude, Cursor, VS Code and other AI
  3. assistants that support the [Model Context Protocol](https://modelcontextprotocol.io).
  4. Ask things like:
  5. - "Is example.com slow in Europe and Asia? Check Core Web Vitals."
  6. - "Ping 1.1.1.1 from three continents."
  7. - "Trace the route to api.example.com from Tokyo and tell me where the latency jumps."
  8. - "Is mail.example.com's SMTP server answering on 587 with STARTTLS?"
  9. - "Is 203.0.113.10 on any email blacklist?"
  10. The assistant runs the test on [Dotcom-Tools](https://www.dotcom-tools.com) and gets a short summary per location, plus a
  11. link to the full result page (waterfall, video, Lighthouse report, maps).
  12. ## Tools
  13. | Tool | What it does |
  14. |---|---|
  15. | `run_test` | Runs a test from one or more locations (by name, such as "London", or picked automatically across regions). Waits up to 60 s and returns a summary per location. |
  16. | `get_test_result` | A test's summary, or every field for one location (`detail: "full"`). |
  17. | `list_tests` | Your recent tests. |
  18. | `list_test_types` | Every test type with its settings, cost and time limit. |
  19. | `list_locations` | The locations available now. |
  20. | `get_credits` | Your plan and the credits you can spend. |
  21. Test types: website speed (Chrome page load with Core Web Vitals and Lighthouse; desktop or mobile), ping, traceroute,
  22. DNS trace, web server (HTTP timings), email server (SMTP/POP3/IMAP), email blacklist, FTP and streaming media
  23. (HLS/DASH).
  24. ## Get an API key
  25. API keys are free. [Create an account](https://www.dotcom-tools.com/register), then create a key on your
  26. [account page](https://www.dotcom-tools.com/account#api). Tests spend the same credits as tests on the website: a free
  27. account gets a daily allowance and up to 5 locations per test; [paid plans](https://www.dotcom-tools.com/pricing) add
  28. credits and every location.
  29. ## Setup
  30. Dotcom-Tools hosts the MCP server at `https://www.dotcom-tools.com/mcp`. Clients that support remote (HTTP) servers
  31. can connect to it directly; this package is for clients that run local (stdio) servers. Both give you the same tools.
  32. ### Claude Code
  33. ```sh
  34. claude mcp add --transport http dotcom-tools https://www.dotcom-tools.com/mcp --header "X-Api-Key: YOUR_KEY"
  35. ```
  36. ### Claude Desktop
  37. In `claude_desktop_config.json`:
  38. ```json
  39. {
  40. "mcpServers": {
  41. "dotcom-tools": {
  42. "command": "npx",
  43. "args": ["-y", "@dotcom-tools/mcp"],
  44. "env": { "DOTCOM_TOOLS_API_KEY": "YOUR_KEY" }
  45. }
  46. }
  47. }
  48. ```
  49. ### Cursor
  50. In `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project):
  51. ```json
  52. {
  53. "mcpServers": {
  54. "dotcom-tools": {
  55. "url": "https://www.dotcom-tools.com/mcp",
  56. "headers": { "X-Api-Key": "YOUR_KEY" }
  57. }
  58. }
  59. }
  60. ```
  61. ### VS Code
  62. In `.vscode/mcp.json`; VS Code asks for the key once and stores it securely:
  63. ```json
  64. {
  65. "inputs": [
  66. { "type": "promptString", "id": "dotcom-tools-key", "description": "Dotcom-Tools API key", "password": true }
  67. ],
  68. "servers": {
  69. "dotcom-tools": {
  70. "type": "http",
  71. "url": "https://www.dotcom-tools.com/mcp",
  72. "headers": { "X-Api-Key": "${input:dotcom-tools-key}" }
  73. }
  74. }
  75. }
  76. ```
  77. ### Any other client
  78. Remote: `https://www.dotcom-tools.com/mcp` (Streamable HTTP) with the header `X-Api-Key: YOUR_KEY`.
  79. Local: run `npx -y @dotcom-tools/mcp` with the environment variable `DOTCOM_TOOLS_API_KEY`.
  80. | Environment variable | |
  81. |---|---|
  82. | `DOTCOM_TOOLS_API_KEY` | Required. Your API key. |
  83. | `DOTCOM_TOOLS_URL` | Optional. The server address, default `https://www.dotcom-tools.com/mcp`. |
  84. ## Limits and privacy
  85. - Each key can make 120 requests and start 10 tests a minute.
  86. - Only public addresses can be tested.
  87. - Test settings you pass (such as a login for an email server) are encrypted at rest and masked in results. The server
  88. doesn't log tool arguments.
  89. - This package only relays messages between your client and the Dotcom-Tools server. It logs nothing but connection
  90. errors, to stderr.
  91. See the [MCP documentation](https://www.dotcom-tools.com/docs/mcp) and the [REST API](https://www.dotcom-tools.com/docs/api),
  92. which the same key works with.
  93. ## Development
  94. ```sh
  95. npm install
  96. npm test # builds, then runs the bridge against a mock server
  97. ```
  98. ## License
  99. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.