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.

io.github.CloudCorpRecords/curvelens

OCI · GHCR.IO/CLOUDCORPRECORDS/CURVELENS · 2 COMPONENTS

Search and read a public essay archive: essays, claim ledgers, weekly calls and AI model records.

40 Trust /100

Last scanned (16 hours ago)

Scores higher than 36% of OCI servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2008 tokens (~334/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 Management13
  • Stability observed for 4 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 6 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

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

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 38

    First indexed and scored.

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 · Analysed oci/ghcr.io/cloudcorprecords/curvelens@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 6 exposed · ~2,008 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_ai_models ~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.

NameTypeReqDescription
frontier_onlyboolean–true: only the frontier releases the /chart/ page plots (models anyone could use on the date given).
labstring–Only this lab, by name or short name: OpenAI, Anthropic, Google, DeepSeek, Meta, xAI, Mistral, Alibaba, Moonshot or Zhipu.
limitinteger–How many models to return, 1 to 50. Default 10.
on_free_planboolean–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…
querystring–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_afterstring–YYYY-MM-DD. Only models released after this day.
released_beforestring–YYYY-MM-DD. Only models released before this day.

No output schema declared.

No examples provided.

get_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.

NameTypeReqDescription
compactboolean–true: each claim as id, status, claim, source, source_url, locator and date_read only (no quoted words or essay sentence).
idsarray–Only these claim IDs, e.g. ["SL1", "SL6"].
slugstringyesThe essay's site or Substack slug (case-insensitive), or its full durabilitycurve.com/blog/ or harryfloyd.substack.com/p/ URL.
statusstring–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 ~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.

NameTypeReqDescription
partstring–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…
sectionstring–With part "section": the section's number from the outline (0 is the opening, before the first heading) or words from its heading.
slugstringyesThe 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 ~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.

NameTypeReqDescription
confidence_at_leastinteger–Only calls printed at this confidence or higher, in percent, e.g. 60.
confidence_at_mostinteger–Only calls printed at this confidence or lower, in percent, e.g. 30.
idstring–One call by its ID, e.g. "W02-5".
issueinteger–Only the calls printed in this issue of the Weekly.
resolves_afterstring–YYYY-MM-DD. Only calls whose latest resolution date is after this day, earliest first.
resolves_beforestring–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.
statusstring–open, resolved or all (default).

No output schema declared.

No examples provided.

related_to ~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.

NameTypeReqDescription
per_kindinteger–How many results of each kind, 1 to 10. Defaults: 5 essays, 5 claims, 3 calls, 2 laws, 2 tools, 3 models.
textstringyesThe 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 ~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.

NameTypeReqDescription
accessstring–Only essays a reader of durabilitycurve.com gets in full ("free") or only in part ("part paid": the rest is for paid subscribers).
has_ledgerboolean–true: only essays that have a claim ledger. false: only essays without one.
kindstring–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.
limitinteger–How many results to return, 1 to 25. Default 5.
querystring–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…
seriesstring–Only essays (and their claims) in this series, e.g. "The Blueprint". Case does not matter.
sortstring–relevance (default for a query) or newest. A list is always newest first.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/curvelens MCP server?

io.github.CloudCorpRecords/curvelens runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/curvelens:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cloudcorprecords/curvelens

# add to Claude Code
claude mcp add cloudcorprecords-curvelens -- docker run --rm -i ghcr.io/cloudcorprecords/curvelens:0.1.0 mcp
Common questions

What is the io.github.CloudCorpRecords/curvelens MCP server?

io.github.CloudCorpRecords/curvelens is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/curvelens. Search and read a public essay archive: essays, claim ledgers, weekly calls and AI model records. This page covers its container image (ghcr.io/cloudcorprecords/curvelens).

Is the io.github.CloudCorpRecords/curvelens MCP server safe to use?

io.github.CloudCorpRecords/curvelens scores 40 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 io.github.CloudCorpRecords/curvelens MCP server expose?

io.github.CloudCorpRecords/curvelens 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.

Is the io.github.CloudCorpRecords/curvelens MCP server still maintained?

io.github.CloudCorpRecords/curvelens 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 licence is the io.github.CloudCorpRecords/curvelens MCP server under?

io.github.CloudCorpRecords/curvelens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.CloudCorpRecords/curvelens MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/curvelens, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/curvelens: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.