Edge Case Museum
NPM · @PIPEWORX/MCP-EDGE-CASE-MUSEUM · 2 COMPONENTS
Edge Case Museum MCP — 'Your code works. Except for these wonderfully terrible inputs.'
Available components
Last scanned (9 hours ago)
Scores higher than 76% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-edge-case-museum). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 633 tokens (~158/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-edge-case-museum@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-edge-case-museum |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-edge-case-museum/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617585554 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:67f76d42c1bea45a3785d3185a3b4ba1bc92c8e08620a4328440281ded467833824572f901700f7e75a79d717d6bbd522ef8f374b8d73106da61da258 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
edge_case_get ~108
Edge Case Museum: one exhibit in full by id (from edge_cases_find or edge_cases_browse): the assumption it breaks, the exact input, what goes wrong and why, every repro (executed Python/Node.js repros with their captured output and runtime version; other stacks labelled documented with a source), the fix, related exhibits, cited sources and test inputs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Exhibit id, e.g. "nfc-nfd-same-name-two-accounts". |
No output schema declared.
No examples provided.
edge_cases_browse ~117
Edge Case Museum: browse the collection. With no arguments, lists the categories (unicode, datetime, float-money, sorting, filenames, parsing, integers, names-addresses) with counts and their most common tags. With category or tag, lists the exhibits in it: id, title, the assumption each breaks, tags and which languages have executed repros.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category to list. |
| tag | string | – | Tag to list, e.g. "username", "csv", "timezone", "money". |
No output schema declared.
No examples provided.
edge_cases_find ~228
Edge Case Museum: describe what you are implementing in plain words ("username uniqueness", "parse a CSV upload", "store and add up money amounts", "schedule a reminder in the user's timezone", "sort customer names") and get the surprising inputs that break that kind of code. Each exhibit gives the assumption it breaks, the exact input with escapes, what goes wrong, the fix, and a repro in your language whose expected_output was captured by actually running it (Python 3 or Node.js). Returns a short form plus refine_tags; use edge_case_get for the full exhibit or edge_cases_test_file for a runnable test file. Curated collection, keyword and tag matching, no upstream calls.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | What you are implementing, in plain words, e.g. "username uniqueness" or "parse a CSV upload". |
| language | string | – | Language of the repro to include with each exhibit. "javascript" means Node.js. Omit for the first available repro. |
| limit | number | – | Maximum exhibits to return (default 8, max 25). |
No output schema declared.
No examples provided.
edge_cases_test_file ~124
Edge Case Museum: one runnable test file (pytest for python, node:test for javascript) bundling the inputs from the exhibits relevant to what you are implementing, as parametrized cases you point at your own function. The file runs as generated against a stub, with TODO marks where your function goes; each case names its exhibit id so edge_case_get can explain a failure.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | What you are implementing, e.g. "parse a CSV upload". |
| language | string | yes | python produces a pytest file; javascript produces a node:test file. |
No output schema declared.
No examples provided.
How do I install the Edge Case Museum MCP server?
Edge Case Museum runs locally as an npm package, launched with npx -y @pipeworx/mcp-edge-case-museum. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-edge-case-museum
claude mcp add pipeworx-io-edge-case-museum -- npx -y @pipeworx/mcp-edge-case-museum
What is the Edge Case Museum MCP server?
Edge Case Museum is an MCP server listed in the public MCP registry as io.github.pipeworx-io/edge-case-museum. Edge Case Museum MCP, 'Your code works. Except for these wonderfully terrible inputs.'. This page covers its npm package (@pipeworx/mcp-edge-case-museum).
Is the Edge Case Museum MCP server safe to use?
Edge Case Museum scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Edge Case Museum MCP server expose?
Edge Case Museum exposes 4 tools: edge_cases_find, edge_case_get, edge_cases_browse, edge_cases_test_file. Their descriptions and schemas cost roughly 577 tokens of context every time the server is loaded.
Is the Edge Case Museum MCP server still maintained?
Edge Case Museum is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Edge Case Museum MCP server under?
Edge Case Museum declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.