The Durability Curve MCP server
com.durabilitycurve/archivedurabilitycurve.comstreamable-httpv0.5.0Scanned
Checks whether a coding agent's guard settings hold, against measured runs. Also essays and ledgers.
8 tools: 1 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- 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 The Durability Curve MCP server can do
The The Durability Curve MCP server is published by durabilitycurve.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (1 tool: check_agent_setup), but cannot delete data. 7 tools only read.
None of its tools reads private data, brings in text other people write, or sends data 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, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 0.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.
8 tools
Changes things 1Claude Code: ask
check_agent_setupCheck whether a coding agent's own guard settings hold, against runs the Durability Curve measured with its paid kits: Claude Code permission rules (which of 30 spellings of deleti…No 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.
Description, as the server wrote it Check whether a coding agent's own guard settings hold, against runs the Durability Curve measured with its paid kits: Claude Code permission rules (which of 30 spellings of deleting a remote branch, force-pushing or pushing to main they let through), sandbox and bypass settings, prompt-injection exposure (WebFetch, shell network access), hook wiring and exit codes, and skill frontmatter; Cursor CLI cli.json rules; Codex config.toml sandbox mode. Send the files' text, with every env block, token, header and key removed. Returns findings, most severe first, each with what it is based on, the measured run (tool, version, date, setup, result) and the kit that tests it on this machine. Free: the counts, the first finding in full and the titles of the rest. Paid: every finding with its fix and the configuration that held. The guard check reads only the text it is sent and runs nothing. Each finding says whether it was predicted from the user's rules, read from their config or taken from the docs, and names the measured run behind it. It is not a security audit, and no finding does not mean a guard holds: only running the kit on the machine shows that.
Annotations the server declares
- title: Check a coding agent's guard settings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 7Show 7 read-only tools
get_ai_modelsGet The Durability Curve's record of AI model releases from ten labs (OpenAI, Anthropic, Google, DeepSeek, Meta, xAI, Mistral, Alibaba, Moonshot, Zhipu): when each model came out, …No findings
Why it is in this group
- The name "get_ai_models" says "get": a word for reading.
Description, as the server wrote it Get The Durability Curve's record of AI model releases from ten labs (OpenAI, Anthropic, Google, DeepSeek, Meta, xAI, Mistral, Alibaba, Moonshot, Zhipu): when each model came out, with the lab's own announcement as source; for models with a page, the API list prices read at the lab's pricing page on a stated day; for the frontier launches the Access Gap tracks, when ordinary people could first use it, in the app, on the cheapest paid plan and on the free plan, each with its source; and each lab's flagship price and free-plan answer. Search by model or lab name, or filter by lab, release date, frontier status or free-plan access. The record runs to data_through; a newer release is not in it yet. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.
Annotations the server declares
- title: Get AI model facts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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. Filter by claim ids or status, or ask for compact rows. 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 one Durability Curve essay: by default its full public text as markdown, with its title, dates, canonical field, access, length, sections, tools and a link to its claim ledger …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 one Durability Curve essay: by default its full public text as markdown, with its title, dates, canonical field, access, length, sections, tools and a link to its claim ledger when it has one. A long essay can be read in parts: part "outline" lists the sections with their opening lines, part "section" returns one, and part "meta" returns everything but the text. For a part-paid essay only the free part is public, and the text says where it stops. The canonical field is the address to cite. 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_kitList the Durability Curve's paid kits (each tests one guard on the user's own machine: permission rules, prompt injection, test locks, hooks, skills), or get one.No findings
Why it is in this group
- The name "get_kit" says "get": a word for reading.
Description, as the server wrote it List the Durability Curve's paid kits (each tests one guard on the user's own machine: permission rules, prompt injection, test locks, hooks, skills), or get one. For a paid subscriber, a kit comes with its download address, its sha256 and the steps for you to run it, which start by asking the user. Free: what each kit tests, what it needs and the guide it belongs to.
Annotations the server declares
- title: Get a kit
- 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. Filter by status, ID, issue, resolution date or printed confidence. The wording is exactly as printed and never changes after publication. outcome is null until a call resolves. counts describe the calls returned; record describes every call. 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
searchSearch or list the public archive of The Durability Curve: essays on which kinds of work keep their value as AI gets cheaper, the checked claims in each essay's claim ledger, the d…No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Search or list the public archive of The Durability Curve: essays on which kinds of work keep their value as AI gets cheaper, the checked claims in each essay's claim ledger, the dated calls printed in The Durability Curve Weekly, the five laws and two derived principles the essays are tested against, the free tools, and AI model releases. With a query, returns ranked matches, each with its kind (essay, claim, call, law, tool or model), a snippet and a URL (canonical for essay citations); "title_matched" says whether any essay title contains every word of the query, and "none_found" is true when nothing matches enough of the query (the nearest misses are then under "closest", not "results"). With an empty query, lists newest first, filtered by kind, series, has_ledger or access, and "total" counts every match. Read a match in full with get_essay, get_claim_ledger, get_weekly_calls or get_ai_models. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.
Annotations the server declares
- title: Search The Durability Curve
- 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 Nov 20, 2026, 18:37 UTC, unchanged since Nov 20, 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://mcp.durabilitycurve.com/mcp/c/registry: tools/list returned 8 tools to an anonymous client, including check_agent_setup (write)
Posture changes
- Nov 20, 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.
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Tools2 added.+2 addedView diff
- Added:check_agent_setupChanges things
- Added:get_kitOnly reads
Tools2 changed.~2 changedView diff
- Changed:get_essayOnly readsdescription
- Changed:related_toOnly readsdescription
Tools2 added, 4 changed.+2 added~4 changedView diff
- Added:get_ai_modelsOnly reads
- Added:related_toOnly reads
- Changed:get_claim_ledgerOnly readsdescriptioninputSchema
- Changed:get_essayOnly readsdescriptioninputSchema
- Changed:get_weekly_callsOnly readsdescriptioninputSchema
- Changed:searchOnly readsdescriptioninputSchema
Install
Pinned to version 0.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http archive https://mcp.durabilitycurve.com/mcp/c/registryclaude mcp add --transport http archive https://mcp.durabilitycurve.com/mcp/c/registryRun 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__archive__search",
"mcp__archive__get_essay",
"mcp__archive__get_claim_ledger",
"mcp__archive__get_weekly_calls",
"mcp__archive__get_ai_models",
"mcp__archive__related_to",
"mcp__archive__get_kit"
],
"ask": [
"mcp__archive__check_agent_setup"
],
"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.
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/com.durabilitycurve/archive/verify?hash=0512806389d3666a2fde0e857a4aa342db0cba33272d7bb92736525c3f0b3630" | jq -e '.changed == false'Pinned hash 0512806389d3, from Nov 15, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.durabilitycurve/archive/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.durabilitycurve/archive)Source: MCP Registry. Synced Nov 15, 2026, 21:17 UTC.
The Durability Curve MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the The Durability Curve MCP server safe?
- No scan can promise that. What its definitions show: 8 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 The Durability Curve MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the The Durability Curve 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 The Durability Curve MCP server have?
- 8 tools: 1 write, 7 read. check_agent_setup, search, get_essay, get_claim_ledger, get_weekly_calls, get_ai_models, related_to and get_kit.
Does the The Durability Curve MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the The Durability Curve MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the The Durability Curve MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.