81trust / 100

Worklore

by worklore.dev in Search & web

MCP serverPassing, checked 3 h ago

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

https://worklore.dev/mcp
Tools
8
open to any client
Uptime
100%
last 30 days
Response time
511 ms
681 ms slowest 5%
Last check
Passed
3 h ago, next in 2 h

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "worklore": {
      "type": "http",
      "url": "https://worklore.dev/mcp"
    }
  }
}

8 tools

  • 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 /…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
3 h agoPassed200487 ms
13 h agoPassed200511 ms
23 h agoPassed200612 ms
32 h agoPassed200681 ms
42 h agoPassed200579 ms
Show 8 older checks
2 days agoPassed200472 ms
3 days agoPassed200478 ms
3 days agoPassed200505 ms
3 days agoPassed200585 ms
4 days agoPassed200555 ms
4 days agoPassed200473 ms
5 days agoPassed200518 ms
5 days agoPassed200506 ms