feat: add Webhound MCP server - #1401
Conversation
|
Hey @mfkhalil, nice work on the OAuth/DCR/PKCE setup, and thanks for the straight note about the runtime smoke test. Three things to fix and then I think this is good to go: the metadata block is CI-populated so it needs to come out, the entry needs a repo-hosted icon.svg in the server directory instead of the external PNG, and version says 0.4.3 while npm is on 0.5.3. One note: I couldn't verify the 30-tool list because the endpoint is OAuth-gated, so I'm taking that on trust unless you can paste a tools/list response. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1401 +/- ##
=======================================
Coverage ? 53.72%
=======================================
Files ? 18
Lines ? 1424
Branches ? 0
=======================================
Hits ? 765
Misses ? 572
Partials ? 87
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
done=truerule, reports, datasets, and evidence packsTesting
webhound_accountwithout starting research or spending creditsI did not claim a native ToolHive runtime smoke: Docker was initially stopped, and starting it automatically resumed nine unrelated pre-existing containers. I created no ToolHive workload, touched no container, and returned Docker Desktop to its prior stopped state rather than risking user workloads.