About Toolcore

Toolcore is for developers, technical teams, and people doing everyday desk work —engineering, operations, content, and admin—who want fast, dependable utilities in one place: formatting and comparing data, converting formats, encoding, hashing, working with media, quick calculations, and similar tasks.

The default is in-browser processing so your input stays on your device unless a tool clearly needs the server. Where a route uses AI-assisted or other server-side logic, the page states it clearly. Automation is supported too: public tool lists and prefilled URLs let assistants open the same pages people use—see AI agents and automation and the sections below.

Search visitors often open these tools first—they are fully cataloged with examples, FAQs, and related links. For a task map across the recent long-tail expansion, see GSC cluster tools guide.

What you'll find here

The sections below are curated highlights from the home catalog. Broad groups include Media, JSON, Calculators, and Data & text (encoding, crypto, compress, regex, identifiers, and AI-assisted helpers where useful).

When you sign in, you can pin a small set of tools on the home page for expandable inline panels (the same UI clients as the full-page tools). The catalog also gives automations a clear public URL to open when a workflow needs to hand off a small task.

Compared with typical tool sites

Plenty of one-off utility pages are genuinely helpful. Toolcore is built for people who bounce between many small tasks and want a single place that stays consistent—without pretending we invented JSON formatting or QR codes. The table below summarizes common differences at a glance.

Comparison of Toolcore with typical standalone developer utility websites
TopicTypical tool sitesToolcore
Finding & groupingEach search can land on a different domain or layout; related tasks (e.g. format vs compare JSON) are often split across unrelated pages.One home catalog plus hubs such as JSON and Color so related utilities sit together.
Where your input runsOften unclear whether text or files are processed only in the browser, sent to a server, or passed to a third party—details may be buried or generic.Each tool explains what runs in your browser, on our servers, or with AI-assisted help, so you can decide what to paste and where (see per-page notes and execution labels).
Automation & assistantsUsually optimized for ad clicks and one-off visits; little or no shared contract for scripts, IDEs, or assistants to open a tool with prefilled input.Public tool lists such as /agent-tools.json, /mcp-tools.json (without AI-assisted entries), and documented URL query keys (q, qb, and tool-specific pairs) so the same pages can be opened with prefilled payloads when that fits your workflow.
Look & feelVisual design, density, and ad placement vary widely between sites; you re-learn a new UI on every tab.Shared layout, typography, and compact toolbars across tools so frequent switching is less jarring (specialty sites may still beat us on depth for a single niche).
Your shortcuts on the home pageRarely any way to pin specific utilities to the site's own home screen; you rely on browser bookmarks or history, which are generic and not tied to that catalog.With an optional account, you can choose a small set of catalog tools to surface as shortcuts on the home page (home tools settings)—so your usual flows stay one click away without managing a separate bookmark folder. You can also pin a few tools to expand inline on the home page (below the categories) when that tool supports it, so you can use the full workspace without opening another route.
ScopeA single page can go very deep on one format or workflow.Broad coverage in one project: many everyday utilities with room to grow—we do not aim to replace every specialized service, but to be a strong default for routine work.

We are not trying to replace every specialized service; we aim to be a dependable default when you need something solid, fast, and easy to return to.

For assistants and automation

Read the overview first: AI agents and automation. Toolcore exposes a machine-readable list of tools and URL query conventions for opening a page with prefilled text (many transforms run in the browser unless a page says otherwise). See /agent-tools.json for the manifest; /mcp-tools.json lists the same contract without AI-assisted entries. Use q / qb (Base64 UTF-8) on tools that accept a primary payload, or the per-tool keys described there (for example, JSON compare uses left / right). The manifest includes an integration block (URL manifest pattern) and a plain-English llmSystemPrompt; the same full-catalog prompt as plain text is at /llm-prompt.txt for easy copy-paste into assistant settings.

Browser pseudo-CLI and token use

The pseudo-CLI is a browser-only terminal-style UI: it navigates to catalog tools and can pass optional query prefill (e.g. -q), not a remote shell. For assistants, that matters in the same way as any other prefilled tool URL from the manifest: if the user runs the transform in the page, you can often return a short link or command instead of emitting the full formatted or encoded result in the chat. That typically reduces output length (and thus billed tokens on providers that charge by generated text) and avoids duplicating work the site already does locally. It is not unique to the CLI—a direct path?q= URL is often equally compact; the CLI is one way to express "open this tool with this input." For trivial outputs, the difference may be negligible; for large payloads or multi-step formatting, the gap is usually clearer.

Browse the full catalog (5997 tools)

The sections above are highlights, not every route. Use home Browse tools, the top-bar search (all catalog tools), or open a category hub below.

Recently added

Tools marked New in the catalog—also findable via search.

Visual explorer: Tool map (3D graph of catalog tools and related links).

How it works

The site is built for static delivery and responsive client components so pages stay fast and predictable. Pick a tool from the home catalog or the top navigation (including the "All" menu for hubs such as JSON and Color). Most items above run primarily in your browser unless a specific page says otherwise. An optional account (Google or GitHub sign-in) when this site offers sign-in; when signed in, your profile shows your name and avatar; you can also customize which tools appear on the home catalog and pin some for inline use on the home page, or send signed-in feedback (bugs and feature requests). Tool pages also include a public comments box (anonymous, with an editable display name). For site-wide notes, see the guestbook. For site policies, see Privacy and Terms of Service; reach us by email on Contact; optional support is on Tip & support.

Common use cases

  • Skim Popular starting points when you arrived from search and need the fastest path to ICCID, barcode, Z85, or JSON array tools.
  • Use What you'll find here as a curated map, then open the home catalog or Tool map when you need the full list.
  • Read For assistants when wiring automation to prefilled tool URLs instead of reimplementing transforms in chat.

Common mistakes to avoid

  • Assuming every tool is browser-only

    Check each page's execution badge—AI-assisted and some server routes send text off-device when configured.

  • Treating checksum passes as registry proof

    Identifier tools (ICCID, D-U-N-S, IMO, FIGI) validate format and math locally—they do not query live directories.

FAQ

What is Toolcore?

A searchable catalog of small online tools for developers and desk work—JSON, encoding, media, identifiers, calculators, and text utilities—with consistent layout and clear execution labels.

Where should I start from search?

Open Popular starting points above for barcode, Z85, ICCID, D-U-N-S, and JSON array remaps, or use the home page search and category tabs for everything else.

Can AI agents use these pages?

Yes. Public manifests at /agent-tools.json and /mcp-tools.json document prefilled URL keys (q, qb, and tool-specific pairs) so assistants can open the same pages people use.