Skip to content

The Durability Curve

by durabilitycurve.com · remote · no sign-in to list tools · v0.3.0 · published by com.durabilitycurve

Search The Durability Curve: essays, claim ledgers, weekly calls, its five laws and free tools.

Read only
CompareRegistry entry

4 tools: 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http archive https://mcp.durabilitycurve.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Only reads 4Claude Code: allow
  • get_claim_ledgerGet the claim ledger for one essay: each load-bearing claim it makes, the source it was checked against, the quoted words, where in the source they appear, the date the source was …No findings

    Why it is in this group

    • The name "get_claim_ledger" says "get": a word for reading.
    Description, as the server wrote it
    Get the claim ledger for one essay: each load-bearing claim it makes, the source it was checked against, the quoted words, where in the source they appear, the date the source was read, and a status saying how the claim was checked. The response defines every status. Claims removed during checking are listed separately under "struck", with the reason; they are not claims the essay makes. Only some essays have a ledger: search results and get_essay link to one when it exists. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.

    Annotations the server declares

    • title: Get a claim ledger
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_essayGet the full public text of one Durability Curve essay as markdown.No findings

    Why it is in this group

    • The name "get_essay" says "get": a word for reading.
    Description, as the server wrote it
    Get the full public text of one Durability Curve essay as markdown. Its metadata carries the title, date and canonical field, and a link to the essay's claim ledger when it has one. For a paid essay only the free part is public, and the text says where it stops. When citing, link the canonical field in the response metadata. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.

    Annotations the server declares

    • title: Get an essay
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_weekly_callsGet the calls printed in The Durability Curve Weekly: dated, checkable predictions, each with the confidence printed at the time and the date or event it resolves on.No findings

    Why it is in this group

    • The name "get_weekly_calls" says "get": a word for reading.
    Description, as the server wrote it
    Get the calls printed in The Durability Curve Weekly: dated, checkable predictions, each with the confidence printed at the time and the date or event it resolves on. The wording is exactly as printed and never changes after publication. outcome is null until a call resolves. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.

    Annotations the server declares

    • title: Get the weekly calls
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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 Oct 22, 2026, 14:31 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
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
none
RFC 9728 protected resource metadata
none
Authorization servers
none
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Install

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

claude mcp add --transport http archive https://mcp.durabilitycurve.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__archive__search",
      "mcp__archive__get_essay",
      "mcp__archive__get_claim_ledger",
      "mcp__archive__get_weekly_calls"
    ],
    "ask": [],
    "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 archive. Review it before you use it.