Hurl MCP: 20 real tools to read, check, lint, scaffold, build and run Hurl code.
Nothing to run from here
SlingHook is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
11
tools declared
local
runs on your machine
—
downloads a day
What it does
Inspect, debug and replay captured webhooks (Stripe, GitHub, Shopify) from your AI agent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user slinghook-mcp '--' npx -y slinghook mcp
# 2 — ask your agent for something these tools do
# list_endpoints, list_events, get_event and 8 more
SlingHook costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DYAll 1 server
dylancourtney5841 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts SlingHook as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user slinghook-mcp '--' npx -y slinghook mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take SLINGHOOK_TOKEN (SlingHook API token (shk_...). Optional after running `npx slinghook login` once.), SLINGHOOK_SERVER (Server URL. Defaults to https://slinghook.co.za; set it for a self-hosted server.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Lists the catch URLs (endpoints) in the current SlingHook workspace, with where each one relays events. Start here to find the endpoint a webhook was sent to.
No parameter schema on file.
Lists webhooks captured on an endpoint, newest first, as short summaries (number, time, method, event type, signature status) without bodies. Use get_event for one event in full. Without query or before_id it reads the newest events (up to 50, every plan). query and before_id search the whole…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | yes | — | |
| limit | integer | no | How many events to return |
| signature | string | no | Only events whose signature check had this result |
| method | string | no | Only this HTTP method, e.g. POST |
| query | string | no | Pro: free text to find in bodies, headers and notes, or a JSON path match such as type = invoice.paid or data.object.id = in_123 (!= to exclude) |
| before_id | integer | no | Pro: page further back; pass next_before_id from the previous result |
Reads one captured webhook in full: method, headers, query string, body and signature status. Long bodies are cut at max_body_chars.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | — | |
| max_body_chars | integer | no | Longest body to return |
Explains why a webhook's signature verified or failed: detected provider scheme (Stripe, GitHub, Shopify, Slack, Standard Webhooks, Twilio), wrong secret, stale timestamp, or a body that was modified (reformatted JSON, re-escaped slashes). Checks against the secret saved on the endpoint, or…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | — | |
| secret | string | no | Optional candidate signing secret to test instead of the saved one (not stored) |
Re-sends a captured webhook to a URL from this machine (e.g. the local handler at http://localhost:3000/webhooks), with its original method, headers and body, so signature checks run for real. Records the result in the dashboard's replay history and returns the verdict against the previous attempt…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | — | |
| target_url | string | yes | Where to deliver it, e.g. http://localhost:3000/webhooks |
Shows the replay history of one event and the fix verification verdict for the latest replay (or replay_id): fixed, regressed, still_failing or still_passing, compared with the attempt before it to the same URL. Includes replays made from the dashboard and by slinghook listen. On Pro and above…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | — | |
| replay_id | integer | no | A specific replay attempt; default the latest |
Lists the saved scenarios on an endpoint: ordered sets of captured events (for example subscription created, payment failed, canceled) that run_scenario replays in sequence. Scenarios are built in the dashboard.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | yes | — |
Replays every event of a saved scenario, in order, from this machine to a URL (e.g. the local handler), and reports each step: status, pass or fail, and the verdict against that event's previous replay to the same URL. Use it after a fix to prove a whole flow works, not just one event. Steps go…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scenario | integer | yes | Scenario id, from list_scenarios |
| target_url | string | yes | Where to deliver each step, e.g. http://localhost:3000/webhooks |
| stop_on_failure | boolean | no | Stop at the first failing step |
| keep_timing | boolean | no | Wait the recorded gap between steps, up to 5 seconds each |
Turns a real captured webhook into code to build a handler around: typed models of its payload, a fixture file with the body, and a test that posts it to the handler. Languages: typescript (types + Jest/Vitest test), python (dataclasses + pytest), php (DTO + Laravel test), go (structs; no test).…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | yes | — | |
| language | string | yes | Language of the handler |
| parts | array | no | Which files to generate. Default: all three |
| target_url | string | no | The handler URL the test posts to. Default: the endpoint's relay URL, or http://localhost:3000/webhooks |
Shows what differs between two captured webhooks, field by field (JSON paths such as data.items[0].price), plus header differences. Use it for "this one worked and that one failed, what changed?" or to spot a provider changing its payload. Leave out b to compare with the previous event of the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a | yes | First event. … | |
| b | no | Second event, same forms as a. Default: the previous event of the same type on the same endpoint | |
| include_headers | boolean | no | Also compare headers |
Creates a new catch URL (endpoint) in the current workspace and returns the URL to paste into the provider's webhook settings. If an endpoint with the same name already exists, returns that one instead of making a copy. Plan limits apply (Free has 3 endpoints). It does not take a signing secret:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | What it is for, e.g. "Shopify orders (local)" |
| relay_to | string | no | Optional URL to relay each event to, e.g. http://localhost:3000/webhooks |
| signature_scheme | string | no | Provider signature to check once a secret is added; auto detects it from headers. Standard covers Standard Webhooks / Svix |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SlingHook or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.5.2 · scanned 10 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest4345d0f7fd1ee745f0bb5aefaa5b23e446741c2e3f67c880baf30c1b60efe58b
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest4345d0f7fd1ee745
Scanned2026-11-10
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.5.2. Pin a release below and the command asks for exactly that one.
0.5.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish SlingHook can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.