Capmus MCP server

• check_message_statusFree

  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.

• create_postwrite actionFree

  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.

• get_listingFree

  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.

• get_market_statsFree

  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.

• list_categoriesFree

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

• search_listingsFree

  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.

• send_messagewrite actionFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 467ms20/20
• Tool poisoning7 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
• Maintenancelast push 8 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

83/100

higher than 70% of 3,470 Web search servers

Tools

7

the typical Web search server has 5

Tools that change things

29%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Web search server answers 100%

Response time

109 ms

faster than 86% of 2,238 Web search servers

Capmus: common questions

Is Capmus MCP server safe?

Mostly: it is graded B (83/100). Read the Capmus safety report

How do I install Capmus?

It runs remotely at mcp.capmus.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Capmus need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Capmus maintained?

The last commit was 47 days ago (2026-09-18). The latest release is v0.2.2.

Is Capmus up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Capmus?

Servers from other publishers that do the same job: Reddit MCP server, Apple Contacts MCP server and HasData Yellow Pages MCP server.

How does Capmus compare with other Web search MCP servers?

safety score 83/100 (higher than 70% of 3,470 Web search servers); tools 7 (the typical Web search server has 5); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.