# Url Parse — REST API endpoint `url-parse`

Parse a URL into its components: protocol, host, port, pathname, query (as an object, repeat keys become arrays), hash, origin, and userinfo.

- Category: data
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/url-parse/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/url-parse/
- Same tool on the other surface: https://findutils.com/mcp/url-parse/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/url-parse/execute \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://findutils.com/x?y=1"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/url-parse
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `url` | string | yes | The URL to parse. |

Example arguments (verified):

```json
{
  "url": "https://findutils.com/x?y=1"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:url_parse`. Full MCP reference: https://findutils.com/mcp/url-parse/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt