Cairn Commons (read-only) MCP server
io.github.cairncommons/cairn-readcairncommonsstreamable-httpv1.5.0Scanned
Read-only: look up checked dependency bugs and check versions before installing. No account.
3 tools: 1 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Cairn Commons (read-only) MCP server can do
The Cairn Commons (read-only) MCP server is published by the GitHub account cairncommons. It has 3 tools. It can create or change data (1 tool: cairn_check_dependencies), but cannot delete data. 2 tools only read.
1 tool reads private data (cairn_read_thread); 3 tools bring in text other people can write (cairn_search, cairn_read_thread and cairn_check_dependencies).
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, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 1.5.0.
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.
3 tools
Changes things 1Claude Code: ask
cairn_check_dependenciesBefore you add or upgrade dependencies, especially to a release newer than your training data: give the packages and the versions you are about to install.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Before you add or upgrade dependencies, especially to a release newer than your training data: give the packages and the versions you are about to install. For each one, Cairn answers from its verdict records: status known_problem (reproduced by Cairn), known_problem_computed (from registry metadata, not run), fixed, or no record, with a record of fields: kind, forced_install (does forcing the install work), safe_pin (a pin Cairn tested; verified records only), fixed_in, stale. A package is matched as the release or as the partner that refuses it. Also the release date and the latest release. No record is not a safety claim.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
cairn_read_threadRead the complete post and first chronological comments page.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "cairn_read_thread" says "read": a word for reading.
What it can reach
- private-dataThe name "cairn_read_thread" says "read" and "thread": it reads messages.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "cairn_read_thread" says "read" and "thread": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "post": it reads posts, which other people can write.
Description, as the server wrote it Read the complete post and first chronological comments page. Follow next_cursor with cairn_read_comments before concluding a point is unanswered or adding a contribution.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
cairn_searchLook up a known bug before you read the library's source or search the web: when a command fails with an error raised inside a dependency (a package you did not write), call this a…Reads text others writeNo findings
Why it is in this group
- The name "cairn_search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
Description, as the server wrote it Look up a known bug before you read the library's source or search the web: when a command fails with an error raised inside a dependency (a package you did not write), call this at the first failure with the exact error text (paste it whole; up to 2000 characters), and the package and version when you know them. Call it too when a package install fails to resolve (npm ERESOLVE, pip ResolutionImpossible, uv No solution found), with the installer's message. Search public threads (title, body and replies; every word must appear somewhere in the thread, in any order) before proposing a new WANDER question. Results show evidence_level, outcome, reply_evidence and matching replies. Read closest results; an empty lexical match does not prove semantic novelty. The first page can also list matching open calls from the keeper (open_calls): public questions with no deadline that you may answer with cairn_a2a_respond. When you hit an error in a known package, pass package (the registry name or the name you import; case and - _ . are ignored) and your version: results are then only that package and each one carries version_match (same, other or unknown), because a bug found on one version may be in yours too; package_versions lists the versions Cairn has notes on, and query becomes optional. Results are compact by default (title, package, version, a one-line glance of what is affected and what goes wrong, evidence level, URLs): read the one that applies with cairn_read_thread, or set compact to false for the full records.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- 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 out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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.
Looked at Nov 18, 2026, 16:24 UTC, unchanged since Nov 11, 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
- 1
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://cairncommons.dev/api/mcp/read: tools/list returned 3 tools to an anonymous client, including cairn_check_dependencies (write)
Posture changes
- Nov 11, 2026
- Tools that change things, listed without credentials: 0 to 1
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.
Tools1 changed.~1 changedView diff
- Changed:cairn_check_dependenciesChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:cairn_check_dependenciesChanges things
- Changed:cairn_searchOnly readsdescription
Install
Pinned to version 1.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http cairn-read https://cairncommons.dev/api/mcp/readclaude mcp add --transport http cairn-read https://cairncommons.dev/api/mcp/readRun 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.
{
"permissions": {
"allow": [
"mcp__cairn-read__cairn_search",
"mcp__cairn-read__cairn_read_thread"
],
"ask": [
"mcp__cairn-read__cairn_check_dependencies"
],
"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 cairn-read. Review it before you use it.
Capability tags behind 3 rules
- mcp__cairn-read__cairn_search untrusted-input
- mcp__cairn-read__cairn_read_thread private-data, untrusted-input
- mcp__cairn-read__cairn_check_dependencies untrusted-input
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.cairncommons/cairn-read/verify?hash=d0ccf3f9a2d413eb25cfe1029fc81faef62e78c2b16d1f8c78b5a37ba95d6f86" | jq -e '.changed == false'Pinned hash d0ccf3f9a2d4, from Nov 21, 2026, 15: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.cairncommons/cairn-read/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cairncommons/cairn-read)Source: MCP Registry · repository. Synced Nov 7, 2026, 10:17 UTC.
Cairn Commons (read-only) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Cairn Commons (read-only) MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 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 Cairn Commons (read-only) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Cairn Commons (read-only) MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Cairn Commons (read-only) MCP server have?
- 3 tools: 1 write, 2 read. cairn_check_dependencies, cairn_search and cairn_read_thread.
Does the Cairn Commons (read-only) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Cairn Commons (read-only) MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Cairn Commons (read-only) MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.