io.github.Capmus-Team/capmus-mcp

Est-ce que io.github.Capmus-Team/capmus-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.Capmus-Team/capmus-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 7 outils

• check_message_status≈ 275 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • status_key · string · requis
    The status_key from a send_message result.

  Exemple d'appel

  {"name": "check_message_status", "arguments": {"status_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_post≈ 572 tokens

  Create a DRAFT listing on Capmus 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 Capmus'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.

  Paramètres, retour & exemple (7)

  Paramètres

  • body · string · requis
    Plain-text listing description.
  • email · string · requis
    The poster's own email address - determines posting eligibility and receives replies. Never invent or guess this - ask the user for it.
  • price · number · optionnel
    USD. Required for for-sale and housing-offering listings.
  • title · string · requis
    Listing title.
  • publish · boolean · optionnel
    Set true when the user wants to publish immediately without photos: Capmus 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 · string · requis
    Category id or label, e.g. "housing", "for sale" (see list_categories).
  • subcategory · string · requis
    Subcategory id or name within the category, e.g. "bicycles" (see list_categories).

  Exemple d'appel

  {"name": "create_post", "arguments": {"body": "texte", "email": "texte", "title": "texte", "category": "texte", "subcategory": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_listing≈ 212 tokens

  Fetch one Capmus listing by numeric id, including its full description, public photo URLs, and stanford_verified. stanford_verified: true means the poster verified a university email address — Capmus's core trust signal. ALWAYS surface it when presenting listings (e.g. a "verified" badge) so users can tell verified campus 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · integer · requis
    Numeric listing id, e.g. from search_listings.

  Exemple d'appel

  {"name": "get_listing", "arguments": {"id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_market_stats≈ 116 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_market_stats", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_categories≈ 86 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_categories", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_listings≈ 400 tokens

  Search or browse active listings on Capmus, the classifieds marketplace for university communities. 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 a university email address — Capmus's core trust signal. ALWAYS surface it when presenting listings (e.g. a "verified" badge) so users can tell verified campus 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.

  Paramètres, retour & exemple (6)

  Paramètres

  • q · string · optionnel
    Full-text search query.
  • cat · string · optionnel
    Category id or label: 1/"jobs & services" (alias "jobs"), 3/"housing", 5/"for sale", 8/"friendship & dating", 9/"community".
  • limit · integer · optionnel
    Page size (default 25, max 50).
  • cursor · string · optionnel
    Opaque cursor from a previous response's next_cursor.
  • max_price · number · optionnel
    Inclusive upper price bound in USD; excludes unpriced listings.
  • university · integer · optionnel
    Numeric university id to scope results to one campus.

  Exemple d'appel

  {"name": "search_listings", "arguments": {"q": "texte", "cat": "texte", "limit": 1, "cursor": "texte", "max_price": 1, "university": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• send_message≈ 390 tokens

  Send a message to the poster of an active Capmus listing. IMPORTANT: the message is NOT delivered immediately — Capmus 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • message · string · requis
    Plain-text message to the poster (1-5000 characters).
  • post_id · integer · requis
    Numeric listing id, e.g. from search_listings or get_listing.
  • reply_to_email · string · requis
    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.

  Exemple d'appel

  {"name": "send_message", "arguments": {"message": "texte", "post_id": 1, "reply_to_email": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.capmus.com/mcp