Is the Vercel Slopcheck One Slopcheck MCP server down?

mcp-registry/app.vercel.slopcheck-one/slopcheck · v1.0.0

healthy
Last checked 2026-10-26 19:25 UTC · handshake 132ms

As of 2026-10-26 19:25 UTC, the Vercel Slopcheck One Slopcheck MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,889
outages (90d)
0
tools
1

Score a YouTube channel's upload pattern against YouTube's inauthentic-content policy.

Point your MCP client at this streamable-http endpoint: https://slopcheck-one.vercel.app/api/mcp

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 1 tool(s); ~177 tokens of tool definitions.
Scores higher than 36% of 15,762 MCP servers Glimind has audited.
Its tool list costs an agent ~177 tokens per session — lighter than 99% of servers.
81 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability100

What to fix (3)

1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_channel_slop_risk

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.vercel.slopcheck-one%2Fslopcheck/fixes

check_channel_slop_risk 1 change
{
  "name": "check_channel_slop_risk",
  "description": "Score a YouTube channel's recent upload pattern (title/description repetition, upload-cadence regularity, AI-disclosure language) against YouTube's inauthentic-content / mass-production demonetization policy. Reads the channel's own real public RSS feed (last 15 uploads) -- grounded in actual upload history, not a guess. Accepts a handle (e.g. '@somechannel'), a channel URL, or a bare UC... channel ID.",
  "inputSchema": {
    "type": "object",
    "required": [
      "channel"
    ],
    "properties": {
      "channel": {
        "type": "string",
        "description": "YouTube channel handle, URL, or channel ID, e.g. '@somechannel'"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.vercel.slopcheck-one/slopcheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.vercel.slopcheck-one/slopcheck"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.slopcheck-one%2Fslopcheck.svg)](https://glimind.com/server/mcp-registry%2Fapp.vercel.slopcheck-one%2Fslopcheck?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fapp.vercel.slopcheck-one%2Fslopcheck?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.slopcheck-one%2Fslopcheck.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.slopcheck-one%2Fslopcheck.svg
   :target: https://glimind.com/server/mcp-registry%2Fapp.vercel.slopcheck-one%2Fslopcheck?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f70e21f09f26d63b…, first seen 2026-10-17, included at leaf 15148 of 75,005. Version history · verify what your client received.

Tools (1)

Compare: most reliable media servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Vercel Slopcheck One Slopcheck MCP server down right now?

As of 2026-10-26 19:25 UTC, the Vercel Slopcheck One Slopcheck MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Vercel Slopcheck One Slopcheck MCP server provide?

Vercel Slopcheck One Slopcheck MCP server advertises 1 tool, including check_channel_slop_risk.

How do I install Vercel Slopcheck One Slopcheck MCP server?

Point your MCP client at this streamable-http endpoint: https://slopcheck-one.vercel.app/api/mcp

Is the Vercel Slopcheck One Slopcheck MCP server safe to connect to an AI agent?

Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Vercel Slopcheck One Slopcheck MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve