FreeTools
Every tool on this page is also a free JSON API — a plain
GET request with no API key, no account and no tracking. Use
them in the browser, from a terminal, or wire them into an AI agent through the
MCP server. Repository results are cached for six hours and refreshed in the
background, so repeat LOC and star-history calls return quickly.
These tools cover the things you actually look up during development: how big a codebase really is, how a project's popularity is trending, whether a site's certificate and headers are healthy, and enough geolocation and weather data to build a demo without signing up for anything.
Count LOC breaks any public GitHub or GitLab
repository down by language, splitting lines of code from blanks and comments and skipping
vendor, build and generated directories. Add detail=1 and you also get a per-file
list and a breakdown by file extension, which is often more revealing than the language mix.
Read the LOC guide for the details.
Star History plots cumulative stars from the repository's creation to today, compares up to six repositories at once, and exports an SVG you can embed in a README with one line of Markdown. See how to add a live chart to your README.
Use the TLS checker for protocol version, cipher strength and days until a certificate expires, and the HTTP headers checker for HSTS, CSP and the whole redirect chain. The security headers checklist explains what each one actually prevents.
Geolocate an IP with the IP geolocation API, fetch current conditions from the weather API, and generate test data with the random data API — up to 10,000 values per request from the operating system CSPRNG.
No. Every endpoint is a plain GET request with no authentication. Add the MCP server at /mcp if you want an AI agent to call them as native tools.
30 requests per minute per IP address, and 300 per minute for the random-data endpoints. LOC and star-history results are cached for six hours; other endpoints should be cached by your application when appropriate.
It resolves every hostname, rejects private and link-local ranges, and re-validates every redirect hop, so it is protected against SSRF. Still, do not route production traffic or credentials through any third-party proxy.
Yes. Every tool is a REST endpoint returning JSON, and there is an OpenAPI spec at /openapi.json plus a machine-readable index at /api.json.
Guides & tutorials — how-to articles with runnable code examples
Every tool is a plain GET JSON API — no key, no signup.
MCP server: https://freetools.one/mcp
{
"mcpServers": {
"freetools": { "url": "https://freetools.one/mcp" }
}
}