MCP server for WordPress Playground - enables AI agents to interact with the WordPress Playground website.
Curvelens is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search and read a public essay archive: essays, claim ledgers, weekly calls and AI model records.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user curvelens-mcp '--' npx -y @reneturcios/curvelens mcp
# 2 — ask your agent for something these tools do
# search, get_essay, get_claim_ledger and 3 more
Curvelens costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Curvelens as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user curvelens-mcp '--' npx -y @reneturcios/curvelens mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | 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 |
| limit | integer | no | How many results to return, 1 to 25. Default 5. |
| kind | string | no | 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. |
| series | string | no | Only essays (and their claims) in this series, e.g. "The Blueprint". Case does not matter. |
| has_ledger | boolean | no | true: only essays that have a claim ledger. false: only essays without one. |
| access | string | no | Only essays a reader of durabilitycurve.com gets in full ("free") or only in part ("part paid": the rest is for paid subscribers). |
| sort | string | no | relevance (default for a query) or newest. A list is always newest first. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The essay's site or Substack slug (case-insensitive), or its full durabilitycurve.com/blog/ or harryfloyd.substack.com/p/ URL. |
| part | string | no | 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 sectio |
| section | string | no | With part "section": the section's number from the outline (0 is the opening, before the first heading) or words from its heading. |
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,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The essay's site or Substack slug (case-insensitive), or its full durabilitycurve.com/blog/ or harryfloyd.substack.com/p/ URL. |
| ids | array | no | Only these claim IDs, e.g. ["SL1", "SL6"]. |
| status | string | no | Only claims with this status, by its key or label (e.g. "VERIFIED" or "Verified"); the response lists every status. |
| compact | boolean | no | true: each claim as id, status, claim, source, source_url, locator and date_read only (no quoted words or essay sentence). |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | open, resolved or all (default). |
| id | string | no | One call by its ID, e.g. "W02-5". |
| issue | integer | no | Only the calls printed in this issue of the Weekly. |
| resolves_before | string | no | 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. |
| resolves_after | string | no | YYYY-MM-DD. Only calls whose latest resolution date is after this day, earliest first. |
| confidence_at_most | integer | no | Only calls printed at this confidence or lower, in percent, e.g. 30. |
| confidence_at_least | integer | no | Only calls printed at this confidence or higher, in percent, e.g. 60. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | 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. |
| lab | string | no | Only this lab, by name or short name: OpenAI, Anthropic, Google, DeepSeek, Meta, xAI, Mistral, Alibaba, Moonshot or Zhipu. |
| released_after | string | no | YYYY-MM-DD. Only models released after this day. |
| released_before | string | no | YYYY-MM-DD. Only models released before this day. |
| frontier_only | boolean | no | true: only the frontier releases the /chart/ page plots (models anyone could use on the date given). |
| on_free_plan | boolean | no | 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 ne |
| limit | integer | no | How many models to return, 1 to 50. Default 10. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
| per_kind | integer | no | How many results of each kind, 1 to 10. Defaults: 5 essays, 5 claims, 3 calls, 2 laws, 2 tools, 3 models. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Curvelens or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Curvelens can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.