com.edgethirteen.www/slopcheck
REMOTE · WWW.EDGETHIRTEEN.COM · SCANNED SEP 20
Check a YouTube channel's recent uploads against YouTube's 2026 inauthentic-content policy.
Available components
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 156 tokens (~156/item across 1 items; 1 tools + 0 resources), lean.Pass
- 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.edgethirteen.www/slopcheck MCP server?
com.edgethirteen.www/slopcheck is a hosted endpoint at https://www.edgethirteen.com/api/mcp/slopcheck, 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 · www.edgethirteen.com
claude mcp add --transport http com-edgethirteen-www-slopcheck 'https://www.edgethirteen.com/api/mcp/slopcheck'
{
"mcpServers": {
"com-edgethirteen-www-slopcheck": {
"url": "https://www.edgethirteen.com/api/mcp/slopcheck"
}
}
} {
"servers": {
"com-edgethirteen-www-slopcheck": {
"type": "http",
"url": "https://www.edgethirteen.com/api/mcp/slopcheck"
}
}
} [mcp_servers.com-edgethirteen-www-slopcheck] url = "https://www.edgethirteen.com/api/mcp/slopcheck"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-edgethirteen-www-slopcheck": {
"type": "remote",
"url": "https://www.edgethirteen.com/api/mcp/slopcheck",
"enabled": true
}
}
} openclaw mcp add com-edgethirteen-www-slopcheck --url 'https://www.edgethirteen.com/api/mcp/slopcheck' --transport streamable-http
mcp_servers:
com-edgethirteen-www-slopcheck:
url: "https://www.edgethirteen.com/api/mcp/slopcheck" {
"McpServers": {
"com-edgethirteen-www-slopcheck": {
"Transport": "http",
"Url": "https://www.edgethirteen.com/api/mcp/slopcheck"
}
}
} assistant mcp add com-edgethirteen-www-slopcheck -t streamable-http -u 'https://www.edgethirteen.com/api/mcp/slopcheck'
{
"mcpServers": {
"com-edgethirteen-www-slopcheck": {
"type": "http",
"url": "https://www.edgethirteen.com/api/mcp/slopcheck"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +3
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-03-26 → 2025-11-25 functional
- 17 Sept 26 +7
- Authorization: unverified → partial ▲ security
- 15 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Sept 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 20 Sept 2026 · Probed https://www.edgethirteen.com/api/mcp/slopcheck
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.edgethirteen.com | CN=YR1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 6839f6f39d66a38fe8deece9986a25a4546 |
| SANs: www.edgethirteen.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.edgethirteen.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| edgethirteen.com. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.edgethirteen.com/api/mcp/slopcheck | Verified | 200 | |
| http (plaintext) | http://www.edgethirteen.com/api/mcp/slopcheck | HTTPS enforced | 308 | https://www.edgethirteen.com/api/mcp/slopcheck |
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 →
check_youtube_channel_slop_risk ~156
Check a YouTube channel's recent uploads against YouTube's 2026 inauthentic-content ('AI slop') policy: title/description repetition, upload-cadence regularity, and AI-disclosure language. Returns an overall risk band (low/medium/high), a numeric score, and the single most severe flag found. This is a heuristic proxy for YouTube's own review process, not a simulation of it. The full flag-by-flag report with exact numbers and suggested fixes is a separate paid product at https://www.edgethirteen.com/tools/slopcheck.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | YouTube channel handle (e.g. @somechannel), URL, or channel ID |
No output schema declared.
No examples provided.
What is the com.edgethirteen.www/slopcheck MCP server?
com.edgethirteen.www/slopcheck is an MCP server listed in the public MCP registry as com.edgethirteen.www/slopcheck. Check a YouTube channel's recent uploads against YouTube's 2026 inauthentic-content policy. This page covers its hosted endpoint (https://www.edgethirteen.com/api/mcp/slopcheck).
Is the com.edgethirteen.www/slopcheck MCP server safe to use?
com.edgethirteen.www/slopcheck scores 77 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 com.edgethirteen.www/slopcheck MCP server expose?
com.edgethirteen.www/slopcheck exposes 1 tool: check_youtube_channel_slop_risk. Their descriptions and schemas cost roughly 156 tokens of context every time the server is loaded.
Does the com.edgethirteen.www/slopcheck MCP server require authentication?
No. We connected to com.edgethirteen.www/slopcheck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.edgethirteen.www/slopcheck MCP server still maintained?
com.edgethirteen.www/slopcheck is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.