Minimal Azure Policy engine with file and sdk backends
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"py-mcp-travelplanner","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Travel Planner **A unified MCP (Model Context Protocol) server providing a single entry point to comprehensive travel planning services.** This project implements ONE unified MCP server that orchestrates multiple travel-related backend services (flights, hotels, weather, geocoding, events, finance). MCP clients like Claude Desktop connect to a single server interface and access all travel planning capabilities through it. ## Key Features - **Single MCP Server Entry Point**: One unified server (`mcp_server.py`) for all travel services - **Service Orchestration**: Manages multiple backend services through one interface - **MCP Tools**: Expose travel planning capabilities via Model Context Protocol - **Claude Desktop Integration**: Ready-to-use configuration for Claude Desktop - **Modular Backend**: Each service runs independently but is coordinated by the unified server - **Runtime Configuration**: Multi-source config with env vars, .env, and YAML support ## Quick Start **Ready-to-use MCP configuration examples** are provided in the `examples/` directory: - **`claude_desktop_config_uv_testpypi.json`** - Run from Test PyPI with UV (no installation) - **`claude_desktop_config_uv_pypi.json`** - Run from PyPI with UV (stable release) - **`claude_desktop_config_template.json`** - Standard Python installation See [`examples/QUICK_REFERENCE.md`](examples/QUICK_REFERENCE.md) for copy-paste configs and [`examples/MCP_CONFIG_README.md`](examples/MCP_CONFIG_README.md) for complete documentation. ## Configuration The project uses a **multi-source runtime configuration system** with proper precedence: 1. **Environment variables** (highest priority) 2. **.env file** 3. **runtime_config.yaml** 4. **Default values** (lowest priority) See [`docs/CONFIG_README.md`](docs/CONFIG_README.md) for complete configuration documentation. ## Architecture ``` MCP Client (Claude Desktop) ↓ (stdio) Unified MCP Server (single entry point) ↓ (orchestrates) Back…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.