Jungle Scout MCP — Amazon sales estimates + product database + keyword data (junglescout.com).…
SUpost is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search listings, message posters, and create drafts on SUpost, the marketplace for Stanford
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http supost-mcp https://mcp.supost.com/mcp
# 2 — ask your agent for something these tools do
# search_listings, get_listing, get_market_stats and 4 more
SUpost costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http supost-mcp https://mcp.supost.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Full-text search query. |
| cat | string | no | Category id or label: 1/"jobs & services" (alias "jobs"), 3/"housing", 5/"for sale", 8/"friendship & dating", 9/"community". |
| university | integer | no | Numeric university id. Defaults to Stanford on supost.com. |
| max_price | number | no | Inclusive upper price bound in USD; excludes unpriced listings. |
| limit | integer | no | Page size (default 25, max 50). |
| cursor | string | no | Opaque cursor from a previous response's next_cursor. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric listing id, e.g. from search_listings. |
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.
No parameter schema on file.
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_ema
| Parameter | Type | Required | Notes |
|---|---|---|---|
| post_id | integer | yes | Numeric listing id, e.g. from search_listings or get_listing. |
| message | string | yes | Plain-text message to the poster (1-5000 characters). |
| reply_to_email | string | yes | 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status_key | string | yes | The status_key from a send_message result. |
The active category/subcategory taxonomy on SUpost — the valid category and subcategory values for create_post (and category filters for search_listings).
No parameter schema on file.
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), pub
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | Category id or label, e.g. "housing", "for sale" (see list_categories). |
| subcategory | string | yes | Subcategory id or name within the category, e.g. "bicycles" (see list_categories). |
| title | string | yes | Listing title. |
| body | string | yes | Plain-text listing description. |
| price | number | no | USD. Required for for-sale and housing-offering listings. |
| string | yes | The poster's own email address - determines posting eligibility and receives replies. Never invent or guess this - ask the user for it. | |
| publish | boolean | no | 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 - |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SUpost or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_listings | untrusted-input | untrusted-input: keyword "browse" |
| get_listing | untrusted-input | untrusted-input: keyword "fetch" |
| get_market_stats | no tags | |
| send_message | external-sink | external-sink: keyword "send_message" |
| check_message_status | no tags | |
| list_categories | no tags | |
| create_post | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.2.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish SUpost can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.