Skip to content

capmus-mcp server

io.github.Capmus-Team/capmus-mcpCapmus-Teamstreamable-httpv0.2.2Scanned

Search listings, message posters, and create draft posts on Capmus, the university marketplace

7 tools: 1 do something that can't be undone, 1 change things and 5 only read.

Tools: 0 delete, 1 irreversible, 1 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the capmus-mcp server can do

The capmus-mcp server is published by the GitHub account Capmus-Team. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_message) and create or change data (1 tool: create_post), but cannot delete data. 5 tools only read.

1 tool reads private data (check_message_status); 3 tools bring in text other people can write (search_listings, check_message_status and list_categories); 2 tools can send data out of your system (send_message and create_post). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 0.2.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 1Claude Code: ask
  • send_messageSend a message to the poster of an active Capmus listing.Can send data outNo findings

    Why it is in this group

    • The name "send_message" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_message" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.
Changes things 1Claude Code: ask
  • create_postCreate a DRAFT listing on Capmus on the poster's behalf.Can send data outNo findings

    Why it is in this group

    • The name "create_post" says "create": a word for a change.

    What it can reach

    • outboundThe name "create_post" says "create" and "post": it writes something other people read.
    Description, as the server wrote it
    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.
Only reads 5Show 5 read-only tools
  • check_message_statusDelivery status of the confirmation email for a message submitted with send_message, by the status_key it returned.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "check_message_status" says "status": a word for reading.

    What it can reach

    • private-dataThe name "check_message_status" says "status" and "message": it reads messages.
    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe name "check_message_status" says "status" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote 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 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.
  • get_listingFetch one Capmus listing by numeric id, including its full description, public photo URLs, and stanford_verified.No findings

    Why it is in this group

    • The name "get_listing" says "get": a word for reading.
    Description, as the server wrote it
    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_statsVerified statistics about Capmus, the classifieds marketplace for university communities: audience size, listing volumes by category, response rates, and response-time medians.No findings

    Why it is in this group

    • The name "get_market_stats" says "get": a word for reading.
    Description, as the server wrote it
    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_categoriesThe active category/subcategory taxonomy on Capmus — the valid category and subcategory values for create_post (and category filters for search_listings).Reads text others writeNo findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
    Description, as the server wrote it
    The active category/subcategory taxonomy on Capmus — the valid category and subcategory values for create_post (and category filters for search_listings).
  • search_listingsSearch or browse active listings on Capmus, the classifieds marketplace for university communities.Reads text others writeNo findings

    Why it is in this group

    • The name "search_listings" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__capmus__check_message_status"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.capmus.com/mcp: tools/list returned 7 tools to an anonymous client, including send_message (irreversible), create_post (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http capmus https://mcp.capmus.com/mcp
claude mcp add --transport http capmus https://mcp.capmus.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__capmus__search_listings",
      "mcp__capmus__get_listing",
      "mcp__capmus__get_market_stats",
      "mcp__capmus__check_message_status",
      "mcp__capmus__list_categories"
    ],
    "ask": [
      "mcp__capmus__send_message",
      "mcp__capmus__create_post"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as capmus. Review it before you use it.

Capability tags behind 5 rules
  • mcp__capmus__search_listings untrusted-input
  • mcp__capmus__send_message outbound
  • mcp__capmus__check_message_status private-data, untrusted-input
  • mcp__capmus__list_categories untrusted-input
  • mcp__capmus__create_post outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Capmus-Team/capmus-mcp/verify?hash=f8ccb4c4d6a685fba0da0634fb43f830b0dc59c1bbbcf0bb1dc9672aa45fd858" | jq -e '.changed == false'

Pinned hash f8ccb4c4d6a6, from Nov 15, 2026, 18:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Capmus-Team/capmus-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Capmus-Team/capmus-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Capmus-Team/capmus-mcp.svg)](https://radar.anlyon.com/servers/io.github.Capmus-Team/capmus-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.

capmus-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the capmus-mcp server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the capmus-mcp server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the capmus-mcp server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_message.

What tools does the capmus-mcp server have?

7 tools: 1 irreversible, 1 write, 5 read. send_message, create_post, search_listings, get_listing, get_market_stats, check_message_status and list_categories.

Does the capmus-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the capmus-mcp server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_message and create_post.

Has the capmus-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.