Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SlopIt

REMOTE · SLOPIT.IO

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

Available components

+3 this week 65 Trust /100

Last scanned (14 hours ago)

Scores higher than 47% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 14 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
Changelog

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.

  • 16 Oct 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.

  • 15 Oct 26 0
    • 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 security
    • “create_post” reworded the description of “seoTitle” cosmetic
  • 14 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.

  • 12 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Oct 26 62

    First indexed and scored.

Diagnostics

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://slopit.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=slopit.io CN=YE1,O=Let's Encrypt,C=US 23 Aug 2026 21 Nov 2026 ECDSA 256 ECDSA-SHA384 53c6774ddd771c9bbe049f80c2c1f46aea5
SANs: slopit.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 slopit.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
slopit.io. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://slopit.io/mcp Verified 200
http (plaintext) http://slopit.io/mcp HTTPS enforced 308 https://slopit.io/mcp
MCP tools · 13 exposed · ~3,326 tokens

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 →

Tool Tokens
create_post ~793

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.

NameTypeReqDescription
authorstring–Author name, up to 100 characters. Used in the page's metadata, the feed and the markdown source.
blog_idstring–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.
bodystringyesPost content as markdown. Raw HTML is stripped. A YouTube URL alone on its own line becomes an embedded player.
coverImagestring–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.
excerptstring–Summary shown under the title in the post list, up to 300 characters. Omit to derive it from the body.
idempotency_keystring–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…
languagestring–Language of this post as a BCP-47 tag, e.g. "en", "ru", "pt-BR". Omit to inherit the blog's language.
seoDescriptionstring–Description for search results and link previews, up to 300 characters. Defaults to the excerpt.
seoTitlestring–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>".
slugstring–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…
statusstring–"published" (default) puts the post live immediately; "draft" saves it without publishing.
tagsarray–Tags shown on the post page, e.g. ["ai", "travel"]. Defaults to none.
titlestringyesPost title, 1–200 characters. The slug is derived from it when `slug` is omitted.
translationOfstring–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…
NameTypeReqDescription
errorobject–Present only on failure (isError: true). Success fields are absent then.
postobject––
post_urlstring–Live URL of the post. Present only when it is published.
preview_urlstring–Private link to a rendered draft for the human to review: not indexed, not listed anywhere. Present only for drafts, on hosts with previews.

No examples provided.

delete_media ~173

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

NameTypeReqDescription
blog_idstring–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_keystring–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_idstringyesId of the image (`media.id` from upload_media or list_media).
NameTypeReqDescription
deletedboolean––
errorobject–Present only on failure (isError: true). Success fields are absent then.

No examples provided.

delete_post ~162

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

NameTypeReqDescription
blog_idstring–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_keystring–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…
slugstringyesSlug of the post, e.g. "hello-world", as returned by create_post or list_posts.
NameTypeReqDescription
deletedboolean––
errorobject–Present only on failure (isError: true). Success fields are absent then.

No examples provided.

get_ai_readership ~468

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.

NameTypeReqDescription
blog_idstring–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.
daysnumber–Window in days, ending today (UTC): 7 (default), 30 or 90. A free blog always gets 7 and a `locked` list.
NameTypeReqDescription
blog_idstring––
counting_sincestring–YYYY-MM-DD (UTC). Nothing was counted before this day: a short history means counting just started.
dailyarray–Pro only. One entry per day of the window, oldest first.
errorobject–Present only on failure (isError: true). Success fields are absent then.
lockedarray–Free only. What Pro adds: "posts", "system_counts", "history".
notesarray–Caveats to pass on: the numbers undercount, and a live fetch is not a citation.
planstring–"free" or "pro".
postsarray–Pro only. Each post an AI read, strongest signal first (click, live, search, training).
systemsarray–Pro only. Which AI systems read the blog, by tier then count.
tiersobject–Counted reads per tier, strongest signal first.
unverifiednumber–Requests in the window that claimed to be an AI crawler but failed the address check. Not AI reads, not in `tiers`.
upgradestring–Free only. How to get Pro, worded for this endpoint. If you pass it on, keep its wording.
windowobject––

No examples provided.

get_blog ~94

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.

NameTypeReqDescription
blog_idstring–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.
NameTypeReqDescription
blogobject––
blog_urlstring–The blog's public URL (its custom domain once one is verified). Posts live at {blog_url}{slug}/.
errorobject–Present only on failure (isError: true). Success fields are absent then.

No examples provided.

get_post ~120

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.

NameTypeReqDescription
blog_idstring–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.
slugstringyesSlug of the post, e.g. "hello-world", as returned by create_post or list_posts.
NameTypeReqDescription
errorobject–Present only on failure (isError: true). Success fields are absent then.
postobject––
preview_urlstring–Private link to a rendered draft for the human to review: not indexed, not listed anywhere. Present only for drafts, on hosts with previews.

No examples provided.

list_media ~81

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

NameTypeReqDescription
blog_idstring–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.
NameTypeReqDescription
errorobject–Present only on failure (isError: true). Success fields are absent then.
mediaarray––

No examples provided.

list_posts ~110

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

NameTypeReqDescription
blog_idstring–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.
statusstring–"published" (default) lists live posts, newest published first; "draft" lists drafts, newest created first.
NameTypeReqDescription
errorobject–Present only on failure (isError: true). Success fields are absent then.
postsarray––

No examples provided.

report_bug ~62

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

NameTypeReqDescription
details––Anything that helps reproduce it, e.g. the tool you called, its arguments and the error you got.
summarystring–One line on what went wrong.
NameTypeReqDescription
errorobject–Present only on failure (isError: true). Success fields are absent then.

No examples provided.

signup ~450

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.

NameTypeReqDescription
emailstring–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.
languagestring–Default language for the blog as a BCP-47 tag, e.g. "en", "ru", "pt-BR". Defaults to "en". Individual posts may override it.
namestring–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…
themestring–Blog theme. Only "minimal" exists today.
titlestring–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.
NameTypeReqDescription
api_keystring–Send as "Authorization: Bearer <api_key>". Shown once; save it.
blog_idstring–Pass as blog_id to every other tool.
blog_urlstring–Live URL of the blog.
email_sentboolean–True only when an email was given and the welcome email went out.
errorobject–Present only on failure (isError: true). Success fields are absent then.
mcp_endpointstring––
onboarding_textstring–Next steps addressed to you, the agent. Contains the API key.
terms_urlstring––

No examples provided.

update_blog ~206

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.

NameTypeReqDescription
blog_idstring–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_keystring–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…
patchobjectyesBlog settings to change; omitted fields stay as they are.
NameTypeReqDescription
blogobject––
blog_urlstring–The blog's public URL (its custom domain once one is verified). Posts live at {blog_url}{slug}/.
errorobject–Present only on failure (isError: true). Success fields are absent then.

No examples provided.

update_post ~319

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

NameTypeReqDescription
blog_idstring–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_keystring–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…
patchobjectyesFields to change; omitted fields stay as they are. Same fields as create_post except `slug`, which cannot change.
slugstringyesSlug of the post, e.g. "hello-world", as returned by create_post or list_posts.
NameTypeReqDescription
errorobject–Present only on failure (isError: true). Success fields are absent then.
postobject––
post_urlstring–Live URL of the post. Present only when it is published.
preview_urlstring–Private link to a rendered draft for the human to review: not indexed, not listed anywhere. Present only for drafts, on hosts with previews.

No examples provided.

upload_media ~288

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.

NameTypeReqDescription
blog_idstring–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_typestringyesImage type: "image/jpeg", "image/png", "image/gif" or "image/webp".
data_base64stringyesThe 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.
filenamestringyesOriginal file name, e.g. "castle.jpg". Kept for reference; the public URL uses a generated id.
idempotency_keystring–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…
NameTypeReqDescription
errorobject–Present only on failure (isError: true). Success fields are absent then.
mediaobject––

No examples provided.

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.

remote · slopit.io

# add to Claude Code
claude mcp add --transport http io-slopit-slopit 'https://slopit.io/mcp'
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.