Infobroker MCP server

<!-- README DESIGN:

Product principle. The README is the product — it answers three questions in under 60 seconds: what this does, why you should care, how to use it. Readme-driven development: changes that affect the README's claims SHALL update the README before or alongside the code change. A README that promises something the server does not deliver is a defect. Every numeric claim (tool count, provider count, zero-config count) reconciles against src/index.ts and config.json — the validator enforces this (Surface reconciliation).

Voice: Professional, confident, benefit-first. Direct address ("you"). No first-person ("we", "I", "our"). Short declarative fragments in the tagline. Every sentence survives a reader who knows nothing about Infobroker.

Demo: Natural-language prompts in blockquotes ("Search for..."), never full tool names (infobrokersearchweb). Show the reader how to express what they want — the AI maps intent to tools. Every demo prompt SHALL be a valid natural-language command the reader could actually run; broken prompts are a README defect.

Structure: Hero → North Star → Quick Start → MCP Server (§3 features) → Skills → Providers → Configuration → How It Compares → Contribute → License → Spec. No other ordering. Canonical h2 headings are enforced by validate-readme. A TOC listing the canonical h2 sections follows the Hero; validate-readme enforces TOC↔heading sync.

Audience split: §2 is for developers who want to start the server. §3 describes what users can do with it. The Skills section (§3.5) describes the bundled client skills and instructions. §4-5 are configuration. §6 is competitive context. §7-9 are contributor/license/spec.

Skills section: Prose only — no tables, no blockquotes, no feature bullet lists. Lists the six bundled skills and the workflow shapes the orchestrator routes to, with analysis-loop as the escalation shape. Cross-links to the skill references (pipeline-map.md, workflows.md).

No repetition. One story vector per section. Don't explain the same concept in two places — the validator flags near-duplicate sentences. No feature bullet lists in prose. No tables for feature descriptions.

Feature blurbs: Each h3 under §3 follows a four-beat cadence — benefit hook, mechanics, competitive proof, closer. The competitive-proof sentence contrasts Infobroker against the current tool landscape without naming individual competitors; it answers "why this beats what you're used to."

MCP server order: Features under §3 follow a research workflow — Search → Extract → Verify → Write → Manage. New features insert at the workflow point they serve; reorder the section to restore the workflow after every addition or removal.

Comparison table: Three columns (Tool name | What you're used to | How Infobroker differs). One row per competitor category, never individual products. Prose paragraph below synthesizes the table; it never repeats a row's content verbatim.

Hero: Exactly three elements — h1 heading, bold tagline, one prose paragraph. No sub-headings, bullet lists, or preamble paragraphs. The tagline uses short declarative fragments separated by periods — never a sentence or question. Enforced maximum 200 words (validate-readme). The tagline "One server. Every source. Research that delivers." is the repeated refrain — it appears exactly twice, in the Hero tagline and the comparison closing prose, and no more. The hero paragraph closes with "Free first. Privacy always." — distinct from the tagline. Updating any repeated line requires updating its echo.

North Star: Single paragraph stating the Bothan Spynet metaphor and intelligence-cycle framing. No sub-headings, lists, or blockquotes. Maximum 100 words (enforced by validate-readme).

Shortened. The full README is on GitHub.