SlopIt

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "SlopIt": {
      "url": "https://slopit.io/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (16)

• signup destructive

  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.

  Parameters:

  • 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_CONFLICT.
  • 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.
  • 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.
  • 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.
  • parentSiteUrl — string — The main website this blog belongs to (http/https), e.g. "https://acme.example". Every page links back to it ("Main site →"), which tells readers and search engines the blog and the site are one thing. Set it whenever the blog is for a product, project or business with its own site. Change or clear it later with update_blog.

  Hints: read-only no · destructive yes · idempotent no · open-world yes

• create_post destructive

  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.

  Parameters:

  • title (required) — string — Post title, 1–200 characters. The slug is derived from it when `slug` is omitted.
  • body (required) — string — Post content as markdown. Raw HTML is stripped. A YouTube URL alone on its own line becomes an embedded player. {{fact:name}} shows the current value of the blog's live fact `name` (see set_fact).
  • 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; "lang" is reserved.
  • tags — array — Tags shown on the post page, e.g. ["ai", "travel"]. Defaults to none.
  • author — string — Author name, up to 100 characters. Used in the page's metadata, the feed and the markdown source.
  • status — string — "published" (default) puts the post live immediately; "draft" saves it without publishing.
  • 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.
  • excerpt — string — Summary shown under the title in the post list, up to 300 characters. Omit to derive it from the body.
  • language — string — Language of this post as a BCP-47 tag, e.g. "en", "ru", "pt-BR". Omit to inherit the blog's language.
  • 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>".
  • 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.
  • 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 translation's language; it must differ from every other member's.
  • seoDescription — string — Description for search results and link previews, up to 300 characters. Defaults to the excerpt.
  • 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 with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

  Hints: read-only no · destructive yes · idempotent no · open-world yes

• update_post destructive

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

  Parameters:

  • slug (required) — string — Slug of the post, e.g. "hello-world", as returned by create_post or list_posts.
  • patch (required) — object — Fields to change; omitted fields stay as they are. Same fields as create_post except `slug`, which cannot change.
  • 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 with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• delete_post destructive

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

  Parameters:

  • slug (required) — string — Slug of the post, e.g. "hello-world", as returned by create_post or list_posts.
  • 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 with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• update_blog destructive

  Edit blog settings: `title` (otherwise the URL name is shown), `language` (BCP-47), `parentSiteUrl`, `analytics`, and brand `accentColor`, `logoUrl`, `faviconUrl` to match a main site. null clears any but `language`.

  Parameters:

  • patch (required) — object — Blog settings to change; omitted fields stay as they are.
  • 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 with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• get_blog read-only

  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.

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_post read-only

  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.

  Parameters:

  • slug (required) — string — Slug of the post, e.g. "hello-world", as returned by create_post or list_posts.
  • 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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_posts read-only

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

  Parameters:

  • status — string — "published" (default) lists live posts, newest published first; "draft" lists drafts, newest created first.
  • 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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• report_bug read-only

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

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• upload_media

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

  Parameters:

  • filename (required) — string — Original file name, e.g. "castle.jpg". Kept for reference; the public URL uses a generated id.
  • content_type (required) — string — Image type: "image/jpeg", "image/png", "image/gif" or "image/webp".
  • data_base64 (required) — string — 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.
  • 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 with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• list_media read-only

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

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• delete_media destructive

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

  Parameters:

  • media_id (required) — string — Id of the image (`media.id` from upload_media or list_media).
  • 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 with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• set_fact destructive

  Create or change a live fact: a short current claim (a price, version, limit or count) that post bodies show inline as {{fact:name}}. Every post that uses it is re-rendered with the new value. Use facts only for things that should stay current. Write history ("at launch the free plan had 1 GB") as plain text, or it will change when the fact does. Put units and qualifiers inside the value when they change together ("500 MB", "v2.4.1"): the words around a fact never update. `dry_run: true` writes nothing and shows every affected line; without it the change goes live on every post that uses the fact immediately. Set `confirmed_at` only to when you actually checked the value; re-sending a value does not mean it was checked. Facts can't go in headings, links, titles or excerpts. A fact used by any post can't be deleted until those posts stop using it.

  Parameters:

  • name (required) — string — Fact name: a lowercase letter, then up to 39 lowercase letters, digits or underscores, e.g. "pro_price". Post bodies use it as {{fact:pro_price}}.
  • value (required) — string — The current value, as plain text: 1–120 characters, one line, none of [ ] < > * _ ~ ` | \ { }. Put units and qualifiers inside it when they change together, e.g. "500 MB" or "v2.4.1".
  • note — Private note on where the value comes from, up to 200 characters. Not shown on pages. null clears it; omitted keeps it.
  • 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.
  • dry_run — boolean — true writes nothing and returns every post and line the change would affect. Without it the change goes live on every post that uses the fact immediately.
  • source_url — https URL the value was checked against. Not shown on pages. null clears it; omitted keeps it.
  • confirmed_at — string — When you actually checked the value: an ISO 8601 date ("2026-10-21") or date-time with a time zone ("2026-10-21T09:30:00Z"). Not in the future, not before 2000. Defaults to now, so only omit it when you checked just now.
  • expected_value — Compare-and-set: the value you believe is current (null: you believe the fact does not exist yet). If it differs, nothing changes and the call fails with FACT_CONFLICT carrying the current value.
  • 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 with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• list_facts read-only

  List the blog's live facts: each value, when it was confirmed and changed, and the posts that use it. Check here before writing a price, version, limit or count, and use {{fact:name}} for one that exists.

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• delete_fact destructive

  Delete a live fact. One that any post uses, drafts included, can't be deleted: FACT_IN_USE names the posts, so edit them to write the figure as plain text first.

  Parameters:

  • name (required) — string — Fact name: a lowercase letter, then up to 39 lowercase letters, digits or underscores, e.g. "pro_price". Post bodies use it as {{fact:pro_price}}.
  • 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 with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• get_ai_readership read-only

  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.

  Parameters:

  • days — number — Window in days, ending today (UTC): 7 (default), 30 or 90. A free blog always gets 7 and a `locked` list.
  • 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.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.