Skip to content
BEAD

URL Parser

Break a URL into protocol, host, path, query parameters, and fragment.

WebDeveloper
Protocol
https
Username
user
Password
pass
Host
www.example.com:8080
Hostname
www.example.com
Port
8080
Origin
https://www.example.com:8080
Pathname
/path/to/page
Search
?id=42&q=hello%20world&tags=a&tags=b
Hash
#section
Query parameters (4)
id42
qhello world
tagsa
tagsb
</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl
curl https://api.b-e-a-d.com/tools/url-parser/run \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://example.com"
}'
JavaScript (fetch)
const res = await fetch("https://api.b-e-a-d.com/tools/url-parser/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "url": "https://example.com"
}),
});
const data = await res.json();
console.log(data.result);
MCP (Claude Desktop / Claude Code)
# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_url_parser

Full reference: developer docs · OpenAPI spec

Frequently asked

▸What does the parser actually return?

Everything you'd get from the WHATWG URL standard: protocol, host, port, pathname, search, hash, plus a flattened params object with array values for repeated keys. The output is JSON, so it pipes cleanly into JSON Formatter or any downstream workflow.

▸Does it decode percent-encoded values?

Query parameter values are URI-decoded for the params object, so %20 becomes a space, %3D becomes =, and so on. The raw search string preserves the encoded form so you can copy it back if needed.

▸What about non-HTTP URLs?

Any URL the WHATWG parser accepts works — including mailto:, ftp:, sftp:, ssh:, custom schemes, and data: URIs. Note that scheme-less URLs (no protocol) won't parse.

You might also like

Used in these workflows