Then Apply
THEN APPLY // developer tools
npm provenance · SLSA attestation provenance verified (3 of 4): web-to-markdown openapi-to-mcp mcp-shield-proxy

Then Apply

Systems that chain, not stall.

Developer infrastructure and tools, built edge-first. No servers to patch, no queues to babysit — each piece does one job and hands off cleanly to the next.

Cloudflare Workers
Edge-first, no servers
269 tests passing
web-to-markdown · openapi-to-mcp · mcp-shield-proxy
TypeScript
Strict, throughout

See it in action

Fixed input/output pairs showing what each tool actually produces.

# Building Next-Gen AI Microservices

Model Context Protocol allows seamless tool execution.

```bash
npx @karlangas12/web-to-markdown https://example.com
```

Static example — not a live API call.

SUITE OVERVIEW

Four Micro-Tools

Built for modularity — deploy each one standalone, or combine them into your AI toolchain.

Edge API · MIT

web-to-markdown

Converts any web page or raw HTML into clean, dense, LLM-ready Markdown — strips nav, ads and scripts. Runs as a CLI, a library, or a Cloudflare Workers API.

npx @karlangas12/web-to-markdown

From €5/mo · 500 free requests

Local firewall · Free · MIT

mcp-shield-proxy

A local firewall for MCP servers. Blocks destructive tool calls and masks secrets like AWS keys and JWTs before they leave your machine. Works with Claude Desktop, Cursor and Claude Code.

npx mcp-shield-proxy
CLI generator · Free · MIT

openapi-to-mcp

Turns an OpenAPI/Swagger 3.x spec into a working MCP server, with request schemas generated straight from the spec via Zod.

npx @karlangas12/openapi-to-mcp
OAuth wrapper · Free · MIT

mcp-auth-kit

Wraps an MCP client's OAuth provider and fixes four token-lifecycle bugs still open in real clients: silent expiry with no refresh, a valid refresh_token that never gets used, registration that fails without retry, and a malformed resource param that breaks Entra ID. Auto-refresh with a TTL fallback, retried registration, and actionable errors instead of silent failure.

Open issues behind it: claude-code#26281, #52871, codex#13200, #17265

npm install @karlangas12/mcp-auth-kit

Free in v1 · MIT · no account · ESM-only

SUPPLY CHAIN

How we audit the code

The same policy applies to web-to-markdown, openapi-to-mcp and mcp-shield-proxy. None of it is opt-in per project, and none of it is a claim you have to take on trust — each item below is verifiable from outside this site.

Static analysis on every push

Each of those three runs CodeQL alongside its test suite and a strict TypeScript typecheck. A failing run blocks the release — publishing is a separate workflow that only fires on a tagged version.

Signed provenance, not a promise

Those three packages publish with npm provenance (--provenance, SLSA attestation via GitHub OIDC). npm ties each published tarball to the exact commit and workflow run that produced it, so you can check what you installed was built from the source you're reading.

Verify any of it on the package pages linked at the top of this page — the attestation lives on npm, not here.

One-Line Integration

Call via standard HTTP `cURL`, integrate into your Node/Python codebase, or add to `claude_desktop_config.json`.

cURL / API Example
# Fetch clean Markdown via API
curl -X POST https://web-to-markdown.karlangas12.workers.dev/v1/convert \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com", "options": {"extract_metadata": true}}'
                
Copied to clipboard!