Skip to content
Back to search

dataforseo-mcp-server

Run DataForSEO API tasks via the CLI in a shell (docs index, docs search, request). Use when the agent should execute terminal commands with npx dataforseo-mcp-server.

Safety scan

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

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dataforseo--mcp-server-typescript/badge.svg)](/listings/dataforseo--mcp-server-typescript)

HTML

<a href="/listings/dataforseo--mcp-server-typescript"><img src="/api/listings/dataforseo--mcp-server-typescript/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.

Start the MCP server on stdio (default mode; set `DATAFORSEO_LOGIN` / `DATAFORSEO_PASSWORD`):

npx dataforseo-mcp-server@latest

HTTP transport (port 3000; override with `PORT`):

npx dataforseo-mcp-server@latest --mode http

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.

SKILL.md · Manifest · 237 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. ---
  2. name: dataforseo-mcp-server
  3. description: >-
  4. Run DataForSEO API tasks via the CLI in a shell (docs index, docs search, request).
  5. Use when the agent should execute terminal commands with npx dataforseo-mcp-server.
  6. ---
  7. # DataForSEO MCP Server — LLM Agent Guide
  8. Run shell commands and read stdout/stderr. Always invoke the tool through the terminal — never substitute another integration path.
  9. ## How AI agents interact with this tool
  10. 1. **Invoke via shell** — use the terminal (Shell tool) to run `npx dataforseo-mcp-server …` commands.
  11. 2. **Read the output** — successful results are printed to stdout (JSON or documentation text). Errors go to stderr and exit code is non-zero.
  12. 3. **Auth for CLI** — set `DATAFORSEO_LOGIN` and `DATAFORSEO_PASSWORD` in the shell environment (fallback / CLI path; see Authentication below).
  13. **Binary name:** `npx dataforseo-mcp-server` (or `npx .` from this repo root after `npm install` + `npm run build`).
  14. **Working directory:** any directory where credentials are available in the environment (for CLI).
  15. ---
  16. ## Authentication
  17. | Mode | Preferred auth | Fallback |
  18. | ---- | -------------- | -------- |
  19. | MCP stdio (default when no CLI command; or `npx dataforseo-mcp-server` with no args) | Env credentials (HTTP Basic) | — |
  20. | HTTP MCP (`--mode http`) | OAuth 2.0 Bearer via authorization server `https://data.dataforseo.com` (discovery at `/.well-known/oauth-protected-resource`) | `DATAFORSEO_LOGIN` + `DATAFORSEO_PASSWORD` in env |
  21. | CLI (`docs` / `request` / `--cli`) | Env credentials (HTTP Basic) | — |
  22. Override the authorization server with `AUTH_SERVER_URL` if needed.
  23. ---
  24. ## Quick reference
  25. | Task | Shell command |
  26. | ---------------------------------- | --------------------------------------------------------------------------- |
  27. | Docs index | `npx dataforseo-mcp-server docs index [--section "SERP API"]` |
  28. | List sections | `npx dataforseo-mcp-server docs index --list-sections` |
  29. | Endpoint docs | `npx dataforseo-mcp-server docs search <url-or-path>` |
  30. | Endpoint docs (with code examples) | `npx dataforseo-mcp-server docs search <url-or-path> --need-code-example` |
  31. | GET request | `npx dataforseo-mcp-server request -X GET -p /v3/...` |
  32. | POST request | `npx dataforseo-mcp-server request -X POST -p <path> --param key=value ...` |
  33. | POST request (JSON) | `npx dataforseo-mcp-server request -X POST -p <path> -d '<json-array>'` |
  34. By default, API paths use the `.ai` suffix (e.g. `/v3/serp/google/organic/live/regular.ai`). Pass `--no-ai-mode` to use the standard path.
  35. **CLI credentials (fallback / shell):** set `DATAFORSEO_LOGIN` and `DATAFORSEO_PASSWORD` as environment variables. Get keys at [https://app.dataforseo.com/api-access](https://app.dataforseo.com/api-access)
  36. ```bash
  37. export DATAFORSEO_LOGIN=your_api_login
  38. export DATAFORSEO_PASSWORD=your_api_password
  39. ```
  40. Windows PowerShell: `$env:DATAFORSEO_LOGIN="..."` / `$env:DATAFORSEO_PASSWORD="..."`. CMD: `set DATAFORSEO_LOGIN=...`
  41. `DATAFORSEO_USERNAME` is also accepted as an alias for `DATAFORSEO_LOGIN`. For HTTP MCP, prefer OAuth; env credentials are only a fallback when no `Authorization` header is present.
  42. ---
  43. ## Agent workflow (shell)
  44. Run these steps as separate shell commands:
  45. 1. `npx dataforseo-mcp-server docs index --section "<API>"` — find endpoint path.
  46. 2. `npx dataforseo-mcp-server docs search <path>` — read method, parameters, example body.
  47. 3. `npx dataforseo-mcp-server request -X <METHOD> -p <path> --param key=value ...` (or `-d '<json-array>'`) — call API.
  48. Parse the printed output to decide the next step.
  49. ---
  50. ## POST body
  51. POST endpoints accept a **JSON array of task objects**: `[{ ... }]`.
  52. **Preferred:** pass fields with repeatable `--param key=value` (merged into the first task object). Use exact API field names from endpoint docs (e.g. `keyword`, `language_code`, `location_code`).
  53. `--param` values override the same fields in `-d` JSON when both are used.
  54. **Array values** (PowerShell strips `"` inside `[...]`, so prefer these forms):
  55. ```bash
  56. # single-item array
  57. --param keywords=[phone]
  58. # multiple items (pipe-separated)
  59. --param keywords=[phone|tablet|laptop]
  60. # or repeat the same key
  61. --param keywords=phone --param keywords=tablet
  62. # order_by with comma inside the value
  63. --param order_by=[keyword_info.search_volume,desc]
  64. ```
  65. Valid JSON in `--param` still works when your shell preserves quotes (bash: `'keywords=["phone"]'`).
  66. ### Example: Live SERP (`/v3/serp/google/organic/live/regular`)
  67. ```bash
  68. npx dataforseo-mcp-server request -X POST -p /v3/serp/google/organic/live/regular \
  69. --param keyword=dataforseo --param language_code=en --param location_code=2840
  70. ```
  71. JSON form:
  72. ```bash
  73. npx dataforseo-mcp-server request -X POST -p /v3/serp/google/organic/live/regular -d '[{\"keyword\":\"dataforseo\",\"location_code\":2840,\"language_code\":\"en\"}]'
  74. ```
  75. ---
  76. ## Installation (once per environment)
  77. ```bash
  78. cd /path/to/mcp-server-typescript
  79. npm install
  80. npm run build
  81. export DATAFORSEO_LOGIN=your_api_login
  82. export DATAFORSEO_PASSWORD=your_api_password
  83. npx dataforseo-mcp-server --help
  84. ```
  85. From a project with CLI as a dependency:
  86. ```bash
  87. cd /path/to/your-project
  88. npm install
  89. export DATAFORSEO_LOGIN=your_api_login
  90. export DATAFORSEO_PASSWORD=your_api_password
  91. npx dataforseo-mcp-server docs index --list-sections
  92. ```
  93. Dev without build (CLI repo only): `npm run dev -- docs index`
  94. ---
  95. ## Commands reference
  96. ### docs index
  97. ```bash
  98. npx dataforseo-mcp-server docs index
  99. npx dataforseo-mcp-server docs index --section "SERP API"
  100. npx dataforseo-mcp-server docs index --list-sections
  101. npx dataforseo-mcp-server docs index --cache-dir D:\my-docs-cache
  102. ```
  103. Sections: SERP API, AI Optimization API, Keywords Data API, Domain Analytics API, DataForSEO Labs API, OnPage API, Backlinks API, Content Analysis API, Merchant API, App Data API, Business Data API, Databases, Appendix.
  104. ### docs search
  105. ```bash
  106. npx dataforseo-mcp-server docs search serp/google/organic/live/regular
  107. npx dataforseo-mcp-server docs search https://docs.dataforseo.com/v3/on_page/instant_pages
  108. npx dataforseo-mcp-server docs search backlinks/referring_networks/live --need-code-example
  109. npx dataforseo-mcp-server docs search serp/google/organic/live/regular --cache-dir D:\my-docs-cache
  110. ```
  111. Accepts a documentation URL or a path relative to `https://docs.dataforseo.com/v3/`. The `.md` suffix is optional. Pass `--need-code-example` to include full code examples.
  112. ### Documentation cache
  113. `docs index` and `docs search` cache fetched documentation for **24 hours**.
  114. | Override | Example |
  115. | ----------------- | ------------------------------------------------- |
  116. | Default (Windows) | `%LOCALAPPDATA%\dataforseo-mcp-server\docs-cache` |
  117. | CLI flag | `--cache-dir D:\my-cache` |
  118. | MCP startup arg | `--docs-cache-dir D:\my-cache` in server `args` |
  119. If not overridden, the platform default directory is used.
  120. ### request
  121. | Option | Description |
  122. | --------------------- | ---------------------------------------------------------- |
  123. | `-X, --method` | GET, POST, PUT, DELETE (required) |
  124. | `-p, --path` | `/v3/serp/google/organic/live/regular` |
  125. | `-u, --url` | Full URL (alternative to `-p`) |
  126. | `-d, --data` | JSON body (POST/PUT) |
  127. | `--param <key=value>` | Request field (repeatable; merged into first task) |
  128. | `--no-ai-mode` | Use standard API path without `.ai` (default: `.ai` is on) |
  129. Response output is the API response body (parsed JSON when possible). Optional field filtering via `--configuration field-config.json` / `FIELD_CONFIG_PATH` (keys = endpoint paths; see `field-config.example.json`).
  130. ---
  131. ## DataForSEO API basics
  132. - **API base:** `https://api.dataforseo.com`
  133. - **Docs base:** `https://docs.dataforseo.com/v3`
  134. - **Auth:** OAuth Bearer preferred on HTTP MCP; HTTP Basic via `DATAFORSEO_LOGIN`/`DATAFORSEO_PASSWORD` as fallback (and for CLI/stdio)
  135. - **POST body:** JSON from endpoint documentation
  136. - **Response:** `status_code` `20000` = OK; each task has `id`, `status_code`, `result`
  137. - **Standard vs Live:** Standard = POST task then GET by id; Live = one POST returns results
  138. - **Errors:** `npx dataforseo-mcp-server docs search appendix/errors`
  139. | Product | Use case |
  140. | -------------------- | ----------------------------------- |
  141. | SERP API | Search results (Google, Bing, etc.) |
  142. | Keywords Data API | Search volume, suggestions |
  143. | DataForSEO Labs API | Keyword research, competitors |
  144. | Backlinks API | Backlink profiles |
  145. | OnPage API | Site crawl, audit, instant pages |
  146. | Domain Analytics API | Domain metrics, WHOIS |
  147. | Content Analysis API | Brand mentions |
  148. | Merchant API | Google Shopping data |
  149. | Business Data API | GBP, reviews |
  150. | App Data API | App Store / Play Store |
  151. | AI Optimization API | LLM mention tracking |
README.md · README · 319 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # DataForSEO MCP Server
  2. > **This is the new v3 MCP server.** The previous v2+ MCP server is **deprecated** and lives at [dataforseo/mcp-server-typescript-deprecated](https://github.com/dataforseo/mcp-server-typescript-deprecated).
  3. MCP server and CLI for LLM agents to browse DataForSEO API documentation and make authenticated API requests. By default the binary starts an MCP server on stdio; CLI commands are an optional second mode.
  4. ## Quick Start
  5. Start the MCP server on stdio (default mode; set `DATAFORSEO_LOGIN` / `DATAFORSEO_PASSWORD`):
  6. ```bash
  7. npx dataforseo-mcp-server@latest
  8. ```
  9. HTTP transport (port 3000; override with `PORT`):
  10. ```bash
  11. npx dataforseo-mcp-server@latest --mode http
  12. ```
  13. ## Authentication
  14. **OAuth 2.0 (default for HTTP MCP):** works out of the box. MCP clients discover the DataForSEO authorization server via Protected Resource metadata and send `Authorization: Bearer` tokens.
  15. **Fallback:** API login/password via environment variables (HTTP Basic). Required for CLI and stdio MCP; on HTTP it is used when no `Authorization` header is present.
  16. ```bash
  17. # bash / macOS / Linux
  18. export DATAFORSEO_LOGIN="your_api_login"
  19. export DATAFORSEO_PASSWORD="your_api_password"
  20. ```
  21. ```powershell
  22. # PowerShell
  23. $env:DATAFORSEO_LOGIN="your_api_login"
  24. $env:DATAFORSEO_PASSWORD="your_api_password"
  25. ```
  26. ```cmd
  27. REM CMD
  28. set DATAFORSEO_LOGIN=your_api_login
  29. set DATAFORSEO_PASSWORD=your_api_password
  30. ```
  31. `DATAFORSEO_USERNAME` is accepted as an alias for `DATAFORSEO_LOGIN`. Get API keys at [https://app.dataforseo.com/api-access](https://app.dataforseo.com/api-access).
  32. ## MCP Server
  33. The same tool implementations power both the MCP server and the CLI. One binary serves both modes; MCP is the default.
  34. **How the binary chooses a mode:**
  35. - MCP stdio — default when no CLI command is passed
  36. - MCP HTTP — pass `--mode http` (Streamable HTTP on port 3000; override with `PORT`)
  37. - CLI — when the first command is `docs` or `request`, or when `--cli` / `--help` / `--version` is passed
  38. MCP stdio (default):
  39. ```bash
  40. npx dataforseo-mcp-server
  41. ```
  42. MCP HTTP:
  43. ```bash
  44. npx dataforseo-mcp-server --mode http
  45. ```
  46. CLI:
  47. ```bash
  48. npx dataforseo-mcp-server docs index
  49. ```
  50. **MCP client config** (Cursor, Claude Desktop, and similar clients that use `mcpServers`):
  51. Via URL — use the hosted remote MCP server, or start a local HTTP server (`npx dataforseo-mcp-server --mode http`) and point the client at it. OAuth works out of the box; env credentials are optional fallback only.
  52. Public remote MCP server URL: [https://mcp.dataforseo.com/v3/mcp](https://mcp.dataforseo.com/v3/mcp)
  53. ```json
  54. {
  55. "mcpServers": {
  56. "dataforseo": {
  57. "url": "https://mcp.dataforseo.com/v3/mcp"
  58. }
  59. }
  60. }
  61. ```
  62. Local server (default port 3000):
  63. ```json
  64. {
  65. "mcpServers": {
  66. "dataforseo": {
  67. "url": "http://localhost:3000/mcp"
  68. }
  69. }
  70. }
  71. ```
  72. Via `command` (stdio) — the client starts the binary itself (stdio is the default mode). OAuth is not used on this transport — set env credentials (or pass them in the MCP client `env` block):
  73. ```jsonc
  74. {
  75. "mcpServers": {
  76. "dataforseo": {
  77. "command": "npx",
  78. "args": [
  79. "dataforseo-mcp-server",
  80. // Optional additional args:
  81. // "--docs-cache-dir", "D:\\my-docs-cache",
  82. // "--configuration", "field-config.json"
  83. ],
  84. "env": {
  85. "DATAFORSEO_LOGIN": "your_api_login",
  86. "DATAFORSEO_PASSWORD": "your_api_password",
  87. // Optional additional env:
  88. // "FIELD_CONFIG_PATH": "field-config.json"
  89. }
  90. }
  91. }
  92. }
  93. ```
  94. From the repo root during development:
  95. ```json
  96. {
  97. "mcpServers": {
  98. "dataforseo": {
  99. "command": "npx",
  100. "args": ["tsx", "src/index.ts"],
  101. "cwd": "/path/to/mcp-server-typescript"
  102. }
  103. }
  104. }
  105. ```
  106. ### MCP Tools
  107. | Tool | Title | Description |
  108. |------|-------|-------------|
  109. | `docs_index` | Docs Index | Fetch documentation index, optionally filtered by section (24h cache) |
  110. | `docs_list_sections` | Docs List Sections | Return available documentation section names |
  111. | `docs_search` | Docs Search | Fetch documentation from a documentation URL (`needCodeExample`, 24h cache) |
  112. | `api_request` | API Request | Make an authenticated API request |
  113. `api_request` uses `.ai` paths by default. Set `noAiMode` to `true` in MCP requests, or pass `--no-ai-mode` in the CLI, to use the standard path. Request body is passed as `data` (JSON object or array). The `--param` option is CLI-only.
  114. ### HTTP transport
  115. Streamable HTTP endpoints:
  116. - `POST /mcp`
  117. - `POST /http`
  118. OAuth 2.0 Protected Resource metadata (RFC 9728) is **always** exposed so MCP clients can discover the authorization server and authenticate with Bearer tokens:
  119. - `GET /.well-known/oauth-protected-resource`
  120. - `GET /.well-known/oauth-protected-resource/mcp`
  121. - `GET /.well-known/oauth-protected-resource/http`
  122. Behind a reverse proxy, set `TRUST_PROXY=true` so metadata URLs use `https`.
  123. Auth priority on HTTP requests:
  124. 1. `Authorization: Basic` header
  125. 2. `Authorization: Bearer` header (OAuth access token)
  126. 3. Env credentials (`DATAFORSEO_LOGIN` / `DATAFORSEO_PASSWORD`) — fallback when no `Authorization` header is sent
  127. ## CLI (optional)
  128. In addition to MCP, the same binary exposes `docs` and `request` as CLI commands.
  129. ### Commands
  130. | Command | Description |
  131. |---------|-------------|
  132. | `npx dataforseo-mcp-server docs index` | Fetch full API documentation index |
  133. | `npx dataforseo-mcp-server docs index --section "SERP API"` | Filter index by API section |
  134. | `npx dataforseo-mcp-server docs index --list-sections` | List available sections |
  135. | `npx dataforseo-mcp-server docs search <url>` | Fetch documentation from a documentation URL or path (cURL example only by default) |
  136. | `npx dataforseo-mcp-server docs search <url> --need-code-example` | Fetch documentation with PHP, Node.js, Python, and C# examples |
  137. | `npx dataforseo-mcp-server request -X <method> -p <path>` | Make an authenticated API request (`.ai` path by default) |
  138. From a built local clone you can also use `npx .` instead of `npx dataforseo-mcp-server`.
  139. ### Examples
  140. ```bash
  141. # Browse SERP API endpoints
  142. npx dataforseo-mcp-server docs index --section "SERP API"
  143. # Read endpoint documentation (path or full docs URL)
  144. npx dataforseo-mcp-server docs search serp/google/organic/live/regular
  145. npx dataforseo-mcp-server docs search https://docs.dataforseo.com/v3/serp/google/organic/live/regular
  146. # Include multi-language code examples (PHP, Node.js, Python, C#)
  147. npx dataforseo-mcp-server docs search backlinks/referring_networks/live --need-code-example
  148. # Live SERP request (recommended: use --param)
  149. npx dataforseo-mcp-server request -X POST -p /v3/serp/google/organic/live/regular \
  150. --param keyword=dataforseo --param language_code=en --param location_code=2840
  151. # Same request via JSON body
  152. npx dataforseo-mcp-server request -X POST -p /v3/serp/google/organic/live/regular \
  153. -d '[{"keyword":"dataforseo","location_code":2840,"language_code":"en"}]'
  154. ```
  155. Documentation responses are cached for **24 hours**. Default cache directory:
  156. - **Windows:** `%LOCALAPPDATA%\dataforseo-mcp-server\docs-cache`
  157. - **macOS:** `~/Library/Caches/dataforseo-mcp-server/docs-cache`
  158. - **Linux:** `~/.cache/dataforseo-mcp-server/docs-cache` (or `$XDG_CACHE_HOME`)
  159. Override with `--cache-dir <path>` on CLI `docs` commands. For MCP, pass `--docs-cache-dir <path>` in server startup `args`.
  160. API responses are returned as the response body only (parsed JSON when possible). When a field configuration is loaded, `api_request` / `request` responses are trimmed to the configured fields for that endpoint path (see [Field configuration](#field-configuration)).
  161. ## Field configuration
  162. Optionally limit which fields are returned from API responses. Unlike the previous multi-tool MCP server (keys = tool names), this package keys the config by **API endpoint path**.
  163. ```bash
  164. # MCP stdio (default when no CLI command is passed)
  165. npx dataforseo-mcp-server --configuration field-config.json
  166. # MCP HTTP
  167. npx dataforseo-mcp-server --mode http --configuration field-config.json
  168. # CLI
  169. npx dataforseo-mcp-server --configuration field-config.json request -X POST -p /v3/backlinks/summary/live --param target=example.com
  170. ```
  171. Or set env:
  172. - `FIELD_CONFIG_PATH` — path to a JSON file (Node)
  173. - `FIELD_CONFIG_JSON` — inline JSON string (Node / Cloudflare Worker)
  174. Minimal example (see `field-config.example.json` for a fuller sample):
  175. ```json
  176. {
  177. "supported_fields": {
  178. "/v3/serp/google/organic/live/advanced": ["id", "items.title", "items.url", "status_code"],
  179. "/v3/backlinks/summary/live": ["id", "items.backlinks", "items.referring_domains", "status_code"]
  180. }
  181. }
  182. ```
  183. Behavior:
  184. - Built-in defaults always apply for `/v3/on_page/lighthouse/live/json` (shrunk Lighthouse payload). Custom config merges on top and can override any path.
  185. - Path match ignores `.ai` suffix, trailing slash, and host (full URLs work).
  186. - If the path is configured with a non-empty field list → only those fields are kept (applied to each `tasks[].result[]` item).
  187. - If the path has an empty field list `[]` → full response for that path (disables filtering).
  188. - If the path is missing from both defaults and custom config → full response.
  189. Copy the example and trim to the endpoints you use:
  190. ```bash
  191. cp field-config.example.json my-config.json
  192. ```
  193. ## Architecture
  194. ```
  195. src/
  196. ├── index.ts # Unified entry (MCP by default stdio; CLI if docs/request/--cli)
  197. ├── config/ # URLs, sections, auth server
  198. ├── core/
  199. │ ├── api/ # auth, client, path, request-body
  200. │ ├── cli/ # program, error, output
  201. │ ├── config/ # field configuration + defaults
  202. │ ├── docs/ # path, section, cache
  203. │ ├── http/ # fetch
  204. │ ├── mcp/ # startup args (--configuration, --docs-cache-dir)
  205. │ ├── tools/ # shared CLI + MCP tool implementations
  206. │ ├── utils/ # field filter
  207. │ ├── env.ts
  208. │ └── version.ts
  209. ├── mcp/
  210. │ ├── init-mcp-server.ts
  211. │ ├── tool-definition.ts
  212. │ ├── auth-middleware.ts
  213. │ ├── http-routes.ts
  214. │ ├── index.ts # stdio transport
  215. │ └── index-http.ts # streamable HTTP
  216. └── worker/ # Cloudflare Worker entry (built separately)
  217. ```
  218. ### Build outputs
  219. | Target | Command | Output | Used by |
  220. |--------|---------|--------|---------|
  221. | Node (MCP + CLI) | `npm run build` (`tsc`) | `dist/index.js` | `bin`, Docker, `start*` scripts |
  222. | Cloudflare Worker | `npm run worker:build` | `build/worker/worker/index-worker.js` | `wrangler.jsonc` → `main` |
  223. Worker path is `build/worker/worker/...` because `tsconfig.worker.json` sets `rootDir` to `src` and the entry lives at `src/worker/index-worker.ts`.
  224. ## For LLM Agents
  225. Read [SKILL.md](./SKILL.md) in this repo for full agent instructions.
  226. ## Development
  227. Requires Node.js 20+.
  228. ```bash
  229. npm install
  230. npm run build
  231. # Dev (tsx, no build step)
  232. npm run dev # MCP stdio (default)
  233. npm run dev:mcp:http # MCP HTTP
  234. npm run dev -- docs index --section "SERP API" # CLI
  235. # After build
  236. npm run start # MCP stdio (default)
  237. npm run start:mcp:http # Streamable HTTP
  238. npx . docs index --list-sections
  239. ```

Ratings and comments

Sign in to rate this skill.

Sign in

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