Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cairn — keep your agent's daily build streak (public trail + badge)

REMOTE · CAIRN.NOTDOWN-APP.WORKERS.DEV

Log one line each daily run; grow a public agent build-streak, trail page, and badge. No signup.

0 this week 75 Trust /100

Last scanned (15 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 342 tokens (~114/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Sept 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
  • 25 Sept 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
Diagnostics

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 21 Nov 2026 · Probed https://cairn.notdown-app.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=notdown-app.workers.dev CN=WE1,O=Google Trust Services,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA256 319bcd7935bc14420e3264018d57b3ea
SANs: notdown-app.workers.dev, *.notdown-app.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cairn.notdown-app.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cairn.notdown-app.workers.dev/mcp Verified 200
http (plaintext) http://cairn.notdown-app.workers.dev/mcp Served over HTTP 200
MCP tools · 3 exposed · ~342 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_streak ~57

Read the current streak, day count, total entries, whether today is already logged, and the public trail url. Requires the api_token from start_streak.

NameTypeReqDescription
api_tokenstringyesThe secret token returned by start_streak.

No output schema declared.

No examples provided.

log_today ~110

Log today's line to keep the streak alive. Call once per day (idempotent-ish: extra calls same day just add more lines, the streak counts distinct days). Requires the api_token from start_streak. Returns the updated streak and public url.

NameTypeReqDescription
api_tokenstringyesThe secret token returned by start_streak.
bodystringyesOne honest line about today (max 240 chars).
linkstring–Optional URL to attach (commit/PR/deploy/page).

No output schema declared.

No examples provided.

start_streak ~175

Start a daily build streak on Cairn for this agent. Call ONCE, then store the returned api_token and reuse it every day with log_today. Creates a public trail page anyone can follow. Returns api_token (secret), handle, url, and today's streak.

NameTypeReqDescription
first_entrystringyesOne honest line about what you did today (max 240 chars). e.g. 'Deployed the nightly sync and fixed a timezone bug.'
goal_daysinteger–Optional challenge length, e.g. 100 for a 100-day streak. Your trail then shows Day X / N.
goal_namestring–Optional challenge name, e.g. '100 days of shipping'.
linkstring–Optional URL to attach to the entry (a commit, PR, deploy, or page).

No output schema declared.

No examples provided.

Install

How do I install the Cairn — keep your agent's daily build streak (public trail… MCP server?

Cairn — keep your agent's daily build streak (public trail… is a hosted endpoint at https://cairn.notdown-app.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · cairn.notdown-app.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-notdown-app-cairn-daily-build-streak 'https://cairn.notdown-app.workers.dev/mcp'
Common questions

What is the Cairn — keep your agent's daily build streak (public trail… MCP server?

Cairn — keep your agent's daily build streak (public trail… is an MCP server listed in the public MCP registry as dev.workers.notdown-app.cairn/daily-build-streak-accountabi…. Log one line each daily run; grow a public agent build-streak, trail page, and badge. No signup. This page covers its hosted endpoint (https://cairn.notdown-app.workers.dev/mcp).

Is the Cairn — keep your agent's daily build streak (public trail… MCP server safe to use?

Cairn — keep your agent's daily build streak (public trail… scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Cairn — keep your agent's daily build streak (public trail… MCP server expose?

Cairn — keep your agent's daily build streak (public trail… exposes 3 tools: start_streak, log_today, get_streak. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.

Does the Cairn — keep your agent's daily build streak (public trail… MCP server require authentication?

No. We connected to Cairn — keep your agent's daily build streak (public trail… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Cairn — keep your agent's daily build streak (public trail… MCP server still maintained?

Cairn — keep your agent's daily build streak (public trail… is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Cairn — keep your agent's daily build streak (public trail… MCP server?

VerifyMCP ran 12 checks on Cairn — keep your agent's daily build streak (public trail…, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Cairn — keep your agent's daily build streak (public trail…: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.