agent-site-audit - website audits for agents
REMOTE · AGENT.AUDITO.LAT
Paid website audits for agents: flat JSON, HTML report, deep audit. USDC via x402.
Available components
Last scanned (22 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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 Security63
- 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 4 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 528 tokens (~132/item across 4 items; 4 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 Management13
- Stability observed for 4 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 65
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 18 Oct 2026 · Probed https://agent.audito.lat/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agent.audito.lat | CN=YE2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e6c0093f5195898559f04a2b210743d9a5 |
| SANs: agent.audito.lat, audito.lat, panel.audito.lat, status.audito.lat | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 agent.audito.lat. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| lat. | present | 25789, 42520 | 8, 8 | Verified |
| audito.lat. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; img-src 'self' data:; style-src 'self'; script-src 'self'; connect-src 'self'; font-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent.audito.lat/mcp | Verified | 200 | |
| http (plaintext) | http://agent.audito.lat/mcp | HTTPS enforced | 301 | https://agent.audito.lat/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 →
audit_site ~168
PAID (0.25 USDC on Base via x402). Full deterministic website audit as flat JSON: HTTP status, latency, server, title, content fingerprint, robots policy, redirect chain, sitemap, viewport meta, JSON-LD, the full issue list and a 0-100 agent-readiness score. If you call it without a payment you get back the x402 challenge (price, payTo, network) so you can sign an EIP-3009 USDC authorization and retry passing it in the "payment" argument.
| Name | Type | Req | Description |
|---|---|---|---|
| payment | string | – | Optional base64 x402 payment payload (the value for the X-Payment header). Omit it on the first call to receive the payment challenge. |
| url | string | yes | Absolute http(s) URL to audit |
No output schema declared.
No examples provided.
deep_audit ~163
PAID (0.25 USDC on Base via x402). Technical deep audit as JSON: TLS certificate (issuer, expiry, SAN, protocol), the seven security headers, cookie flags, DNS and email security (SPF, DMARC, DKIM, CAA, MX), compression and caching, and AI-agent readiness (robots.txt, llms.txt, security.txt, blocked AI crawlers). Every finding is ranked critical/high/medium/low with a copy-paste fix, plus a prioritised remediation plan. Also returns report_url with a human-readable HTML report.
| Name | Type | Req | Description |
|---|---|---|---|
| payment | string | – | Optional base64 x402 payment payload (the value for the X-Payment header). |
| url | string | yes | Absolute http(s) URL to audit |
No output schema declared.
No examples provided.
scan_site ~67
Free preview of a website audit: 3 of 9 checks (HTTP status, robots policy, latency, agent-readiness score). Use it to see the shape of the result before paying. Returns JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the site to scan |
No output schema declared.
No examples provided.
service_info ~52
Free. Describes this paid website-audit service: the three products, their prices, and exactly how to pay with x402 (USDC on Base). Call this first if you do not know how to pay.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the agent-site-audit - website audits for agents MCP server?
agent-site-audit - website audits for agents is a hosted endpoint at https://agent.audito.lat/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 · agent.audito.lat
claude mcp add --transport http lat-audito-agent-site-audit 'https://agent.audito.lat/mcp'
What is the agent-site-audit - website audits for agents MCP server?
agent-site-audit - website audits for agents is an MCP server listed in the public MCP registry as lat.audito/agent-site-audit. Paid website audits for agents: flat JSON, HTML report, deep audit. USDC via x402. This page covers its hosted endpoint (https://agent.audito.lat/mcp).
Is the agent-site-audit - website audits for agents MCP server safe to use?
agent-site-audit - website audits for agents scores 67 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-site-audit - website audits for agents MCP server expose?
agent-site-audit - website audits for agents exposes 4 tools: service_info, scan_site, audit_site, deep_audit. Their descriptions and schemas cost roughly 450 tokens of context every time the server is loaded.
Does the agent-site-audit - website audits for agents MCP server require authentication?
No. We connected to agent-site-audit - website audits for agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the agent-site-audit - website audits for agents MCP server still maintained?
agent-site-audit - website audits for agents is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.