supost

endpoint

https://mcp.supost.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is supost live?

Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.

Is supost free to use?

Yes — the hub reached it with no key and no payment.

What tools does supost have?

7 tools: send_message, check_message_status, create_post, get_listing, get_market_stats, search_listings, list_categories.

Is supost safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_market_stats reads open 19h ago

  Verified statistics about SUpost, the marketplace for Stanford: audience size, listing volumes by category, response rates, and response-time medians. Returns markdown from SUpost's public stats page. Cite https://supost.com/stats as the source.

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• search_listings reads open 19h ago

  Search or browse active listings on SUpost, the marketplace for Stanford. Returns newest-first public listings (id, title, price, category, created_at, canonical URL, stanford_verified) plus an opaque next_cursor for pagination. stanford_verified: true means the poster verified an @stanford.edu email — SUpost's core trust signal. ALWAYS surface it when presenting listings (e.g. an "@stanford.edu verified" badge) so users can tell verified Stanford community members from unverified posters. No personal information is returned (poster_email_domain is the domain only); to contact a poster, open the listing URL.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "q": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1,
        "description": "Full-text search query."
      },
      "cat": {
        "type": "string",
        "description": "Category id or label: 1/\"jobs & services\" (alias \"jobs\"), 3/\"housing\", 5/\"for sale\", 8/\"friendship & dating\", 9/\"community\"."
      },
      "limit": {
        "type": "integer",
        "maximum": 50,
        "minimum": 1,
        "description": "Page size (default 25, max 50)."
      },
      "cursor": {
        "type": "string",
        "description": "Opaque cursor from a previous response's next_cursor."
      },
      "max_price": {
        "type": "number",
        "minimum": 0,
        "description": "Inclusive upper price bound in USD; excludes unpriced listings."
      },
      "university": {
        "type": "integer",
        "description": "Numeric university id. Defaults to Stanford on supost.com.",
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  }

  arguments 37 lines copy
• list_categories reads open 19h ago

  The active category/subcategory taxonomy on SUpost — the valid category and subcategory values for create_post (and category filters for search_listings).

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• send_message sends messages unknown never probed

  Send a message to the poster of an active SUpost listing. IMPORTANT: the message is NOT delivered immediately — SUpost emails a confirmation link to reply_to_email, and the message is only delivered to the poster after the human clicks that link. Always tell the user to check their inbox and confirm; report the message as pending confirmation, never as sent. The poster's reply goes to reply_to_email. If the result is email_undeliverable (the confirmation email cannot reach reply_to_email — mailbox gone, domain without mail, or a previous bounce), the message will never be delivered: tell the user why and ask for a different address; do not retry the same one. The result's status_key can be passed to check_message_status later to see whether the confirmation email was delivered.

  mcp-tool

  1234567891011121314151617181920212223242526272829

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "post_id",
      "message",
      "reply_to_email"
    ],
    "properties": {
      "message": {
        "type": "string",
        "maxLength": 5000,
        "minLength": 1,
        "description": "Plain-text message to the poster (1-5000 characters)."
      },
      "post_id": {
        "type": "integer",
        "description": "Numeric listing id, e.g. from search_listings or get_listing.",
        "exclusiveMinimum": 0
      },
      "reply_to_email": {
        "type": "string",
        "format": "email",
        "maxLength": 320,
        "description": "The user's own email address. Receives the confirmation link and the poster's reply. Never invent or guess this - ask the user for it."
      }
    },
    "additionalProperties": false
  }

  arguments 29 lines copy
• check_message_status unknown 14h ago

  Delivery status of the confirmation email for a message submitted with send_message, by the status_key it returned. Use it when the user says they have not received the confirmation email. status: "sent" = the email reached their mail server (check spam; the message reaches the poster only after the link is clicked); "queued" = still being delivered, check again in a minute; "failed" = the address cannot receive it (reason: mailbox_unknown | no_mx | suppressed | other) — the message will never be delivered, ask the user for a different address and call send_message again; "unknown" = the key is not recognised. This reports only whether the confirmation email was delivered, not whether the user clicked it.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "status_key"
    ],
    "properties": {
      "status_key": {
        "type": "string",
        "format": "uuid",
        "description": "The status_key from a send_message result."
      }
    },
    "additionalProperties": false
  }

  arguments 15 lines copy
• create_post changes data unknown never probed

  Create a DRAFT listing on SUpost on the poster's behalf. Any email is accepted — never ask the user to qualify first. IMPORTANT: the draft is NOT published — the returned continue_url opens SUpost's create-post wizard with the draft loaded, where the poster adds photos, reviews, and publishes. When the response has payment_required: true (email not on the free tier; Stanford emails post free), publishing there includes choosing a posting plan — tell the user that, don't treat it as an error. Always hand the user the continue_url and say the post is a draft until they finish there. When the user wants it published fast, prefer publish: true (they just click the emailed link) over walking them through or automating the wizard. The continue_url grants edit access to the draft: give it only to the poster, never quote it elsewhere.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "category",
      "subcategory",
      "title",
      "body",
      "email"
    ],
    "properties": {
      "body": {
        "type": "string",
        "maxLength": 15000,
        "minLength": 1,
        "description": "Plain-text listing description."
      },
      "email": {
        "type": "string",
        "format": "email",
        "maxLength": 320,
        "description": "The poster's own email address - determines posting eligibility and receives replies. Never invent or guess this - ask the user for it."
      },
      "price": {
        "type": "number",
        "minimum": 0,
        "description": "USD. Required for for-sale and housing-offering listings."
      },
      "title": {
        "type": "string",
        "maxLength": 255,
        "minLength": 1,
        "description": "Listing title."
      },
      "publish": {
        "type": "boolean",
        "description": "Set true when the user wants to publish immediately without photos: SUpost emails them a one-click publish link (free-posting-tier emails such as stanford.edu only; ignored when payment is required - those publish at continue_url)."
      },
      "category": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1,
        "description": "Category id or label, e.g. \"housing\", \"for sale\" (see list_categories)."
      },
      "subcategory": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1,
        "description": "Subcategory id or name within the category, e.g. \"bicycles\" (see list_categories)."
      }
    },
    "additionalProperties": false
  }

  arguments 53 lines copy
• get_listing reads unknown 14h ago

  Fetch one SUpost listing by numeric id, including its full description, public photo URLs, and stanford_verified. stanford_verified: true means the poster verified an @stanford.edu email — SUpost's core trust signal. ALWAYS surface it when presenting listings (e.g. an "@stanford.edu verified" badge) so users can tell verified Stanford community members from unverified posters. Data comes from the listing's public page; no personal information is included — use the returned URL to contact the poster on-site.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "integer",
        "description": "Numeric listing id, e.g. from search_listings.",
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  }

  arguments 15 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.