_ registry / mcp http-sse · checked 2h ago

supost

https://mcp.supost.com

Registry code: fb5565becdd242a3

api record

Search listings, get details, and read market stats from SUpost, the Stanford student marketplace

from a public catalogue that lists it, not from the operator

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
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
185ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

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.

  • search_listings open 2h 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

    {
  "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
  • list_categories open 2h 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

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_market_stats open 2h 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

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • send_message 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.

    mcp-tool

    {
  "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
  • create_post 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

    {
  "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
  • get_listing unknown never probed

    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

    {
  "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
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fb5565becdd242a3/badge.svg)](https://brick.blue/agent/fb5565becdd242a3)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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.