io.github.Capmus-Team/supost-mcp
REMOTE · MCP.SUPOST.COM · SCANNED AUG 3
Search listings, message posters, and create drafts on SUpost, the marketplace for Stanford
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1027 tokens (~171/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.supost.com
claude mcp add --transport http capmus-team-supost-mcp https://mcp.supost.com/mcp
[mcp_servers.capmus-team-supost-mcp] url = "https://mcp.supost.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"capmus-team-supost-mcp": {
"type": "remote",
"url": "https://mcp.supost.com/mcp",
"enabled": true
}
}
} openclaw mcp add capmus-team-supost-mcp --url https://mcp.supost.com/mcp --transport streamable-http
mcp_servers:
capmus-team-supost-mcp:
url: "https://mcp.supost.com/mcp" {
"mcpServers": {
"capmus-team-supost-mcp": {
"type": "http",
"url": "https://mcp.supost.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.supost.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.supost.com | CN=YR1,O=Let's Encrypt,C=US | 10 Jul 2026 | 8 Oct 2026 | RSA 2048 | SHA256-RSA | 5334edb852ae2881daf8709260e458a8bfd |
| SANs: mcp.supost.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.supost.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| supost.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.supost.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.supost.com/mcp | HTTPS enforced | 308 | https://mcp.supost.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
create_post Create a SUpost draft listing ~362
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Plain-text listing description. |
| category | string | yes | Category id or label, e.g. "housing", "for sale" (see list_categories). |
| string | yes | The poster's own email address - determines posting eligibility and receives replies. Never invent or guess this - ask the user for it. | |
| price | number | — | USD. Required for for-sale and housing-offering listings. |
| publish | boolean | — | 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 -… |
| subcategory | string | yes | Subcategory id or name within the category, e.g. "bicycles" (see list_categories). |
| title | string | yes | Listing title. |
No output schema declared.
No examples provided.
get_listing Get a SUpost listing ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric listing id, e.g. from search_listings. |
No output schema declared.
No examples provided.
get_market_stats Get SUpost market statistics ~61
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_categories List SUpost categories ~38
The active category/subcategory taxonomy on SUpost — the valid category and subcategory values for create_post (and category filters for search_listings).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_listings Search SUpost listings ~265
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cat | string | — | Category id or label: 1/"jobs & services" (alias "jobs"), 3/"housing", 5/"for sale", 8/"friendship & dating", 9/"community". |
| cursor | string | — | Opaque cursor from a previous response's next_cursor. |
| limit | integer | — | Page size (default 25, max 50). |
| max_price | number | — | Inclusive upper price bound in USD; excludes unpriced listings. |
| q | string | — | Full-text search query. |
| university | integer | — | Numeric university id. Defaults to Stanford on supost.com. |
No output schema declared.
No examples provided.
send_message Message a SUpost poster ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Plain-text message to the poster (1-5000 characters). |
| post_id | integer | yes | Numeric listing id, e.g. from search_listings or get_listing. |
| 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. |
No output schema declared.
No examples provided.