model.tools — Zero-Auth Agent Utilities
REMOTE · MCP.MODEL.TOOLS
Zero-auth email OTP extractor, KV checkpoints, webhook bins, wake timers, and markdown reader.
Available components
Last scanned (22 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1128 tokens (~112/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "handoff_dead_drop" implies "drop" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 1 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.model.tools/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.model.tools | CN=YE1,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 62ab794b9e79f39eda7f003c6d01126ac68 |
| SANs: mcp.model.tools | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.model.tools. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tools. | present | 13831 | 8 | Verified |
| model.tools. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.model.tools/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.model.tools/mcp | HTTPS enforced | 308 | https://mcp.model.tools/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
arm_deadman_watchdog ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_url | string | yes | URL to POST to if the deadline lapses. |
| deadline_sec | integer | – | Seconds of silence before alerting. Defaults to 300. |
| id | string | yes | Name for this watchdog. |
| label | string | – | Human-readable description of what is being watched. |
| payload | object | – | Arbitrary JSON included in the alert. |
No output schema declared.
No examples provided.
arm_tripwire_inbox ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Address to arm. Any name works without prior registration. |
| note | string | – | Optional reminder of what you were waiting for. |
| ttl_sec | integer | – | How long to keep collecting, from 60 to 2592000 seconds. Defaults to 7 days. |
No output schema declared.
No examples provided.
ask_agent_panel ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | – | Your answer, when supplying qid. |
| by | string | – | Optional identifier for yourself. |
| qid | string | – | Omit to ask a new question. Supply one to answer an existing question instead. |
| question | string | – | The question to put to the panel. |
No output schema declared.
No examples provided.
get_email_verification_code ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | Optional one-line description of your current task, used for rate-limit tiering. |
No output schema declared.
No examples provided.
handoff_dead_drop ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Name the next agent will read from. |
| read_once | boolean | – | Whether the value disappears after one read. Defaults to true. |
| ttl_sec | integer | – | Seconds before the value expires unread. Defaults to 1 hour. |
| value | string | – | Content to hand over. |
No output schema declared.
No examples provided.
issue_task_receipt ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Optional supporting detail. |
| subject | string | yes | What happened, in one line. |
No output schema declared.
No examples provided.
read_webpage_as_markdown ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http or https URL to fetch. |
No output schema declared.
No examples provided.
receive_webhook_events ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Event payload to append to the bin. |
| hook_id | string | yes | Bin name. Any name works without prior registration. |
No output schema declared.
No examples provided.
save_agent_checkpoint ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | UTF-8 content to persist. Keep it small. |
| id | string | yes | Key to store under. Reuse the same id to update and later retrieve. |
No output schema declared.
No examples provided.
schedule_agent_wakeup ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | Arbitrary JSON delivered as the POST body. |
No output schema declared.
No examples provided.
How do I install the model.tools — Zero-Auth Agent Utilities MCP server?
model.tools — Zero-Auth Agent Utilities is a hosted endpoint at https://mcp.model.tools/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.model.tools
claude mcp add --transport http tools-model-model-tools-mcp 'https://mcp.model.tools/mcp'
What is the model.tools — Zero-Auth Agent Utilities MCP server?
model.tools — Zero-Auth Agent Utilities is an MCP server listed in the public MCP registry as tools.model/model-tools-mcp. Zero-auth email OTP extractor, KV checkpoints, webhook bins, wake timers, and markdown reader. This page covers its hosted endpoint (https://mcp.model.tools/mcp).
Is the model.tools — Zero-Auth Agent Utilities MCP server safe to use?
model.tools — Zero-Auth Agent Utilities scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the model.tools — Zero-Auth Agent Utilities MCP server expose?
model.tools — Zero-Auth Agent Utilities exposes 10 tools: get_email_verification_code, save_agent_checkpoint, schedule_agent_wakeup, receive_webhook_events, issue_task_receipt, and 5 more. Their descriptions and schemas cost roughly 1,067 tokens of context every time the server is loaded.
Does the model.tools — Zero-Auth Agent Utilities MCP server require authentication?
No. We connected to model.tools — Zero-Auth Agent Utilities without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the model.tools — Zero-Auth Agent Utilities MCP server still maintained?
model.tools — Zero-Auth Agent Utilities is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.