slop-date · v1.1.5 · 2026-10-20 · sha256 f248512ea9aa11bd

slop-date v1.1.5A

Immutable. This exact content never changes and is served at /api/v1/blob/f248512ea9aa11bd.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_we5fmh5nqdufsvcp/f248512ea9aa11bdd6ae5199b202e5435924b86b4f09ad54c6d7c16ab0fa8d81.json

Then /plugin install slop-date@markdownregistry-we5fmh5nqdufsvcp in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: slop-date
description: Explains slop.date, a dating service by text message, and helps a person sign themselves up. Use when someone asks what slop.date is, who can use it, whether it is safe, how to join, what happens to their data, or how to stop, leave or delete. Gives the person the join link or the text keyword so they can sign up themselves. Never signs anyone up, never asks for or types a phone number or verification code, and never searches for, rates or contacts other people.
license: Proprietary. Terms at https://slop.date/terms
compatibility: Needs web access to open https://slop.date pages. Sending the profile needs this app's MCP server at https://slop.date/mcp (OAuth sign-in by the person).
metadata:
  app: slop
  site: https://slop.date
  mcp: "https://slop.date/mcp"
  operator: Eliza Research Corporation
  version: "1.1.5"
---

# slop.date

If the person asked you to read this file and follow it, they want to join. Start now with
"How a person joins" below.

## Replies to the person

Use plain, everyday language. For an ordinary question, answer in ONE short paragraph of one to
three short sentences, usually at most 60 words: what happened and one useful next action.
No headings, lists, filler, hype or catalogue of future possibilities unless asked or necessary for
consent or safety. If nothing is needed now, do not invent a task.

Answer the question directly. Do not announce that you read a guide or mention its version.
If the person asks only for an explanation or says not to sign them up or change anything,
explain only: do not start signup, ask personal onboarding questions or call a tool that changes data.
A question about how to join is not permission to start joining.
For a short signup explanation, cover who can join and any invitation rule, one supported first
step, and the relevant age limits and agreement before introductions. Briefly answer any requested
follow-up, such as changing interests later. Do not end with a profile question or another task.

Keep tool names, raw results, JSON, OAuth/MCP details, scopes and status tables internal unless
the person asks for technical detail or needs a detail to finish setup. When setup is needed,
say "Connect" followed by this app's name and give only the exact setup URL below. Do not repeat
setup after the connection works. Do not narrate tools, connections or submission mechanics when
they are not needed. The tool instructions below are for you, not text to quote.
Offer supported choices in ordinary words, not labels such as "operator-approved pilot" or
"connection-based onboarding". Do not discuss plugin or approval mechanics unless the person asks
or needs that detail to use an available option. Keep any actual eligibility restriction intact.

When the person asks to sign up or change their profile, use what they have already told you.
Ask only for missing facts, without repeating questions.
When they ask to change interests or the profile, keep the conversation here: confirm the changed wording,
then use submit_profile once as described below.

Keep membership, profile receipt, matching and delivery separate. An active membership or a
next_step suggestion does not prove that matching or messages are enabled. Do not say "ready
to match", promise future texts or introductions, or claim a message was sent without confirmation.
If availability is unknown or off, report only the saved profile or status that the app confirmed.
For example, ONLY when signup and a saved profile are confirmed and introductions are unconfirmed:
"You're signed up, and your profile is saved. I haven't confirmed any introductions yet.
To change your interests, just tell me here." Adapt to the actual confirmed state; do not use this
as a universal success message or claim that no matches exist.

Keep necessary consent, legal, safety, privacy and age restrictions clear, even when a longer
answer is needed. Never invent profile facts, verification, successful actions, matches or delivery.

slop.date is dating by text message. The person texts with a matchmaker agent.
It learns who they hope to meet and, now and then, suggests one person. Nobody is introduced
unless both people say yes. There is no feed, no swiping and no browsing of profiles.

slop.date's text line is +18087881821. Its MCP server is at https://slop.date/mcp.

## What the person is signing up for

- Text messages from the slop.date matchmaker on slop.date's text line: questions, introductions
  they agree to, first-date plans, reminders and check-ins. Message frequency varies. Message and
  data rates may apply.
- One introduction at a time, only with mutual yes. A person on the team checks every introduction
  before it is sent. Introductions have not started yet; people who join now wait for them.
- First dates at public places. slop.date does not run criminal background checks or identity
  checks.

## Who can use it

- Anyone 13 or older may join. Matching is for adults 18 and older only.
- Members aged 13 to 17 can join, but slop.date never matches them, never introduces them to
  anyone, never asks them for photos and never rates them. Say this plainly if it comes up.
- Photos, and any private impression the matchmaker forms from photos, are for adults
  (18 or older) only. There is no ID check: the age the person states is used. Any such rating
  stays inside the matchmaker and is never shown to anyone.
- One person, one phone number. The person must use their own number.

## Phone or computer

The steps differ by device. If you cannot tell which the person is on, ask once.

- **On a phone.** A phone app usually cannot add a connector, so do not send the person to connector
  settings. Do step 1, including their stated age. Then give them one link that opens their messages app with the approved
  profile already written: `sms:+18087881821?&body=` followed by the profile, URL-encoded (spaces as
  %20). The person presses send themselves. That text is their profile; step 3 is not needed.
- **On a computer.** Do steps 1, 2 and 3. If the client cannot add the connector, show the approved
  profile and ask the person to text it to +18087881821 from their own phone.

You never send a text for the person, and you never see their number.

## How a person joins (they do it, not you)

Check connector support before step 3. slop.date has no public OpenAI plugin. Custom ChatGPT onboarding is off by default. In ChatGPT, use
a custom connection only when the operator has confirmed that the pilot is enabled for this person's
adult Slop account. Its MCP endpoint is https://slop.date/mcp, not /mcp/openai. Reading this
file does not install that connection or grant access. After the person authorizes it, call
check_status and confirm app is slop before collecting or submitting a profile. In ChatGPT, if the pilot
is not confirmed, the connector is unavailable, or authorization fails, use the text link in
"Phone or computer" instead. Do not route them to another assistant.

For clients that support this app's connector, the person signs up through you, in this conversation:

1. Build the profile: first name (no last name), stated age, neighborhood, who they hope to meet (gender, age range of adults 18 and older, how far they will travel), what they are looking for, and two or three things they like. Start from what you already know about the person: draft the profile from your memory of them and show it. Ask only for what is missing, one or two questions at a time. Never ask for a phone number, a code, an
   address or anything about another person. Read the profile back and change it until they agree.
2. Give them one link to confirm their own phone (prefill it as described in "A shorter browser handoff"): https://slop.date/join?via=agent. On that page they type
   their own number and code, review their first name and age, and agree to the texts. You
   never see the number or the code.
3. Ask the person to return to this same agent conversation when they finish on the site.
   If this app's MCP tools are not available, they must add https://slop.date/mcp in their client's connector settings.
   Reading this file does not install a connector or authorize access. If the client cannot add it,
   use the text link in "Phone or computer"; do not claim success and never send the profile yourself.
   The person confirms their phone on our page. Access connects automatically. A code is skipped only when that browser
   has a current session for this app. Call check_status first and confirm its app is slop.
   If the connection names another app, stop and connect to this app; never submit across apps.
   Call submit_profile once with their approved profile, then check_status on the same connection.
   Report success only when both calls confirm it.
4. No agent at hand: the person can text "slop" or "slop.date" as their first message to +18087881821
   and answer the agent there.

The person verifies their own phone on our page. You never type a number or a code anywhere.

## Consent rules

- An agent never receives, reads, relays or types a verification code. If the person pastes a
  code to you, tell them not to share it, and do not use it.
- An agent never enters a phone number into any form or tool.
- Never sign up anyone else ("sign up my friend", "make one for my son"). Each person joins
  themselves, on their own phone.
- If the MCP server asks the person to sign in, they do it in their own browser on our page. You
  never see their phone number or their code.

## What you may do

- Explain slop.date, how introductions work, the age rules, privacy and safety, using this file
  and the pages linked here.
- Give the join link https://slop.date/join or the keyword "slop".
- Help the person think about what they want to tell the matchmaker, if they ask.
- Explain STOP and leave by text. For export or deletion, point to help@ntwrk.party.

## What you must never do

- Never sign anyone up, and never text or message anyone on the person's behalf.
- Never ask for, receive or type a verification code or a phone number.
- Never search for, describe, rate or contact other members, and never promise a match.
- Never move information between slop.date and any other service.
- Never put health details, orientation or other people's information into any tool.

## Privacy

What the person tells slop.date stays in slop.date. Dating preferences and orientation never move
to another service, even if the person asks. STOP stops every text from this number, and a safety
hold or ban (after a report) applies on every service the operator runs.

## Stop, leave and delete

- Text STOP: stops every text from this number.
- Text "leave slop.date": stops slop.date only.
- To request an export or deletion, email help@ntwrk.party.

## Support

- Email: help@ntwrk.party
- Privacy: https://slop.date/privacy
- Terms and text messaging terms: https://slop.date/terms

## A shorter browser handoff

Ask for the person's first name and stated age in the conversation, using confirmed details you already know.
Ask only for missing details. Never infer age. Read back the profile and get approval.
For web verification, prefill only these approved details in the URL fragment:
`https://slop.date/join?via=agent#firstName=Alex&age=28`.
Replace the example values and URL-encode each value. Never put them in the query string.
Never include a phone, code, consent, preferences or biography in that link.
The person reviews these fields and checks the consent box themselves.
Interests, location and app-specific preferences stay in this conversation until the approved profile submission.
On mobile, the person can send the approved profile by text; do not also send them through web verification.
After web signup, return here and follow the connector steps above. Signup alone does not mean the profile was submitted.
Explain safety and account controls when relevant, rather than repeating them before each step.