MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Worklore 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.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search worklore stories and x-ray any skill or story capability tier (T0-T4) before you run it.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http worklore-mcp https://worklore.dev/mcp
# 2 — ask your agent for something these tools do
# check_capability, get_story, search_stories and 5 more
Worklore costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WOAll 1 server
worklore1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http worklore-mcp https://worklore.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 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.
Disclose what an agent Skill or worklore story CAN DO before you run it: a capability tier T0-T4 bound to a content sha256, with findings that carry file:line evidence, PLUS a separate list of behavioral red flags (prompt-injection / deception / exfiltration-intent / safety-bypass phrasings) for a human to review. This is blast-radius disclosure and triage, never a 'safe' verdict. Pass the raw `te
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | The skill/story text to scan. |
| url | string | no | A URL to fetch and scan. |
Fetch one worklore story by slug — its full markdown (narrative + the 'Reproduce this' contract your agent would run) WITH its capability disclosure attached (tier + findings), so you see what it can do before applying it. Read the capability first; run check_capability on the live artifacts before executing. After you apply the story to the user's task, call report_reproduction with an honest res
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The story slug (from search_stories / a worklore URL). |
Search worklore stories by keyword across title, summary, tags and stack. Returns matches with their capability tier.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Keywords (space-separated; all must match). |
Given a short description of the current project (stack, what you're building, recent problems), suggest up to 3 worklore stories worth reproducing here, with why each fits and its tier.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context | string | yes | Project context: stack, goal, recent TODOs/problems. |
Call this right after you apply a worklore story's steps to the user's own task, to record the reproduction (attributed to the signed-in account). Use an honest result: 'worked', 'partial' (you produced the output but it isn't verified yet), or 'failed' — all are useful. One counted report per person per story; repeats are acknowledged, not doubled. Never report a story you did not apply.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The story slug you reproduced. |
| result | string | yes | How it honestly went. |
| note | string | no | Optional short note (max 500 chars). |
Record the result of a story's read-only 'Check if this applies to you' section, run in the user's own project (attributed to the signed-in account). Run ONLY that check — change nothing, apply no fix. First decide whether it applies at all: if the project does not match the check's preconditions, do NOT call this — 'not applicable' is never recorded. Otherwise report 'has_problem' or 'no_problem'
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The story slug whose check you ran. |
| result | string | yes | What the check found in the user's project. |
| note | string | no | Optional short note: the evidence (max 300 chars). |
Publish a NEW worklore story as the signed-in account. worklore stories are PUBLIC and honest, so before you call this you MUST show the human the complete draft — the title, the first-person narrative, and the 'Reproduce this' contract — and get their EXPLICIT approval. Never publish on your own initiative and never invent details. Provide the full story as markdown (frontmatter with title/date
| Parameter | Type | Required | Notes |
|---|---|---|---|
| markdown | string | no | The complete story markdown (frontmatter + '# title' + narrative + '## Reproduce this' contract). Preferred. |
| title | string | no | Story title (used only if markdown is not given). |
| narrative | string | no | First-person narrative, ~150-400 words, honest (used if no markdown). |
| reproduce | string | no | The 'Reproduce this' contract body: prerequisites, inputs, ordered steps, verify. |
| tags | array | no | 3-6 lowercase kebab tags. |
| type | string | no | success (default), fail, or proposal — a proposal is work the author believes is right but cannot prove yet, published to get evidence or review rather than to claim a result. |
| stack | string | no | Optional: the ecosystem this story is about. |
| visibility | string | no | public (default) — anyone can read and reproduce it; private — only the author can, and it appears in no feed, search, badge or link. Ask the human which they want if the draft contains anything they |
Revise a worklore story the signed-in account PUBLISHED — only its author can edit it. Call get_story first, then show the human a before/after diff of your change and get their EXPLICIT approval before calling this; never edit on your own initiative. Send the COMPLETE revised story as markdown (frontmatter + '# title' + narrative + '## Reproduce this'), not a fragment. Keep the frontmatter `dat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The slug of the story to revise (one the signed-in account wrote). |
| markdown | string | yes | The complete revised story markdown, frontmatter included, with the original date unchanged. |
| kind | string | no | rephrase (default) — same claims, reworded; addition — new detail, nothing was wrong; correction — something was wrong (requires note, notifies reproducers). |
| note | string | no | One line on what changed (max 500 chars). Required for a correction: what was wrong. |
| source | string | no | Optional https URL crediting what prompted the revision (a comment, an issue, an article). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Worklore or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.7.1.
0.7.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Worklore can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.