altfinance-mcp 0.3.0__tar.gz

altfinance_mcp-0.3.0/.gitignore

@@ -0,0 +1,133 @@
+# Environment variables
+.env
+.env.local
+.env.*
+*.csv
+*.json
+*.pkl
+env
+
+# Gmail Assistant tokens, logs, and reports
+Gmail_Assistant/token.json
+Gmail_Assistant/logs/
+Gmail_Assistant/reports/
+Gmail_Assistant/config/backups/
+
+# Windows reserved device names (created accidentally by 2>NUL in bash)
+NUL
+**/nul.ipynb
+
+# ---- Sensitive credentials and secrets ----
+# Private keys / certificates
+*.pem
+*.key
+*.p12
+*.pfx
+*.jks
+
+# Auth tokens and session cookies
+*token*.txt
+*.token
+*cookie*.txt
+.saleroom_cookie_header.txt
+
+# AWS credentials
+.aws/credentials
+aws_credentials*
+
+# Project-specific: Cartier deliverable (contains client-embedded AWS/API keys pending rotation)
+Cartier_Search_Engine/
+
+# Claude Code worktrees (may duplicate credentials)
+.claude/worktrees/
+
+# Virtualenv / caches / build artifacts
+.venv/
+venv/
+__pycache__/
+*.pyc
+*.pyo
+
+# Logs
+*.log
+Scheduled_Local_Tasks/Pipeline_Status_Logs/
+
+# Downloaded / temporary data
+downloaded_files/
+
+# Large binary tools bundled locally (not source)
+ffmpeg-master-latest-win64-gpl/
+
+# Downloaded media (scraping artifacts)
+**/youtube_videos/
+*.mp4
+*.mov
+*.webm
+
+# Large pipeline output / test fixtures (regenerated, not source)
+test_*.jsonl
+**/Pipeline_Output/*.jsonl
+**/Merged/*.jsonl
+
+# Gemini reclassification notebook outputs (large generated data)
+AI_Models/Gemini/1_gemini_output_watches_reclassify*.ipynb
+AI_Models/Gemini/2_gemini_merge_output_watches*.ipynb
+
+# Failed-log artifacts
+*.log.failed*
+
+# ---- Direct-vendor scraping (Bidpath, EasyLive, etc.) ----
+# Whitelist vendor configs that should be tracked (override global *.json rule)
+!Data Collection/vendor-configs/
+!Data Collection/vendor-configs/*.json
+
+# Whitelist small reference outputs (top-100 vendor list, discovery results, probe results)
+!Data Collection/vendor_top100.json
+!Data Collection/vendor_directory.json
+!Data Collection/bidpath_probe_results.json
+!Data Collection/step5_jewelry_targets_filtered.json
+
+# Block large local caches (regenerable from S3)
+Data Collection/_cache_*.json
+Data Collection/cross_platform_matches.json
+Data Collection/cross_platform_merge_manifest.json
+Data Collection/saleroom_split_manifest.json
+Data Collection/bonhams_enrichment_candidates*.json
+Data Collection/bonhams_enrichment_strict.json
+Data Collection/bonhams_enrichment_summary.json
+Data Collection/bonhams_enrichment_execution_summary.json
+Data Collection/bonhams_categories_enrichment_summary.json
+Data Collection/bonhams_jewelry_v2_summary.json
+Data Collection/bonhams_gwh_v2_summary.json
+Data Collection/enrichment_strategy_comparison.json
+Data Collection/step5_jewelry_targets.json
+Data Collection/saleroom_vendors_captured.txt
+Data Collection/cross_platform_matches.csv
+Data Collection/enrich_bonhams_*.sql
+
+# Auth files (already in .saleroom_cookie_header.txt rule above, but be explicit)
+Data Collection/.saleroom_cookie_header.txt
+Data Collection/.saleroom_user_agent.txt
+Data Collection/.saleroom_cookies.json
+Data Collection/Tajan/*_out.ipynb
+
+# Repeat-detection cache: keep only small artifacts; skip ALL the giant parquet datasets
+repeat_detection_cache/jewelry_lots.parquet
+repeat_detection_cache/jewelry_verified.parquet
+repeat_detection_cache/*.parquet
+
+# Barrett-Jackson raw API dump (large, regenerable from S3/API)
+Data Collection/Barrett-Jackson/bj_api_pre2023.jsonl
+
+# Branding storybook/Figma BUILD artifacts (~956MB of node_modules + storybook-static,
+# regenerable; the storybooks deploy to the altfinancedbstatuspage S3 bucket).
+# NOTE: Branding/AltFinance is intentionally NOT ignored — it's source (docs, email_system, covers).
+Branding/Bloomberg/
+Branding/BusinessInsider/
+Branding/AlphaSense/
+Branding/LoversByShan/
+Branding/Figma_Projects/
+Branding/JPMorgan/
+
+# Safety net: never track node_modules anywhere (a JPMorgan storybook leaked ~7.5k untracked files)
+**/node_modules/

altfinance_mcp-0.3.0/Community_Posts_Draft.md

@@ -0,0 +1,282 @@
+# Community Post Drafts — AltFinance Launch
+
+> These are draft posts for various communities. Adapt tone and length as needed before posting.
+> Remember the 90/10 rule: lead with value, not product.
+
+---
+
+## 1. r/ClaudeAI — MCP Server Announcement
+
+**Title:** I built an MCP server that gives Claude access to 990K luxury auction records (watches, handbags, jewelry)
+
+**Body:**
+
+I've been building a luxury asset data platform for a while now and just shipped an MCP server that lets Claude query auction results directly.
+
+**What it does:**
+
+Three tools — `list_tables`, `get_table_schema`, and `query_table`. Once connected, you can ask Claude things like:
+
+- "Find the top 10 most expensive Rolex Daytona watches sold since 2020"
+- "How many Hermes Birkin bags were sold at Christie's vs Sotheby's?"
+- "Show me diamond jewelry that sold for over $100K last year, sorted by price"
+
+Claude translates your natural language into structured queries against the API automatically. It handles filtering (11 operators including `like`, `in`, `is_null`), sorting, field selection, and pagination.
+
+**The data:**
+
+| Table | Records | Sources |
+|-------|---------|---------|
+| Watches | 390K+ | Christie's, Sotheby's, Phillips, Bonhams, and 100+ more |
+| Handbags | 120K+ | Same major houses + specialist auction houses |
+| Jewelry | 480K+ | Jewelry and gemstone auction results worldwide |
+
+Each record includes lot details, sale price, estimates, auction house, sale date, descriptions, and more (up to 122 fields for watches).
+
+**Setup (takes 2 minutes):**
+
+1. `pip install altfinance-mcp`
+2. Add to your Claude Desktop config (`%APPDATA%\Claude\claude_desktop_config.json` on Windows, `~/Library/Application Support/Claude/claude_desktop_config.json` on Mac):
+
+```json
+{
+  "mcpServers": {
+    "altfinance": {
+      "command": "altfinance-mcp",
+      "env": {
+        "ALTFINANCE_API_KEY": "your-api-key-here"
+      }
+    }
+  }
+}
+```
+
+3. Restart Claude Desktop.
+
+For Claude Code: `claude mcp add altfinance -- altfinance-mcp`
+
+**Getting an API key:**
+
+Sign up at altfndata.com. There's a free tier (1K rows/day) so you can try it out without committing.
+
+Happy to answer any questions about the data, setup, or how the MCP tools work under the hood. The server itself is a thin wrapper over our REST API using httpx — Claude does all the heavy lifting of translating your question into the right query.
+
+---
+
+## 2. r/datasets — Dataset Announcement
+
+**Title:** 990K luxury auction records — watches, handbags, and jewelry from 100+ auction houses (API access)
+
+**Body:**
+
+I've spent the last couple of years building a structured dataset of luxury goods auction results and wanted to share it with this community.
+
+**What's in the data:**
+
+| Category | Records | Fields | Key Columns |
+|----------|---------|--------|-------------|
+| Watches | 390K+ | 122 | brand, model, reference number, sale price (USD), estimate range, auction house, sale date, movement, case material, dial color, complications |
+| Handbags | 120K+ | 67 | brand, model, material, color, sale price (USD), estimates, auction house, sale date, condition |
+| Jewelry | 480K+ | 99 | item type, gemstone, carat weight, color, clarity, metal, sale price (USD), estimates, auction house, sale date |
+
+**Sources:** Christie's, Sotheby's, Phillips, Bonhams, Artcurial, Dorotheum, Heritage Auctions, and 100+ more worldwide. Data is collected from public auction results and standardized into a consistent schema.
+
+**Coverage:** Results going back 10+ years for major houses, with new results added regularly via automated pipelines.
+
+**How to access:**
+
+REST API at `api.altfndata.com`:
+
+```bash
+# List available tables
+curl -H "X-API-Key: YOUR_KEY" https://api.altfndata.com/v1/tables
+
+# Query watches
+curl -X POST -H "X-API-Key: YOUR_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"filters":[{"field":"brand","operator":"eq","value":"Rolex"}],"sort_field":"price_usd","sort_direction":"desc","limit":10}' \
+  https://api.altfndata.com/v1/tables/watches/query
+```
+
+Filter operators: `eq`, `neq`, `gt`, `gte`, `lt`, `lte`, `like`, `in`, `not_in`, `is_null`, `is_not_null`
+
+Also available as an MCP server for Claude Desktop/Code users: `pip install altfinance-mcp`
+
+**Free tier:** 1K rows/day, 10 requests/min — enough to explore the data and build prototypes.
+
+Sign up at altfndata.com.
+
+If there's interest, I could also share some analysis or summary statistics from the data (price distributions, top brands by volume, etc.).
+
+---
+
+## 3. r/algotrading — Alternative Data for Luxury Assets
+
+**Title:** Alternative data: 990K auction records for luxury watches, handbags, and jewelry — accessible via REST API
+
+**Body:**
+
+Posting this for the alt-data crowd here. I've built a structured dataset + API covering luxury goods auction results that might be interesting for anyone looking at alternative asset classes or non-traditional price signals.
+
+**The pitch in one sentence:** A REST API with 990K records from 100+ auction houses covering luxury watches (390K), handbags (120K), and jewelry (480K), with standardized schemas and programmatic access.
+
+**Why this might be useful for quant/systematic approaches:**
+
+- **Price discovery:** Luxury watches (Rolex, Patek Philippe, Audemars Piguet) are traded in a fragmented market. Auction data provides the closest thing to a consolidated tape.
+- **Macro correlation:** Luxury auction results can signal consumer sentiment and wealth effects before they show up in retail data.
+- **Cross-asset analysis:** The API covers three distinct luxury categories in a single schema, so you can analyze correlations across collectible asset classes.
+- **Comparable sales:** If you're building valuation models for fractional ownership platforms or luxury lending, this is your training data.
+
+**Technical details:**
+
+- **Endpoints:** `/v1/tables` (list), `/v1/tables/{name}/schema` (schema), `/v1/tables/{name}/query` (query via POST or GET)
+- **Filters:** 11 operators — `eq`, `neq`, `gt`, `gte`, `lt`, `lte`, `like`, `in`, `not_in`, `is_null`, `is_not_null`
+- **Sorting:** Any column, asc/desc
+- **Pagination:** limit + offset
+- **Auth:** API key in header (`X-API-Key`)
+- **Format:** JSON responses
+- **Rate limits:** Free tier at 10 req/min, 1K rows/day. Paid tiers go up to 60 req/min, 50K rows/day.
+
+**Sample query:**
+
+```python
+import requests
+
+headers = {"X-API-Key": "YOUR_KEY"}
+payload = {
+    "filters": [
+        {"field": "brand", "operator": "eq", "value": "Rolex"},
+        {"field": "price_usd", "operator": "gt", "value": 50000}
+    ],
+    "fields": ["brand", "model", "reference_number", "price_usd", "sale_date", "auction_house"],
+    "sort_field": "sale_date",
+    "sort_direction": "desc",
+    "limit": 100
+}
+resp = requests.post("https://api.altfndata.com/v1/tables/watches/query",
+                     json=payload, headers=headers)
+data = resp.json()
+```
+
+**What I'd love feedback on:**
+
+1. What additional fields or enrichments would make this useful for quantitative work? (currently up to 122 fields per record for watches)
+2. Would bulk export (CSV/Parquet) matter more than API access for backtesting?
+3. Any interest in a time-series endpoint (e.g., monthly average price by brand/model)?
+
+Sign up for a free key at altfndata.com. Also available as an MCP server for Claude users: `pip install altfinance-mcp`.
+
+---
+
+## 4. Hacker News — Show HN
+
+**Title:** Show HN: AltFinance – API for luxury auction data (990K records from 100+ auction houses)
+
+**Body:**
+
+Hi HN,
+
+I built an API that provides structured access to luxury goods auction results. It covers three categories — watches (390K records), handbags (120K), and jewelry (480K) — from Christie's, Sotheby's, Phillips, Bonhams, and 100+ other auction houses.
+
+The problem: luxury asset data is fragmented across hundreds of auction house websites, each with different formats, currencies, and naming conventions. There's no consolidated feed. If you're an investor, analyst, or builder working with luxury collectibles, you have to manually piece together data from dozens of sources.
+
+What I built:
+
+- A collection pipeline that scrapes, standardizes, and enriches auction results across 100+ houses
+- A REST API (FastAPI) with flexible querying — 11 filter operators, sorting, field selection, pagination
+- An MCP server so Claude Desktop users can query the data in natural language
+- Anti-scraping protections: rate limits, daily row quotas, per-table access control
+
+Tech stack: Python, FastAPI, AWS Athena (Apache Iceberg tables), S3, Fargate, Gemini for AI classification of lot categories.
+
+Free tier: 10 req/min, 1K rows/day.
+
+API docs: api.altfndata.com/docs
+MCP server: pip install altfinance-mcp
+Website: altfndata.com
+
+I'd appreciate feedback on the API design, pricing model, or the data itself. Happy to answer questions.
+
+---
+
+## 5. r/Watches — Data Insight Post (Value-First, No Hard Sell)
+
+**Title:** I analyzed 390K+ watch auction records — here are some patterns I found interesting
+
+**Body:**
+
+I've been building a database of luxury watch auction results as a side project for the past couple of years. The dataset now covers 390K+ lots from Christie's, Sotheby's, Phillips, Bonhams, and dozens of other houses going back 10+ years. Thought I'd share some of the patterns I've found interesting.
+
+**A few things the data shows:**
+
+**Brand concentration:** A small number of brands dominate the auction market by volume. Rolex, Patek Philippe, and Omega together account for a significant chunk of all watch lots. But when you look at average hammer price, the picture shifts — Patek and A. Lange & Sohne punch well above their volume share.
+
+**The "Phillips effect":** Phillips has carved out a distinct position. Their average sale price per lot trends notably higher than other houses, even for the same references. Whether that's selection bias (they curate aggressively) or buyer premium (their audience skews differently) is an interesting question.
+
+**Estimate accuracy:** Auction houses are surprisingly good at estimating — most lots sell within the estimate range. But the interesting cases are the outliers: lots that sell for 3-5x the high estimate. These tend to cluster around specific references and provenance features.
+
+**Seasonal patterns:** There are clear seasonal rhythms. The major houses run their marquee watch sales in May/June and November. Average prices in these months tend to run higher — likely because they save the best consignments for the flagship sales, not because of seasonal demand.
+
+**Material matters more than you'd think:** Steel sport watches from certain brands (you can probably guess which ones) have outperformed precious metal dress watches from the same brands over the last decade. The data is pretty clear on this one.
+
+I'm happy to dig into specific questions if anyone is curious about a particular brand, reference, or trend. This is one of those projects where the more I look at the data, the more questions come up.
+
+*[Note: no product link, no API mention. If asked "where can I access this data?" in comments, then naturally mention the API.]*
+
+---
+
+## 6. Product Hunt — Launch Day (Save for Phase 2)
+
+**Tagline:** The Bloomberg Terminal for luxury collectibles
+
+**Description:**
+
+AltFinance gives you structured API access to 990K+ auction results across luxury watches, handbags, and jewelry. Data from Christie's, Sotheby's, Phillips, Bonhams, and 100+ auction houses worldwide.
+
+Query by brand, model, price range, auction house, date, and 100+ other fields. Built for investment firms, analysts, collectors, and developers building in the luxury asset space.
+
+Also available as an MCP server for Claude — ask Claude questions about the luxury market in natural language.
+
+**Key Features:**
+- 390K+ watch records, 120K+ handbag records, 480K+ jewelry records
+- REST API with 11 filter operators
+- MCP server for Claude Desktop and Claude Code
+- Free tier available
+- Data updated regularly via automated pipelines
+
+---
+
+## 7. awesome-mcp-servers GitHub PR
+
+**Entry to add (in the appropriate category):**
+
+```markdown
+- [AltFinance MCP](https://pypi.org/project/altfinance-mcp/) - Query 990K+ luxury auction records (watches, handbags, jewelry) from 100+ auction houses. Provides tools to list tables, get schemas, and run filtered queries against the AltFinance API.
+```
+
+---
+
+## Posting Schedule
+
+| Week | Community | Post Type |
+|------|-----------|-----------|
+| 1 | r/ClaudeAI | MCP announcement (Post #1) |
+| 1 | PulseMCP + MCP Registry | Submit listing |
+| 1 | awesome-mcp-servers | Submit PR (Post #7) |
+| 2 | r/datasets | Dataset announcement (Post #2) |
+| 3 | r/algotrading | Alt data post (Post #3) |
+| 4 | Hacker News | Show HN (Post #4) |
+| 5 | r/Watches | Data insight post (Post #5) — no product link |
+| 6 | r/SideProject | Build story |
+| 8+ | PurseForum | Handbag trend analysis (organic) |
+| 8+ | WatchUSeek | Watch analysis (organic) |
+| Phase 2 | Product Hunt | Coordinated launch (Post #6) |
+
+## Tips Before Posting
+
+1. **Reddit accounts** — Make sure the posting account has established karma and history. New accounts get auto-filtered.
+2. **Don't cross-post** — Each community should get a unique, tailored post. Don't copy-paste.
+3. **Respond to every comment** — Engagement in the first 2 hours determines visibility on Reddit and HN.
+4. **Timing** — Post on Tuesday-Thursday mornings (US time) for best Reddit/HN visibility.
+5. **r/Watches post has no product link** — This is intentional. Only mention the API if someone asks in comments. This builds credibility and avoids removal.
+6. **HN formatting** — Keep the Show HN body concise. HN readers prefer brevity over marketing copy.

altfinance_mcp-0.3.0/DEPLOYMENT_PROGRESS.md

@@ -0,0 +1,108 @@
+# AltFinance MCP & API — Deployment Progress
+
+**Date**: 2026-03-03
+**Status**: Infrastructure code complete, awaiting tooling install for deployment
+
+---
+
+## What Was Done
+
+### Infrastructure Code (all files written and ready)
+
+| File | Purpose |
+|------|---------|
+| `infra/app.py` | CDK entry point — instantiates the stack |
+| `infra/cdk.json` | CDK config |
+| `infra/requirements.txt` | `aws-cdk-lib` + `constructs` |
+| `infra/stacks/__init__.py` | Package init |
+| `infra/stacks/api_stack.py` | Main CDK stack — VPC, ECR, ECS Fargate, ALB (HTTPS), Route 53, IAM (least-privilege Athena/Glue/S3), CloudWatch logs |
+| `infra/scripts/deploy.py` | Docker build + ECR push + ECS force-redeploy (uses boto3 since AWS CLI isn't on PATH) |
+| `infra/scripts/provision_key.py` | Generate API keys per tier (free/standard/premium), auto-add to `api_keys.json`, prints Claude Desktop config snippet |
+| `infra/scripts/publish_mcp.py` | Rebuild + publish `altfinance-mcp` to PyPI via twine |
+| `API_Management/.dockerignore` | Excludes `__pycache__`, `.env`, etc. from Docker builds |
+| `API_Management/Dockerfile` | Modified — added non-root `appuser` for security hardening |
+| `altfinance-mcp/QUICKSTART.md` | 1-page beta user guide (MCP setup, API usage, examples, filter operators) |
+
+### Key Findings
+
+- **Wildcard ACM cert exists**: `arn:aws:acm:us-east-1:766784195791:certificate/613ff2e7-abfa-4168-8f68-adf74c6e074a` for `*.altfndata.com` — reused in CDK stack (no new cert needed)
+- **altfinance-mcp NOT on PyPI** — wheel built locally at `dist/` but never uploaded. `publish_mcp.py` script handles this.
+- **IAM user lacks Route53 permissions** — `api_stack.py` has a comment explaining how to skip auto-DNS and set the A record manually if needed
+- **Node.js and Docker not installed** — required before running `cdk deploy` and `docker build`
+
+### Architecture Decisions
+
+| Decision | Choice | Rationale |
+|----------|--------|-----------|
+| Load balancer | ALB (not API Gateway) | API Gateway has 30s hard timeout; Athena queries can take 60s |
+| NAT strategy | 1 NAT gateway | Saves ~$32/mo vs 2; acceptable for beta |
+| Compute | On-demand Fargate (not Spot) | Customer-facing API shouldn't have interruptions |
+| API keys | Baked into container | For 5-10 beta users, rebuild+deploy is fine; Phase 2 moves to DynamoDB |
+| Sizing | 0.25 vCPU / 0.5 GB RAM | Athena does the heavy lifting; container just sends boto3 calls |
+| Redundancy | 1 task (desired_count=1) | Sufficient for beta; ECS auto-restarts on crash |
+| VPC | New dedicated VPC | Isolated from the 28+ data pipeline Fargate tasks |
+
+### Estimated Monthly Cost: ~$59
+
+| Resource | Cost |
+|----------|------|
+| NAT Gateway | ~$32 |
+| ALB | ~$17 |
+| Fargate (0.25 vCPU/0.5GB 24/7) | ~$8.50 |
+| ECR + CloudWatch + Route53 | ~$1.50 |
+
+---
+
+## What's Left To Do
+
+### Prerequisites (install these first)
+
+| Tool | How to Install | Why |
+|------|----------------|-----|
+| **Node.js** | https://nodejs.org (LTS) | CDK CLI runs on Node.js |
+| **Docker Desktop** | https://docker.com/products/docker-desktop | Build + push container image |
+| **AWS CDK CLI** | `npm install -g aws-cdk` (after Node.js) | `cdk deploy` command |
+
+### IAM Permissions Needed
+
+Add to IAM user `sobuobi@altfndata.com`:
+- `route53:ListHostedZones`, `route53:ChangeResourceRecordSets`, `route53:GetHostedZone`
+- CloudFormation full access (for CDK)
+- Or skip Route53 in CDK and manually create the A record in AWS Console
+
+### Deployment Sequence
+
+```bash
+# 1. One-time setup
+npm install -g aws-cdk
+cd C:\Users\sharo\altfinance_monitoring_console\infra
+pip install -r requirements.txt
+cdk bootstrap aws://766784195791/us-east-1
+
+# 2. Deploy infrastructure
+cdk deploy AltFinanceApiStack
+
+# 3. Build and push Docker image
+python scripts/deploy.py
+
+# 4. Verify
+curl https://api.altfndata.com/v1/health
+
+# 5. Provision beta user keys
+python scripts/provision_key.py "Acme Capital" --tier standard --add
+python scripts/deploy.py    # Redeploy with new keys baked in
+
+# 6. Publish MCP to PyPI
+python scripts/publish_mcp.py
+
+# 7. Send QUICKSTART.md + API key to beta users
+```
+
+### Phase 2 Items (not started)
+
+- Stripe billing integration
+- DynamoDB for API key storage (no more baking keys into container)
+- DynamoDB for quota persistence (currently in-memory, resets on restart)
+- Self-service portal on `app.altfndata.com`
+- MCP directory listings (PulseMCP, awesome-mcp-servers, Anthropic registry)
+- Test suite for API and MCP server

altfinance_mcp-0.3.0/Dockerfile

@@ -0,0 +1,21 @@
+FROM public.ecr.aws/docker/library/python:3.12-slim
+
+WORKDIR /app
+
+# Install dependencies first for layer caching
+COPY pyproject.toml README.md ./
+COPY src/ ./src/
+RUN pip install --no-cache-dir .
+
+# Non-root user for security
+RUN adduser --disabled-password --no-create-home appuser
+USER appuser
+
+# Default to remote MCP mode
+ENV ALTFINANCE_TRANSPORT=streamable-http
+ENV ALTFINANCE_HOST=0.0.0.0
+ENV ALTFINANCE_PORT=8000
+
+EXPOSE 8000
+
+CMD ["python", "-m", "altfinance_mcp"]

altfinance_mcp-0.3.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 AltFinance Data
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.