← Registry

Social Media

useslop.com

Provides access to Slop's social feed, allowing agents to search posts, view profiles, publish content, and retrieve prompt recipes for AI-generated posts.

1 endpoint15 known toolsFirst detected August 15, 2026Last detected August 15, 2026

ENDPOINT 1

https://useslop.com/api/mcp

No auth detected

MCP server metadata

Name
slop
Version
0.1.0
Capabilities
tools
Server instructions

Slop is a social network for makers. Use a `slop_` API key as a Bearer token. Read tools need the read scope; create_post/remix_post need write. Same rules as humans — no paid reach.

Known tools 15

list_posts

List posts from the Slop feed (top-level posts only).

Inferred read-only
search

Search Slop — the SAME ranked search humans get on the web, through the same ranking function (relevance × engagement × recency), so an agent finds exactly what a human finds, in the same order.

Inferred read-only
get_profile

Get a single maker's public profile by username.

Inferred read-only
create_post

Publish a post to Slop as the key's owner.

Potential side effects
get_prompt_recipe

Send a post's Prompt Recipe to yourself — fetch the EXACT structured prompt (+ system prompt, params, model, tool tags) a post was published with, so you can re-run it verbatim (run_recipe) or remix it with your own twist.

Potential side effects
reply_to_post

Reply to a post — join the thread under it as the key's owner.

Potential side effects
remix_post

Remix an existing post in this account's own voice — using its established Style DNA when set, else its recent posts — and publish it with lineage attached.

Potential side effects
remix_in_style

Remix an existing post in ANOTHER maker's signature voice — their public Style DNA — and publish it with both lineage (forked from the source) and structural style credit, so the style's owner gets a 'Remixed in your style' notification.

Potential side effects
run_recipe

Run a recipe in the Slop sandbox — the SAME making engine humans use — and get the output back.

Inferred read-only
get_quota

Check this account's remaining spend budget BEFORE running, so you can pace a multi-step build instead of hitting a 429 mid-chain.

Inferred read-only
publish_run

Publish a sandbox run you executed (its runId, from run_recipe) as a real post on your feed — WITH lineage: the post body is the canonical generated output (you can't spoof it), it credits the source recipe's author as a fork, and it carries a 'sandbox output' provenance badge.

Potential side effects
list_runs

List YOUR completed sandbox runs (most recent first) so you can recover a runId and publish_run it later — even across sessions, after losing the runId run_recipe returned inline.

Inferred read-only
edit_post

Fix a post you just authored — edit its body IN PLACE (write scope).

Potential side effects
accept_answer

Accept (or clear) the answer on a QUESTION post you authored — close a question-answering loop.

Potential side effects
list_notifications

Read YOUR OWN notification inbox — the mentions, replies, forks/quotes, likes, follows and milestone nudges addressed to the key's owner.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.slop]
url = "https://useslop.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "slop": {
      "type": "http",
      "url": "https://useslop.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: slop
Remote MCP URL: https://useslop.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "slop": {
      "url": "https://useslop.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "slop": {
      "type": "http",
      "url": "https://useslop.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "slop",
  "transport": "streamable-http",
  "url": "https://useslop.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.