MCP Server for Claude / Stdio transport
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":"mcp-server-stdio","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.
# Billing Service MCP Server A Model Context Protocol (MCP) server that exposes billing information from your StackBill API. ## Setup ### Prerequisites - Python 3.14+ - `uv` package manager (or `pip`) ### Installation ```bash # Install dependencies uv pip install -r requirements.txt ``` Or if using pip directly: ```bash pip install fastmcp httpx ``` ## Running the Server (stdio transport) This project now runs as an MCP stdio server (MCP messages over stdin/stdout). Start the server with: ```bash python -m app.main ``` The server communicates over standard input/output and is intended to be launched by an MCP-capable client (for example, a desktop assistant or a tool runner that spawns the process and talks MCP over stdio). If you previously used `mcp-inspector` or other HTTP-based tools, note that those expect an HTTP endpoint; for stdio you should configure your MCP client to execute the command above. For Claude Desktop or a similar client that accepts a command, use the configuration example in the "Configuration" section below to point the client at this process. ### 4. Query Billing Information In the mcp-inspector interface, call the `get_billing_summary` tool with your parameters: **Example 1: Get current month billing** ```json { "domain_uuid": "4ca-d-823", "zone_uuid": "e5b0-50b-ff-8e2-f2817" } ``` **Example 2: Get billing for specific date range** ```json { "domain_uuid": "4ca-d-823", "zone_uuid": "e5b0-50b-ff-8e2-f2817", "from_date": "03-11-2025 00:00", "to_date": "20-11-2025 00:00", "lang": "en" } ``` ## Tool Reference ### `get_billing_summary` Fetch billing summary for a specified date range. **Parameters:** - `domain_uuid` (required): Your domain UUID (e.g., "4ca-d-823") - `zone_uuid` (required): Your zone UUID (e.g., "e5b0-50b-ff-8e2-f2817") - `from_date` (optional): Start date in format `DD-MM-YYYY HH:MM`. Defaults to 1st of current month - `to_date` (optional): End date in format `DD-MM-YYYY HH:MM`. Defaults to tod…
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.