Agent Traffic Lab
REMOTE · MCP.AGENTTRAFFICLAB.COM
Execute supported agent tasks through verified providers with fallback and durable outcomes.
Available components
Last scanned (16 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 351 tokens (~351/item across 1 items; 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 +10
- Stability: fail → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Oct 26 +4
No change was recorded against any check on this day. Stability & Change Management went from 0 to 25.
- 15 Oct 26 0
- Tool “atl_complete_task” rewrote its description, which is the text the model reads security
- Schema quality: 304 → 351 ▼ functional
- Destructive annotations: pass → 100 functional
- 10 Oct 26 0
- Stability: pass → fail ▼ security
- Tool “atl_complete_task” rewrote its description, which is the text the model reads security
- Schema quality: 1108 → 304 ▲ functional
- Tool coverage: 25% → 100% ▲ functional
- Destructive annotations: 100 → pass functional
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 21 Nov 2026 · Probed https://mcp.agenttrafficlab.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.agenttrafficlab.com | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4fc7ffdafbf5dec0e5e15c1fa431b85 |
| SANs: mcp.agenttrafficlab.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.agenttrafficlab.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| agenttrafficlab.com. | No DS | 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.agenttrafficlab.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.agenttrafficlab.com/mcp | HTTPS enforced | 301 | https://mcp.agenttrafficlab.com/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 →
atl_complete_task ~274
Execute a user-authorized external search, public web/content extraction, summary, translation, or classification task. ATL selects an eligible verified provider or tool, performs the supported task where supply is available, may use bounded fallback on eligible failures, validates the result, and records execution Outcome. Routine use: this operation is suited to user-authorized external information tasks that need a completed result rather than routing evidence, even if no prior provider has failed. Rescue use: it can retry the original authorized task when a prior provider fails, times out, is rate-limited, is unavailable, or returns an invalid result. For routing evidence without execution, use the separate atl_decide tool. Do not duplicate work already completed, override a user-specified provider or tool, or infer authorization for private inputs. The task must be user-authorized; do not submit private or local-only information without permission. Supported capabilities and provider availability are limited, so completion is not guaranteed. No ATL API key is required for the public first-use path.
| Name | Type | Req | Description |
|---|---|---|---|
| required_capability | string | – | Optional capability hint. Omit unless the caller already knows the required capability; ATL normally derives a structured TaskSpec from the task. |
| task | string | yes | The natural-language task to complete. Include the goal and any relevant input, constraints, or desired output. |
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | The supported capability selected or inferred for the task; empty if unavailable. |
| decision | object|null | yes | ATL Decision evidence retained for advanced/debug consumers. |
| discovery_resume_status | string | – | Outcome of the same-call discovery resume attempt when used. |
| discovery_resume_used | boolean | – | True when ATL synchronously ran bounded discovery/promotion and retried the same task. |
| execution | object|null | yes | ATL execution evidence retained for advanced/debug consumers; null when execution did not start. |
| execution_status | string | yes | Provider execution status; EXECUTED alone does not imply task correctness. |
| fallback_used | boolean | yes | Whether bounded fallback/failover was used during execution. |
| ok | boolean | yes | True only when execution succeeded and ATL's task-level result verifier accepted the result. |
| result | string | yes | The provider's task result. When ok=false, inspect result_validation before trusting it. |
| result_validation | object|null | yes | ATL task-level correctness checks. passed must be true before the result is treated as product success. |
| stage | string | yes | The furthest ATL product stage reached for this call. |
No examples provided.
How do I install the Agent Traffic Lab MCP server?
Agent Traffic Lab is a hosted endpoint at https://mcp.agenttrafficlab.com/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.agenttrafficlab.com
claude mcp add --transport http com-agenttrafficlab-atl 'https://mcp.agenttrafficlab.com/mcp'
What is the Agent Traffic Lab MCP server?
Agent Traffic Lab is an MCP server listed in the public MCP registry as com.agenttrafficlab/atl. Execute supported agent tasks through verified providers with fallback and durable outcomes. This page covers its hosted endpoint (https://mcp.agenttrafficlab.com/mcp).
Is the Agent Traffic Lab MCP server safe to use?
Agent Traffic Lab scores 84 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 Agent Traffic Lab MCP server expose?
Agent Traffic Lab exposes 1 tool: atl_complete_task. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.
Does the Agent Traffic Lab MCP server require authentication?
No. We connected to Agent Traffic Lab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Traffic Lab MCP server still maintained?
Agent Traffic Lab is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Agent Traffic Lab MCP server?
VerifyMCP ran 13 checks on Agent Traffic Lab, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.