Hystruct
Hystruct is an AI-driven web scraping tool that simplifies data extraction from websites using predefined schemas, supporting various data fields like job listings and e-commerce.
Verdict
Common use cases
- Audit webhook endpoints before a security review
- Debug missing events by checking active webhooks
- Document integration architecture for onboarding
- Verify webhook configuration after deployment
- Compare staging and production webhook setups
Integration
- Vendor
- Hystruct
- Category
- other
- Auth
- API_KEY
- Tools
- 1
- Composio slug
hystruct
Tools
- List All Webhooks
Tool to list all webhooks associated with the account. Use when you need to retrieve every configured webhook for your team.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Add MCP. 2. Search for Hystruct and click Connect. 3. You'll be prompted to paste an API key — generate one in your Hystruct dashboard under API Settings with at least 'webhooks:read' scope. 4. Paste the key into Switchy and click Authorize. 5. Switchy confirms the connection and shows Hystruct as active in your MCP list. 6. Open any Space and type '@Hystruct list all webhooks' to test — you should see a structured response with your configured endpoints. 7. If the response is empty or errors, verify the API key has the correct scope and hasn't expired in Hystruct's dashboard.
What teammates see: by default, memories from Hystruct are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Audit Active Webhooks
@Hystruct list all webhooks and show me the URL, event types, and status for each one in a tableOpen in a Space →
Find Inactive Endpoints
@Hystruct list all webhooks and highlight any that are inactive or have a non-success statusOpen in a Space →
Document Event Pipeline
@Hystruct list all webhooks and write a short summary of what events we're sending whereOpen in a Space →
Compare Environments
@Hystruct list all webhooks and tell me if any endpoints look like they're pointing to staging instead of productionOpen in a Space →
Pre-Deploy Checklist
@Hystruct list all webhooks and confirm we have endpoints configured for order.created and payment.succeeded eventsOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Hystruct show me all the webhooks we have configured right now
Found 3 active webhooks in your account: (1) 'Slack Notifications' posting to https://hooks.slack.com/services/T00/B00/xxx, triggered on document.created and document.updated events; (2) 'Analytics Pipeline' sending to https://analytics.example.com/ingest, triggered on all events; (3) 'Backup Service' posting to https://backup.internal/receive, triggered on document.deleted only. All three webhooks show 'active' status with recent successful deliveries in the last 24 hours.
This example shows the MCP's single read capability — listing webhooks. Useful for auditing integrations or debugging event flows. Requires a valid API key with read permissions. The MCP currently offers only this one tool, so teams needing webhook creation or modification must use Hystruct's dashboard directly.
@Hystruct which webhooks are listening for document deletion events?
One webhook is configured to receive document.deleted events: 'Backup Service' (https://backup.internal/receive). This webhook has been active since March 2024 and successfully delivered 47 events in the past week. The other two webhooks in your account ('Slack Notifications' and 'Analytics Pipeline') are not subscribed to deletion events — they trigger on creation and update actions only.
Demonstrates filtering webhook data by event type, which the AI can infer from the list response. This workflow helps teams understand their event routing without clicking through a UI. Note that the MCP retrieves all webhooks and the AI performs the filtering — there's no server-side query parameter for event type.
@Hystruct compare our current webhook setup to last month's configuration and flag any changes
I can retrieve your current webhook list, but I don't have access to historical configurations — the Hystruct MCP only returns the present state of webhooks. To track changes over time, you'd need to store snapshots externally (e.g., in a Space note or version control). Right now, your account has 3 active webhooks: 'Slack Notifications', 'Analytics Pipeline', and 'Backup Service'. If you share a previous snapshot, I can compare them for you.
This example shows a limitation: the MCP provides no versioning or audit trail. The AI correctly declines to hallucinate historical data and suggests a workaround. Teams wanting change detection should export webhook lists periodically. The MCP's single-tool design means it's best suited for quick audits, not ongoing monitoring.
Use-case deep-dives
When Hystruct makes sense for quarterly security reviews
A 6-person compliance team at a fintech startup runs quarterly audits of all third-party integrations. They need a single list of every webhook firing into their systems—Slack, PagerDuty, customer support tools—to verify each one against their vendor risk register. Hystruct's single-tool MCP gives them that list in one call, no manual portal-hopping. The trade-off: if your team only uses 2-3 SaaS tools, you can audit webhooks faster by logging into each admin panel directly. Hystruct wins when you're managing 10+ webhook sources and need the full inventory on demand. If your compliance cadence is monthly or faster, this MCP saves 20 minutes per cycle.
Why Hystruct helps on-call engineers during outages
A 3-person DevOps rotation gets paged at 2am because a critical alert isn't firing. The on-call engineer suspects a misconfigured or deleted webhook but doesn't know which service broke. Hystruct's list-all tool lets them pull the full webhook inventory from Switchy's chat without switching contexts or remembering which admin panel holds the config. The limitation: this MCP only lists webhooks—it won't show you payload schemas or firing history. If your incident requires deeper forensics, you'll still need the vendor's dashboard. Hystruct is the right call when speed matters more than detail, and your team's webhook sprawl is large enough that memory fails under pressure.
When Hystruct speeds up new-hire integration setup
A 5-person growth team onboards a new marketing ops hire who needs to understand every webhook feeding their analytics stack. The team lead uses Hystruct to generate a current webhook list, then pastes it into the onboarding doc so the new hire sees exactly which tools talk to which endpoints. The catch: if your webhook config changes weekly, a static list goes stale fast. Hystruct works best for teams with stable integration architectures—SaaS stacks that shift every few months, not every sprint. If your webhook topology is volatile, you'll re-run this list often enough that a dedicated integration-mapping tool might justify the cost. For teams under 10 people with modest churn, Hystruct's single-call simplicity beats heavier tooling.
Frequently asked
What does the Hystruct MCP do in Switchy?
It lets your AI agents list and inspect all webhooks configured in your Hystruct account. This is useful when you're debugging integrations, auditing what external systems are listening to your events, or checking webhook configurations before making changes. The MCP currently focuses on read operations — you can see what's configured but not create or modify webhooks through Switchy.
Do I need admin access to connect Hystruct?
You need an API key with read permissions for webhooks. Hystruct uses API key authentication, so whoever connects it must have access to generate or retrieve a valid key from your Hystruct account settings. If your team restricts API key creation to admins, you'll need admin involvement to set this up initially.
Can the Hystruct MCP create or delete webhooks?
No, it only lists existing webhooks. If you need to create, update, or delete webhooks, you'll still need to use Hystruct's dashboard or API directly. The MCP is designed for inspection and auditing workflows, not webhook lifecycle management. This keeps the integration simple and reduces the risk of accidental changes.
Why use this instead of just logging into Hystruct?
The MCP lets your AI agents pull webhook data into conversations without context-switching. If you're troubleshooting an integration issue or documenting your event architecture, the agent can fetch the webhook list alongside logs from other tools. It's faster than manually copying data from Hystruct's UI, especially when you're correlating webhook configs with activity in Slack, GitHub, or your monitoring stack.
Who on the team should connect Hystruct to Switchy?
Whoever manages your integrations or has access to Hystruct API keys. Typically this is a backend engineer, DevOps lead, or technical product manager. Since the MCP only reads webhook configurations, you don't need to restrict it to a single person — anyone who needs visibility into your event routing can connect their own API key.