Connect-MCP

io.github.worklore/worklore

io.github.worklore/worklore · v0.7.1

Search worklore stories and x-ray any skill or story capability tier (T0-T4) before you run it.

MCPremoteno credentialsDocuments & PDF

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 8 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 80/100

What it does: 8 tools · 4 read, 4 write (incl. delete/pay) · Documents & PDF, Tasks & projects

Test call check_capability: failed — tool error: provide 'text' or 'url' (1,103 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: 0
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://worklore.dev/mcp

Tools

8 tools listed at last check
  • check_capability 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 h
  • get_story 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
  • search_stories Search worklore stories by keyword across title, summary, tags and stack. Returns matches with their capability tier.
  • suggest_for_project 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.
  • report_reproduction 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 perso
  • report_check 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, d
  • publish_story 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 in
  • edit_story 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` (f

Badge

Connect-MCP badge for io.github.worklore/worklore

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.worklore/worklore.svg)](https://clawy.uk/mcp/s/io.github.worklore/worklore)

Repository