io.github.patwalls/feedhook-mcp
NPM · FEEDHOOK-MCP · SCANNED SEP 20
Turn a YouTube channel into a webhook: a signed HTTP POST seconds after every new video.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 100 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 517 tokens (~64/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "test_subscription" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.patwalls/feedhook-mcp server?
io.github.patwalls/feedhook-mcp runs locally as an npm package, launched with npx -y feedhook-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · feedhook-mcp
claude mcp add patwalls-feedhook-mcp -- npx -y feedhook-mcp
{
"mcpServers": {
"patwalls-feedhook-mcp": {
"command": "npx",
"args": [
"-y",
"feedhook-mcp"
]
}
}
} {
"servers": {
"patwalls-feedhook-mcp": {
"command": "npx",
"args": [
"-y",
"feedhook-mcp"
]
}
}
} codex mcp add patwalls-feedhook-mcp -- npx -y feedhook-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"patwalls-feedhook-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"feedhook-mcp"
],
"enabled": true
}
}
} openclaw mcp add patwalls-feedhook-mcp --command npx --arg -y --arg feedhook-mcp
mcp_servers:
patwalls-feedhook-mcp:
command: "npx"
args: ["-y", "feedhook-mcp"] {
"McpServers": {
"patwalls-feedhook-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"feedhook-mcp"
]
}
}
} assistant mcp add patwalls-feedhook-mcp -t stdio -c npx -a -y feedhook-mcp
{
"mcpServers": {
"patwalls-feedhook-mcp": {
"command": "npx",
"args": [
"-y",
"feedhook-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/feedhook-mcp@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_account ~76
Create a free Feedhook account (1 feed). Returns the API key ONCE — surface it to the user and have them save it as FEEDHOOK_API_KEY in this server's environment; it cannot be retrieved again. Skip this tool if FEEDHOOK_API_KEY is already set.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Account email address. |
No output schema declared.
No examples provided.
create_subscription ~148
Turn a YouTube channel into a webhook: Feedhook will POST signed JSON {event:'video.published', videoId, title, author, url, publishedAt, …} to callbackUrl ~8s after every new video. The response includes a per-subscription `secret` (shown once) for verifying the X-Feedhook-Signature header (sha256 HMAC of the raw body).
| Name | Type | Req | Description |
|---|---|---|---|
| callbackUrl | string | yes | The http(s) URL that will receive the webhook POSTs. |
| channel | string | yes | The channel as an @handle (e.g. '@mkbhd'), a youtube.com channel URL, or a raw UC… id — resolved server-side. |
No output schema declared.
No examples provided.
delete_subscription ~37
Delete a subscription — unsubscribes from YouTube's hub and stops all deliveries.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The subscription id (uuid). |
No output schema declared.
No examples provided.
get_account ~35
Show the current account: email, plan, feed limit, and how many feeds are in use. Requires FEEDHOOK_API_KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_subscription ~62
Get one subscription including its recent delivery log — each delivery shows the videoId, status (delivered/retrying/failed), and per-attempt HTTP results. Use this to check whether webhooks are arriving.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The subscription id (uuid). |
No output schema declared.
No examples provided.
list_subscriptions ~35
List the account's channel→webhook subscriptions with state (pending/active/unsubscribed), lease expiry, and delivery counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
test_subscription ~58
Send a signed test.ping through the real delivery pipeline to a subscription's callback URL — verify the receiver works without waiting for a real video. Check get_subscription afterwards for the delivery result.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The subscription id (uuid). |
No output schema declared.
No examples provided.
upgrade_plan ~66
Upgrade the account from free (1 feed) to Pro ($9/mo, 10 feeds). Returns a Stripe Checkout URL — give it to the user to open in a browser and pay; the plan flips automatically after checkout. Call this when create_subscription returns a 402 feed-limit error.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.patwalls/feedhook-mcp server?
io.github.patwalls/feedhook-mcp is listed in the public MCP registry as io.github.patwalls/feedhook-mcp. Turn a YouTube channel into a webhook: a signed HTTP POST seconds after every new video. This page covers its npm package (feedhook-mcp).
Is the io.github.patwalls/feedhook-mcp server safe to use?
io.github.patwalls/feedhook-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.patwalls/feedhook-mcp server expose?
io.github.patwalls/feedhook-mcp exposes 8 tools: create_account, get_account, create_subscription, list_subscriptions, get_subscription, and 3 more. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.
Is the io.github.patwalls/feedhook-mcp server still maintained?
io.github.patwalls/feedhook-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.patwalls/feedhook-mcp server under?
io.github.patwalls/feedhook-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.