MCP server exposing 4 tools for edge-case-museum.
This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.
POST https://gateway.pipeworx.io/edge-case-museum/mcp
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/list"}edge_cases_find — 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.edge_case_get — 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.edge_cases_browse — 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.edge_cases_test_file — 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.Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/edge-case-museum/
Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io