
Feedhook Mcp
io.github.patwallsPublished by GitHub account patwallsv0.4.0Updated Oct 25, 2026
Turn a YouTube channel into a webhook: a signed HTTP POST seconds after every new video.
Overview
Feedhook MCP lets an assistant create and manage YouTube-to-webhook subscriptions, so a callback URL receives a signed POST when a channel posts a new video.
- What you can do
- Create a Feedhook account and read plan, feed limit and feeds in use, with the API key returned once at signup. Create, list, inspect and delete channel subscriptions that fire a webhook on every new video. Review per-attempt delivery logs for a subscription and send a signed test ping through the real pipeline to check a receiver. Upgrade from the free plan to a paid plan, which returns a Stripe Checkout URL to open in a browser.
- When to use it
- Use it when you want an assistant to wire a YouTube channel to an HTTP endpoint without polling or YouTube API quota, for example to trigger automation on new uploads. Also useful for checking whether a webhook receiver is reachable and correctly verifying signatures.
- Requirements
- Runs locally over stdio via npx, so Node.js is needed. Most tools require the FEEDHOOK_API_KEY environment variable; without it, the create_account tool can issue a free-plan key. FEEDHOOK_API_URL optionally overrides the API base. Network access to the Feedhook service and a reachable callback URL are needed.
Installation
In SourceWeft
- Open Feedhook Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
feedhook-mcp
MCP server for Feedhook — turn a YouTube channel into a webhook: your endpoint gets a signed HTTP POST ~8 seconds after a new video is published. No polling, no YouTube API quota. Feedhook does YouTube's WebSub plumbing (hub subscription, verification handshake, ~5-day lease renewals, retries with backoff) and resells it as a clean API; this package is the agent front door.
Use it
Or in any MCP client config:
No key yet? Add the server without the env var and ask your agent to call
create_account (free plan: 1 feed) — the key is returned once; save it as
FEEDHOOK_API_KEY.
Tools
The webhook your endpoint receives
Non-2xx responses are retried 5 times with backoff. Respond within 15 seconds.
Environment
FEEDHOOK_API_KEY— your account key (most tools need it)FEEDHOOK_API_URL— override the API base (defaulthttps://feedhook.walls.sh)
MIT · a walls.sh product
Source: README.md at commit 68d289f
Tools
0Version history
1- v0.4.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts