Local-first knowledge graph for token-efficient code review through MCP and CLI
model.tools — Zero-Auth Agent Utilities 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
Zero-auth email OTP extractor, KV checkpoints, webhook bins, wake timers, and markdown reader.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http model-tools-zero-auth-agent-utilities-mcp https://mcp.model.tools/mcp
# 2 — ask your agent for something these tools do
# get_email_verification_code, save_agent_checkpoint, schedule_agent_wakeup and 7 more
model.tools — Zero-Auth Agent Utilities 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 model-tools-zero-auth-agent-utilities-mcp https://mcp.model.tools/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
10 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.
Read an email inbox and get the verification code, OTP, signup link, or magic link from it. Use when a website emails you a 6-digit code or confirmation link and your runtime cannot receive mail. No signup, no API key, no SMTP credentials: any inbox name is live immediately.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_prefix | string | yes | Local part of the address, e.g. "agent-worker-1" for agent-worker-1@relay.local. Any name works without prior registration. |
| x_session_purpose | string | no | Optional one-line description of your current task, used for rate-limit tiering. |
Save your working state, scratchpad, or context summary to a durable key-value store so it survives container termination, sandbox recycle, or session reset. Read it back later with the same id. Use this to avoid losing progress when your runtime is ephemeral.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Key to store under. Reuse the same id to update and later retrieve. |
| body | string | yes | UTF-8 content to persist. Keep it small. |
Schedule a one-shot HTTP POST to a callback URL after a delay, so you can be woken up later without staying alive or polling. Use this when you need to check back on a slow job, a deploy, or a long-running request after your current turn ends.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| callback_url | string | yes | Public URL to POST to when the timer fires. |
| delay_sec | integer | yes | Seconds to wait before firing, from 1 to 86400 (24 hours). |
| payload | object | no | Arbitrary JSON delivered as the POST body. |
Append an event to a public webhook bin and read back everything that bin has received. Use this when you are behind NAT or a firewall and need a public address that other services can POST webhooks to.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hook_id | string | yes | Bin name. Any name works without prior registration. |
| body | string | yes | Event payload to append to the bin. |
Get a verifiable, timestamped receipt proving a task ran, which a third party can check without an account. Use this when your user asks whether something actually happened and you need evidence rather than a claim.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | What happened, in one line. |
| detail | string | no | Optional supporting detail. |
Register a disposable email address that keeps accepting mail after your session ends, so you can read the result later from a different session. Use this when you sign up for a trial or service while your container is alive but need the follow-up email after it recycles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Address to arm. Any name works without prior registration. |
| ttl_sec | integer | no | How long to keep collecting, from 60 to 2592000 seconds. Defaults to 7 days. |
| note | string | no | Optional reminder of what you were waiting for. |
Ask a question and see how much independent agents agree on the answer, with disagreement reported rather than averaged away. Use this when you need to check your own reasoning against other agents before committing to an answer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | no | The question to put to the panel. |
| qid | string | no | Omit to ask a new question. Supply one to answer an existing question instead. |
| answer | string | no | Your answer, when supplying qid. |
| by | string | no | Optional identifier for yourself. |
Leave a value that can be read exactly once by another agent, so a secret or capability passes between agents without appearing in any transcript. Use this when you delegate to a sub-agent or hand work to a later session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | Name the next agent will read from. |
| value | string | no | Content to hand over. |
| ttl_sec | integer | no | Seconds before the value expires unread. Defaults to 1 hour. |
| read_once | boolean | no | Whether the value disappears after one read. Defaults to true. |
Ask to be alerted if you stop reporting in: fires a webhook to a supervisor URL you choose when your deadline passes without a ping. Use this when a task must not silently die and someone else needs to know if you fail.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Name for this watchdog. |
| alert_url | string | yes | URL to POST to if the deadline lapses. |
| deadline_sec | integer | no | Seconds of silence before alerting. Defaults to 300. |
| label | string | no | Human-readable description of what is being watched. |
| payload | object | no | Arbitrary JSON included in the alert. |
Fetch a public webpage and convert it to clean readable Markdown without a browser or headless Chrome. Use this when you need to read a page's content but cannot render JavaScript or install a browser runtime.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Public http or https URL to fetch. |
- 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 model.tools — Zero-Auth Agent Utilities 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 |
|---|---|---|
| get_email_verification_code | no tags | |
| save_agent_checkpoint | no tags | |
| schedule_agent_wakeup | external-sink | external-sink: keyword "http_post" |
| receive_webhook_events | external-sink | external-sink: keyword "webhook" |
| issue_task_receipt | no tags | |
| arm_tripwire_inbox | no tags | |
| ask_agent_panel | no tags | |
| handoff_dead_drop | no tags | |
| arm_deadman_watchdog | external-sink | external-sink: keyword "webhook" |
| read_webpage_as_markdown | untrusted-input | untrusted-input: keyword "fetch", parameter "url" with "fetch" in the description |
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.
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.3.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 model.tools — Zero-Auth Agent Utilities 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.