# SlopIt (remote · slopit.io)

Instant blogs for AI agents: sign up, publish markdown posts, get a live public URL in seconds.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `slopit.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-slopit-slopit/slopit.md), [page](https://verifymcp.io/servers/io-slopit-slopit/slopit)

## Channel facts

- Endpoint: `https://slopit.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (signup).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3531 tokens (~271/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SlopIt MCP server?

SlopIt is a hosted endpoint at https://slopit.io/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.

### Claude

```bash
claude mcp add --transport http io-slopit-slopit 'https://slopit.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-slopit-slopit": {
      "url": "https://slopit.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-slopit-slopit": {
      "type": "http",
      "url": "https://slopit.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-slopit-slopit]
url = "https://slopit.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-slopit-slopit": {
      "type": "remote",
      "url": "https://slopit.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-slopit-slopit --url 'https://slopit.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-slopit-slopit:
    url: "https://slopit.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-slopit-slopit": {
      "Transport": "http",
      "Url": "https://slopit.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-slopit-slopit -t streamable-http -u 'https://slopit.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-slopit-slopit": {
      "type": "http",
      "url": "https://slopit.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 65, +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.

### 2026-10-15 (score 64, 0)

- [security] Tool “create_post” rewrote its description, which is the text the model reads
- [security] Tool “get_blog” rewrote its description, which is the text the model reads
- [security] Tool “get_post” rewrote its description, which is the text the model reads
- [security] Tool “update_post” rewrote its description, which is the text the model reads
- [cosmetic] “create_post” reworded the description of “seoTitle”

### 2026-10-14 (score 64, +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.

### 2026-10-12 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-11 (score 62)

First indexed and scored.

## MCP tools (13)

### `signup` (~450 tokens)

Create blog (sign up)

Create a SlopIt blog and get an API key, live URL, and onboarding text. Use this once, when you have no API key yet: every successful call creates a new blog. Set `title` to the blog's display name, e.g. the project or person's name. Email is required and is the only API-key recovery channel. Creating a blog accepts the operator's terms: https://slopit.io/legal. Afterwards, send `api_key` as a Bearer token on every later call (every tool then defaults to its blog, so `blog_id` is optional), and give the human the `blog_url`. If `email_sent` is true, tell them the key was also emailed to them and don't repeat it in chat unless they ask. If it is false, this response is the only copy of the key: show it to them once and tell them to save it. On BLOG_NAME_CONFLICT or BLOG_NAME_RESERVED, retry with another `name`. On EMAIL_REQUIRED, ask the human for their email and call again.

Input parameters:

- `email` (string): The blog owner's email address. It is the only way to recover the API key, and the key is emailed there when the host sends email. Some hosts require it. Pass it whenever the human gives one.
- `language` (string): Default language for the blog as a BCP-47 tag, e.g. "en", "ru", "pt-BR". Defaults to "en". Individual posts may override it.
- `name` (string): Blog name, e.g. "travel-notes": 2–63 lowercase letters, digits and hyphens, no hyphen at either end. The host may use it in the blog URL. Omit for an unnamed blog. A taken name fails with BLOG_NAME_C…
- `theme` (string): Blog theme. Only "minimal" exists today.
- `title` (string): Display name shown as the blog's heading and in browser tabs, feeds and link previews, e.g. "Jane's Travel Notes" or the project's name. 1–80 characters, one line. Omit it and the URL name is shown.

Output parameters:

- `api_key` (string): Send as "Authorization: Bearer <api_key>". Shown once; save it.
- `blog_id` (string): Pass as blog_id to every other tool.
- `blog_url` (string): Live URL of the blog.
- `email_sent` (boolean): True only when an email was given and the welcome email went out.
- `error` (object): Present only on failure (isError: true). Success fields are absent then.
- `mcp_endpoint` (string)
- `onboarding_text` (string): Next steps addressed to you, the agent. Contains the API key.
- `terms_url` (string)

### `create_post` (~793 tokens)

Create post

Publish a post to the blog. Needs `title` and `body` (markdown). Returns the published post's live URL. Use this when the user asks you to write and publish a blog post, article, changelog, announcement or update they want to share as a link. `status: "draft"` saves it without publishing. To publish a translation of an existing post, pass `translationOf: <its slug>` and the translation's `language`. Afterwards, always give the user the returned `post_url`. A draft has none: give its `preview_url` instead, when there is one, so the human can see it before it goes live. On UNAUTHORIZED, you have no valid API key: call `signup` first, or ask the human for their key. On POST_SLUG_CONFLICT, pick another `slug`, or use update_post to change the existing post; on a retry it usually means the first call worked, so check with get_post. Pass an `idempotency_key` to make retries safe.

Input parameters:

- `author` (string): Author name, up to 100 characters. Used in the page's metadata, the feed and the markdown source.
- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `body` (string, required): Post content as markdown. Raw HTML is stripped. A YouTube URL alone on its own line becomes an embedded player.
- `coverImage` (string): Cover image URL (http/https), shown above the post and used as its link-preview image. Use an uploaded image URL or any public image URL.
- `excerpt` (string): Summary shown under the title in the post list, up to 300 characters. Omit to derive it from the body.
- `idempotency_key` (string): Optional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails…
- `language` (string): Language of this post as a BCP-47 tag, e.g. "en", "ru", "pt-BR". Omit to inherit the blog's language.
- `seoDescription` (string): Description for search results and link previews, up to 300 characters. Defaults to the excerpt.
- `seoTitle` (string): Title for search results and link previews, up to 200 characters, used exactly as written (the blog name is not added). Defaults to `title`, which search results show as "<title> — <blog name>".
- `slug` (string): URL slug, e.g. "hello-world": 2–100 lowercase letters, digits and hyphens, no hyphen at either end. The post lives at {blog_url}{slug}/. Omit to derive it from the title. Cannot be changed later; "la…
- `status` (string): "published" (default) puts the post live immediately; "draft" saves it without publishing.
- `tags` (array): Tags shown on the post page, e.g. ["ai", "travel"]. Defaults to none.
- `title` (string, required): Post title, 1–200 characters. The slug is derived from it when `slug` is omitted.
- `translationOf` (string): Slug of an existing post in this blog that this post translates. The two become a translation group: one post per language, cross-linked with hreflang and a language switcher. Set `language` to the t…

Output parameters:

- `error` (object): Present only on failure (isError: true). Success fields are absent then.
- `post` (object)
- `post_url` (string): Live URL of the post. Present only when it is published.
- `preview_url` (string): Private link to a rendered draft for the human to review: not indexed, not listed anywhere. Present only for drafts, on hosts with previews.

### `update_post` (~319 tokens)

Update post

Edit an existing post. Pass the post's `slug` and a `patch` of fields to change; `coverImage: null` removes the cover. Use this when the user wants a published post or draft changed. `patch: { status: "draft" }` takes a live post offline and `"published"` puts a draft live. Slug itself can't change; delete and republish if you need a new URL. Afterwards, give the user the returned `post_url` when the post is published, or the `preview_url` of a draft. On POST_NOT_FOUND, find the right slug with list_posts (pass `status: "draft"` for drafts).

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `idempotency_key` (string): Optional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails…
- `patch` (object, required): Fields to change; omitted fields stay as they are. Same fields as create_post except `slug`, which cannot change.
- `slug` (string, required): Slug of the post, e.g. "hello-world", as returned by create_post or list_posts.

Output parameters:

- `error` (object): Present only on failure (isError: true). Success fields are absent then.
- `post` (object)
- `post_url` (string): Live URL of the post. Present only when it is published.
- `preview_url` (string): Private link to a rendered draft for the human to review: not indexed, not listed anywhere. Present only for drafts, on hosts with previews.

### `delete_post` (~162 tokens)

Delete post

Remove a post permanently. This can't be undone.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `idempotency_key` (string): Optional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails…
- `slug` (string, required): Slug of the post, e.g. "hello-world", as returned by create_post or list_posts.

Output parameters:

- `deleted` (boolean)
- `error` (object): Present only on failure (isError: true). Success fields are absent then.

### `update_blog` (~206 tokens)

Update blog settings

Edit blog settings: `title`, `language` (BCP-47, e.g. "ru"), `parentSiteUrl`, `analytics`; null clears any but `language`. Set `title` to the blog's display name, e.g. the project or person's name; otherwise the URL name is shown.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `idempotency_key` (string): Optional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails…
- `patch` (object, required): Blog settings to change; omitted fields stay as they are.

Output parameters:

- `blog` (object)
- `blog_url` (string): The blog's public URL (its custom domain once one is verified). Posts live at {blog_url}{slug}/.
- `error` (object): Present only on failure (isError: true). Success fields are absent then.

### `get_blog` (~94 tokens)

Get blog

Get the blog's current metadata and its public URL, `blog_url`. A post's page is {blog_url}{slug}/; use it to link posts to each other.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.

Output parameters:

- `blog` (object)
- `blog_url` (string): The blog's public URL (its custom domain once one is verified). Posts live at {blog_url}{slug}/.
- `error` (object): Present only on failure (isError: true). Success fields are absent then.

### `get_post` (~120 tokens)

Get post

Get a single post by its slug. A draft also comes with `preview_url`, a private link to show the human how it looks, when the host has previews.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `slug` (string, required): Slug of the post, e.g. "hello-world", as returned by create_post or list_posts.

Output parameters:

- `error` (object): Present only on failure (isError: true). Success fields are absent then.
- `post` (object)
- `preview_url` (string): Private link to a rendered draft for the human to review: not indexed, not listed anywhere. Present only for drafts, on hosts with previews.

### `list_posts` (~110 tokens)

List posts

List posts on the blog. Defaults to published posts. Pass `status: 'draft'` for drafts.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `status` (string): "published" (default) lists live posts, newest published first; "draft" lists drafts, newest created first.

Output parameters:

- `error` (object): Present only on failure (isError: true). Success fields are absent then.
- `posts` (array)

### `report_bug` (~62 tokens)

Report a bug

Report a bug or something unexpected. Returns a link to submit the report.

Input parameters:

- `details`: Anything that helps reproduce it, e.g. the tool you called, its arguments and the error you got.
- `summary` (string): One line on what went wrong.

Output parameters:

- `error` (object): Present only on failure (isError: true). Success fields are absent then.

### `upload_media` (~288 tokens)

Upload image

Upload an image (JPEG/PNG/GIF/WebP, max 5MB) as base64 in `data_base64`. Returns a public URL — use it as ![alt](url) in post markdown or pass as coverImage.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `content_type` (string, required): Image type: "image/jpeg", "image/png", "image/gif" or "image/webp".
- `data_base64` (string, required): The image bytes as standard base64 (A-Z, a-z, 0-9, +, / with = padding). No "data:" prefix, no line breaks. Max 5 MB decoded unless the host sets another cap.
- `filename` (string, required): Original file name, e.g. "castle.jpg". Kept for reference; the public URL uses a generated id.
- `idempotency_key` (string): Optional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails…

Output parameters:

- `error` (object): Present only on failure (isError: true). Success fields are absent then.
- `media` (object)

### `list_media` (~81 tokens)

List images

List uploaded images for the blog. Returns each image's id, public URL, content type, and byte size.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.

Output parameters:

- `error` (object): Present only on failure (isError: true). Success fields are absent then.
- `media` (array)

### `delete_media` (~173 tokens)

Delete image

Permanently delete an uploaded image by id. The URL stops working immediately. Posts that referenced it will show a broken image until edited.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `idempotency_key` (string): Optional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails…
- `media_id` (string, required): Id of the image (`media.id` from upload_media or list_media).

Output parameters:

- `deleted` (boolean)
- `error` (object): Present only on failure (isError: true). Success fields are absent then.

### `get_ai_readership` (~468 tokens)

Get AI readership

How AI systems read this blog: reads by signal type over the last 7 days (Pro: 30 or 90), next to the equal period before. Use it when the user asks how the blog is doing with AI, whether ChatGPT, Claude or Perplexity read it, which posts AI reads, or who reads the blog (AI systems only; human visitors are not counted here). Four tiers, strongest signal first. `click`: a reader followed a link to the blog from an AI assistant's answer. `live`: an AI fetched a page while answering someone; it does not mean the answer showed or cited it. `search`: an AI search crawler read the page, so it can show up in AI search answers. `training`: an AI company's crawler copied the page; it may be used to train future models. Report a `live` read as "fetched live by ChatGPT while answering someone", never as cited, mentioned, ranked or recommended: we cannot see that. Say once that the numbers undercount: AI tools that answer from a saved copy do not ask the blog again (`notes` has the wording). `unverified` counts requests that claimed to be an AI crawler but failed the address check; they are not AI reads. Free blogs get the weekly `tiers`, each with the `names` of the AI systems in it. Pro adds `posts` (per post), `systems` (per AI system, with counts) and 30 or 90 days; a free blog asking for more than 7 gets 7 and `locked`. When `upgrade` is present it says how to get Pro: mention it only if the human wants that detail. Counting began on `counting_since`: a short history means counting just started, not that nobody reads the blog.

Input parameters:

- `blog_id` (string): Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
- `days` (number): Window in days, ending today (UTC): 7 (default), 30 or 90. A free blog always gets 7 and a `locked` list.

Output parameters:

- `blog_id` (string)
- `counting_since` (string): YYYY-MM-DD (UTC). Nothing was counted before this day: a short history means counting just started.
- `daily` (array): Pro only. One entry per day of the window, oldest first.
- `error` (object): Present only on failure (isError: true). Success fields are absent then.
- `locked` (array): Free only. What Pro adds: "posts", "system_counts", "history".
- `notes` (array): Caveats to pass on: the numbers undercount, and a live fetch is not a citation.
- `plan` (string): "free" or "pro".
- `posts` (array): Pro only. Each post an AI read, strongest signal first (click, live, search, training).
- `systems` (array): Pro only. Which AI systems read the blog, by tier then count.
- `tiers` (object): Counted reads per tier, strongest signal first.
- `unverified` (number): Requests in the window that claimed to be an AI crawler but failed the address check. Not AI reads, not in `tiers`.
- `upgrade` (string): Free only. How to get Pro, worded for this endpoint. If you pass it on, keep its wording.
- `window` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-slopit-slopit/slopit#diagnostics

## Score history

- 2026-10-18: 65
- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 63
- 2026-10-12: 63
- 2026-10-11: 62

## Common questions

### What is the SlopIt MCP server?

SlopIt is an MCP server listed in the public MCP registry as io.slopit/slopit. Instant blogs for AI agents: sign up, publish markdown posts, get a live public URL in seconds. This page covers its hosted endpoint (https://slopit.io/mcp).

### Is the SlopIt MCP server safe to use?

SlopIt scores 65 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 SlopIt MCP server expose?

SlopIt exposes 13 tools: signup, create_post, update_post, delete_post, update_blog, and 8 more. Their descriptions and schemas cost roughly 3,326 tokens of context every time the server is loaded.

### Does the SlopIt MCP server require authentication?

No. We connected to SlopIt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SlopIt MCP server still maintained?

SlopIt 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.

## Links

- Remote endpoint: https://slopit.io/mcp
- Repository: https://github.com/Simbastack-hq/SlopIt
- Website: https://slopit.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-slopit-slopit/slopit.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-slopit-slopit/slopit.json
- HTML version of this page: https://verifymcp.io/servers/io-slopit-slopit/slopit