MCP server for BizChat Gov Cloud quality-through-feedback data
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":"gc-feedback-mcp","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.
# GC-Feedback MCP Server Manifest-driven MCP server for BizChat Gov Cloud **quality-through-feedback** data. Same architecture as `gc-eval-mcp` — reads a `manifest.json` from Azure Blob Storage at startup, dynamically registers tools per dataset type (HTML reports, Markdown docs, JSON, SQLite). ## Architecture ``` ┌──────────────┐ ┌──────────────────┐ ┌────────────────────┐ │ Copilot CLI │───▶│ gc-feedback-mcp │───▶│ Azure Blob Storage │ │ (MCP client) │ │ (this server) │ │ (feedback-data) │ └──────────────┘ └──────────────────┘ └────────────────────┘ │ ▲ ▼ │ ┌──────────────┐ ┌─────────────┐ │ Key Vault │──────────▶│ Storage Key │ │ (az login) │ └─────────────┘ └──────────────┘ ``` ## Adding Data 1. Add files to the `feedback-data` blob container 2. Update `manifest.json` to describe the new dataset 3. Upload the updated manifest No code changes needed — the server picks up new datasets automatically. ## Local Development ```bash cd quality-through-feedback/mcp-server pip install -e . gc-feedback-mcp ``` ## Publishing Tagged releases (e.g., `feedback-v1.0.0`) auto-publish to PyPI via GitHub Actions.
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.