worklore

endpoint

https://worklore.dev/mcp

protocol

streamable-http ·2025-06-18

authentication

bearer

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is worklore live?

Yes — it answered the hub's last check (checked 3m ago). It answered 98% of checks over the last 30 days.

Is worklore free to use?

Yes — the hub reached it with no key and no payment.

What tools does worklore have?

8 tools: get_story, check_capability, report_check, report_reproduction, publish_story, edit_story, suggest_for_project, search_stories.

Is worklore safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• search_stories reads open 14h ago

  Search worklore stories by keyword across title, summary, tags and stack. Returns matches with their capability tier.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Keywords (space-separated; all must match)."
      }
    }
  }

  arguments 9 lines copy
• get_story reads unknown 14h ago

  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 result to record it.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "The story slug (from search_stories / a worklore URL)."
      }
    }
  }

  arguments 12 lines copy
• check_capability reads unknown 14h ago

  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 `text`, or a `url` to fetch and scan (e.g. a worklore story .md). `text` needs no sign-in; a `url` makes the server fetch it for you, so it needs a signed-in session.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "properties": {
      "url": {
        "type": "string",
        "description": "A URL to fetch and scan."
      },
      "text": {
        "type": "string",
        "description": "The skill/story text to scan."
      }
    }
  }

  arguments 13 lines copy
• report_check unknown never probed

  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', honestly. One counted result per person per story; a later report replaces the earlier one. Only stories whose get_story result has has_check: true can be checked.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "required": [
      "slug",
      "result"
    ],
    "properties": {
      "note": {
        "type": "string",
        "description": "Optional short note: the evidence (max 300 chars)."
      },
      "slug": {
        "type": "string",
        "description": "The story slug whose check you ran."
      },
      "result": {
        "enum": [
          "has_problem",
          "no_problem"
        ],
        "type": "string",
        "description": "What the check found in the user's project."
      }
    }
  }

  arguments 25 lines copy
• report_reproduction changes data unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526

  {
    "type": "object",
    "required": [
      "slug",
      "result"
    ],
    "properties": {
      "note": {
        "type": "string",
        "description": "Optional short note (max 500 chars)."
      },
      "slug": {
        "type": "string",
        "description": "The story slug you reproduced."
      },
      "result": {
        "enum": [
          "worked",
          "partial",
          "failed"
        ],
        "type": "string",
        "description": "How it honestly went."
      }
    }
  }

  arguments 26 lines copy
• publish_story changes data unknown never probed

  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/tags/type/reproducible, then '# title', the narrative, then '## Reproduce this' with prerequisites/inputs/steps/verify) — call get_story on an existing story first to match the format — OR provide the structured fields title + narrative (+ reproduce, tags, type, stack) and the server assembles it. SANITIZE: no secrets, employer internals, client names, or private URLs. Returns the live URL and capability tier.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849

  {
    "type": "object",
    "properties": {
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "3-6 lowercase kebab tags."
      },
      "type": {
        "enum": [
          "success",
          "fail",
          "proposal"
        ],
        "type": "string",
        "description": "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": {
        "type": "string",
        "description": "Optional: the ecosystem this story is about."
      },
      "title": {
        "type": "string",
        "description": "Story title (used only if `markdown` is not given)."
      },
      "markdown": {
        "type": "string",
        "description": "The complete story markdown (frontmatter + '# title' + narrative + '## Reproduce this' contract). Preferred."
      },
      "narrative": {
        "type": "string",
        "description": "First-person narrative, ~150-400 words, honest (used if no `markdown`)."
      },
      "reproduce": {
        "type": "string",
        "description": "The 'Reproduce this' contract body: prerequisites, inputs, ordered steps, verify."
      },
      "visibility": {
        "enum": [
          "public",
          "private"
        ],
        "type": "string",
        "description": "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 may not want public."
      }
    }
  }

  arguments 49 lines copy
• edit_story changes data unknown never probed

  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 `date` exactly as it is: it records when the work happened, and a revision never moves it. Say what kind of edit this is: 'rephrase' (same claims, better wording), 'addition' (new detail, nothing was wrong), or 'correction' (something in the story was WRONG — a step, a claim, a result). If anything was wrong, it is a correction: never hide a correction as a rephrase. A correction requires a one-line `note` saying what was wrong, and notifies everyone who reported reproducing the story. `source` optionally credits what prompted the revision (an https URL). The new text REPLACES the old (worklore keeps no copy of earlier text), while a record of this revision — when, what kind, the note — is appended to the story's public history.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435

  {
    "type": "object",
    "required": [
      "slug",
      "markdown"
    ],
    "properties": {
      "kind": {
        "enum": [
          "rephrase",
          "addition",
          "correction"
        ],
        "type": "string",
        "default": "rephrase",
        "description": "rephrase (default) — same claims, reworded; addition — new detail, nothing was wrong; correction — something was wrong (requires `note`, notifies reproducers)."
      },
      "note": {
        "type": "string",
        "description": "One line on what changed (max 500 chars). Required for a correction: what was wrong."
      },
      "slug": {
        "type": "string",
        "description": "The slug of the story to revise (one the signed-in account wrote)."
      },
      "source": {
        "type": "string",
        "description": "Optional https URL crediting what prompted the revision (a comment, an issue, an article)."
      },
      "markdown": {
        "type": "string",
        "description": "The complete revised story markdown, frontmatter included, with the original `date` unchanged."
      }
    }
  }

  arguments 35 lines copy
• suggest_for_project reads unknown 11h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "context"
    ],
    "properties": {
      "context": {
        "type": "string",
        "description": "Project context: stack, goal, recent TODOs/problems."
      }
    }
  }

  arguments 12 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.