Search, save and rate AI tools people shared in chats. Local catalogue, any model or none.
Toolbox is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Small tools for agent builders: AI-writing tells, tools/list token cost, CLAUDE.md lint, and more.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http allthepossibles-toolbox-mcp https://toolbox.allthepossibles.com/mcp
# 2 — ask your agent for something these tools do
# check_tells, manifest_cost, lint_agent_md and 10 more
Toolbox costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http allthepossibles-toolbox-mcp https://toolbox.allthepossibles.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take Authorization header (Optional. Bearer tb_... for Pro; every tool works free with daily caps. Install steps per client: https://toolbox.allthepossibles.com/docs#install) if you want to set it.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Check text for AI-writing tells (em-dashes, 'not just X but Y', rule-of-three lists, stock vocabulary like delve or seamlessly, hedge words, smart quotes, hidden Unicode) and return a score, each tell with its position, and a cleaned copy. Run it on anything you are about to publish on a human's behalf.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The text to check. Free tier: 3,000 chars. |
Estimate what an MCP server's tools/list costs in tokens on every session start, per tool, with the three most expensive tools and flags for oversized descriptions, base64 blobs and echoed schemas. Pass a live Streamable HTTP endpoint or a tools array.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | Streamable HTTP MCP endpoint |
| tools | array | no | Tool definitions, if the server is not reachable over HTTP |
Lint a CLAUDE.md, AGENTS.md or MEMORY.md: line count against Claude Code's 200-line memory index cap, estimated tokens, duplicate lines, contradicting rules, leftover TODO markers, hidden characters, empty headings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | File contents |
| filename | string | no | e.g. CLAUDE.md or MEMORY.md; changes the severity of the line cap |
Generate install snippets for an MCP endpoint (Claude Code, Claude Desktop, Cursor, Codex, VS Code, curl) and probe the endpoint once to confirm it answers initialize and tools/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | — |
| name | string | no | Server name to use in configs |
| headerName | string | no | — |
| headerValue | string | no | — |
| probe | boolean | no | — |
Read a site's robots.txt and report which AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Bytespider and more) are allowed, blocked or partially blocked; check for llms.txt and draft one from the site's metadata and sitemap.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Any URL on the site |
Fetch a URL once and grade its response headers: HSTS, Content-Security-Policy, X-Content-Type-Options, frame control, Referrer-Policy, Permissions-Policy, Cache-Control, cookie Secure/HttpOnly/SameSite flags, and server version leaks. Returns a grade, a score and the exact header to add for each gap.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page to fetch |
Fetch a URL and report what crawlers and link unfurlers see: title and meta description with lengths, canonical, lang, viewport, robots meta, h1s, Open Graph and Twitter card tags, favicon, JSON-LD types, the resulting preview card, and findings for anything missing or too long.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page to fetch |
Turn a JSON sample (or an array of samples of the same shape) into a JSON Schema draft 2020-12 and a TypeScript type. Infers required vs optional keys across samples, nullable fields, integer vs number, date/email/uri/uuid formats, and small enums. Use it to draft an MCP tool inputSchema from an example payload.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| json | string | yes | The JSON text. Free tier: 20,000 chars. |
| name | string | no | Type name, default Root |
Explain a five-field cron expression in plain English, list the next runs in UTC, and warn about the cases Cloudflare Workers, GitHub Actions and crontab handle differently (nicknames, six fields, day-of-month plus day-of-week, sub-5-minute intervals, day 31).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| expression | string | yes | e.g. 0 */6 * * 1-5 |
| count | integer | no | How many next runs to list, 1 to 20, default 5 |
| from | string | no | ISO date to compute next runs from, default now |
Scrub a .env file into a safe .env.example: every value is blanked or replaced with a placeholder that keeps its shape (postgres://USER:PASSWORD@HOST/DB). Returns the example, the secrets found (AWS, GitHub, Stripe, Slack, Google, OpenAI, Anthropic, Resend, SendGrid, Twilio, Cloudflare, JWTs, private keys, database URLs, high-entropy strings) by key, kind and line with only the first 4 characters
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The .env file contents. Free tier: 20,000 chars. |
Trace a URL's redirect chain hop by hop (up to 10 hops, 8 s each) with status, location, timing and scheme per hop. Flags chains over two redirects, loops, HTTPS-to-HTTP downgrades, 302s used for www or https canonicalisation, dropped paths or query strings, cross-domain moves, meta-refresh or JS redirects on a 200, and a final page that is not 200.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | URL to trace, e.g. http://example.com |
Check a site's sitemaps: discovers them from robots.txt, /sitemap.xml and /sitemap_index.xml, reads index files one level deep (20 children max), counts URLs per file and per host, summarises lastmod, and fetches a sample of URLs (HEAD, then GET) to count the ones that are not 200. Flags a missing sitemap, no robots.txt entry, over 50,000 URLs, other hosts, http URLs on https sites and missing las
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Any URL on the site |
| sample | integer | no | How many sitemap URLs to fetch, default 10, max 25 on free and 100 on Pro |
Decode a JWT's header and payload without verifying the signature (it never takes a secret). Returns the claims with iat, nbf and exp as ISO times, a plain-text expiresIn, issuer, subject and audience, and findings: alg none, HS* with a URL-like kid, missing or distant exp, expired, nbf or iat in the future, payload over 4 KB, sensitive field names, and jku or x5u pointing off-site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The JWT, three dot-separated parts. A leading Bearer is ignored. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Toolbox or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_tells | no tags | |
| manifest_cost | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lint_agent_md | no tags | |
| mcp_install_snippets | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_ai_crawlers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_headers | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| check_page_meta | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| json_to_schema | no tags | |
| explain_cron | no tags | |
| scrub_env | no tags | |
| trace_redirects | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_sitemap | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| decode_jwt | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Toolbox can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.