The Durability Curve
REMOTE · MCP.DURABILITYCURVE.COM
Essays, claim ledgers, weekly calls and laws, plus AI model release dates, prices and free plans.
Available components
Last scanned (11 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2867 tokens (~477/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- 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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 64
First indexed and scored.
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 5 Nov 2026 · Probed https://mcp.durabilitycurve.com/mcp/c/registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=durabilitycurve.com | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 49f9776258e52b2213ada9f2ad2ee2a3 |
| SANs: durabilitycurve.com, mcp.durabilitycurve.com, *.mcp.durabilitycurve.com | ||||||
| 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 mcp.durabilitycurve.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| durabilitycurve.com. | 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://mcp.durabilitycurve.com/mcp/c/registry | Verified | 200 | |
| http (plaintext) | http://mcp.durabilitycurve.com/mcp/c/registry | Inconclusive | 405 |
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 →
get_ai_models Get AI model facts ~442
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.
| Name | Type | Req | Description |
|---|---|---|---|
| frontier_only | boolean | – | true: only the frontier releases the /chart/ page plots (models anyone could use on the date given). |
| lab | string | – | Only this lab, by name or short name: OpenAI, Anthropic, Google, DeepSeek, Meta, xAI, Mistral, Alibaba, Moonshot or Zhipu. |
| limit | integer | – | How many models to return, 1 to 50. Default 10. |
| on_free_plan | boolean | – | true: only models whose lab's free consumer plan includes them; false: only models the free plan is recorded as not including. A model whose free-plan access is unknown, unnamed or restricted is on n… |
| query | string | – | A model or lab name in plain words, e.g. "Claude Opus 5.5", "GPT-6.1", "Gemini Flash" or "DeepSeek". Leave empty to list newest first. |
| released_after | string | – | YYYY-MM-DD. Only models released after this day. |
| released_before | string | – | YYYY-MM-DD. Only models released before this day. |
No output schema declared.
No examples provided.
get_claim_ledger Get a claim ledger ~275
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | true: each claim as id, status, claim, source, source_url, locator and date_read only (no quoted words or essay sentence). |
| ids | array | – | Only these claim IDs, e.g. ["SL1", "SL6"]. |
| slug | string | yes | The essay's site or Substack slug (case-insensitive), or its full durabilitycurve.com/blog/ or harryfloyd.substack.com/p/ URL. |
| status | string | – | Only claims with this status, by its key or label (e.g. "VERIFIED" or "Verified"); the response lists every status. |
No output schema declared.
No examples provided.
get_essay Get an essay ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| part | string | – | full (default): the whole public text. meta: dates, length, access, sections, tools and a content hash, without the text. outline: each section's heading, length and opening lines. section: one secti… |
| section | string | – | With part "section": the section's number from the outline (0 is the opening, before the first heading) or words from its heading. |
| slug | string | yes | The essay's site or Substack slug (case-insensitive), or its full durabilitycurve.com/blog/ or harryfloyd.substack.com/p/ URL. |
No output schema declared.
No examples provided.
get_weekly_calls Get the weekly calls ~283
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence_at_least | integer | – | Only calls printed at this confidence or higher, in percent, e.g. 60. |
| confidence_at_most | integer | – | Only calls printed at this confidence or lower, in percent, e.g. 30. |
| id | string | – | One call by its ID, e.g. "W02-5". |
| issue | integer | – | Only the calls printed in this issue of the Weekly. |
| resolves_after | string | – | YYYY-MM-DD. Only calls whose latest resolution date is after this day, earliest first. |
| resolves_before | string | – | YYYY-MM-DD. Only calls whose latest resolution date is before this day, earliest first. A call that resolves on an event "or" a date counts by that date. |
| status | string | – | open, resolved or all (default). |
No output schema declared.
No examples provided.
related_to Find what the archive says about a passage ~253
Compare a passage of text (an article, a headline, a draft, a question) with the whole archive and return what The Durability Curve has already published on it, grouped: essays, ledger claims, weekly calls, laws, free tools and AI models. Each result carries its URL and a share: how much of the passage's distinctive vocabulary it uses. possible_repeat is true when an essay (with its best ledger rows) shares at least 45% of that vocabulary: on the live archive it flagged 13 of 21 paragraphs taken from essays and none of 4 unrelated passages. It is a word-overlap signal, not a judgement: whether a topic is covered is in the essay itself. These tools retrieve The Durability Curve's public material. They do not certify that any claim is true.
| Name | Type | Req | Description |
|---|---|---|---|
| per_kind | integer | – | How many results of each kind, 1 to 10. Defaults: 5 essays, 5 claims, 3 calls, 2 laws, 2 tools, 3 models. |
| text | string | yes | The passage, headline, question or topic to compare with the archive, as text. Paste the words themselves: this tool does not open links. |
No output schema declared.
No examples provided.
search Search The Durability Curve ~481
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | Only essays a reader of durabilitycurve.com gets in full ("free") or only in part ("part paid": the rest is for paid subscribers). |
| has_ledger | boolean | – | true: only essays that have a claim ledger. false: only essays without one. |
| kind | string | – | Only this kind of result: essay, claim, call, law (the framework's laws and principles), tool (the free tools) or model (AI model releases). A list (empty query) defaults to essays. |
| limit | integer | – | How many results to return, 1 to 25. Default 5. |
| query | string | – | What to look for, in plain words, e.g. "agent reliability", "memory chip deposits", a call ID like "W02-5" or a model name like "Claude Opus 5.5". Leave empty to LIST instead (newest first), with the… |
| series | string | – | Only essays (and their claims) in this series, e.g. "The Blueprint". Case does not matter. |
| sort | string | – | relevance (default for a query) or newest. A list is always newest first. |
No output schema declared.
No examples provided.
How do I install the The Durability Curve MCP server?
The Durability Curve is a hosted endpoint at https://mcp.durabilitycurve.com/mcp/c/registry, 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 · mcp.durabilitycurve.com
claude mcp add --transport http com-durabilitycurve-archive 'https://mcp.durabilitycurve.com/mcp/c/registry'
What is the The Durability Curve MCP server?
The Durability Curve is an MCP server listed in the public MCP registry as com.durabilitycurve/archive. Essays, claim ledgers, weekly calls and laws, plus AI model release dates, prices and free plans. This page covers its hosted endpoint (https://mcp.durabilitycurve.com/mcp/c/registry).
Is the The Durability Curve MCP server safe to use?
The Durability Curve scores 70 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 The Durability Curve MCP server expose?
The Durability Curve exposes 6 tools: search, get_essay, get_claim_ledger, get_weekly_calls, get_ai_models, related_to. Their descriptions and schemas cost roughly 2,008 tokens of context every time the server is loaded.
Does the The Durability Curve MCP server require authentication?
No. We connected to The Durability Curve without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the The Durability Curve MCP server still maintained?
The Durability Curve is still listed as active in the MCP registry. We last reached this channel on 5 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 The Durability Curve MCP server?
VerifyMCP ran 12 checks on The Durability Curve, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about The Durability Curve: HTTPS. 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.