SlopIt MCP server

• Registry nameio.slopit/slopitverified in the MCP registry

The registry name sits under slopit.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools16
• Server calls itself@slopit/core
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 178 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Use2 GitHub stars
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer532 ms
• Space in an agent's context≈ 6,812 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsA · 99 of 100
• Typed results16 of 16 toolsdeclared outputSchema: results come typed, read once

• Parameters without a type: in 1 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• signup

  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…

• 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…

• 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…

• delete_post

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

• update_blog

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

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

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

• list_posts

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

• report_bug

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

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

• list_media

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

• delete_media

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

• set_fact

  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…

• list_facts

  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.

• delete_fact

  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.

• 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…