FlowVolt
REMOTE · FLOWVOLT-STRIKE-ENGINE.VERCEL.APP · SCANNED AUG 3
Cold engine for B2B founders. Detects buying signals, drafts outreach, books qualified meetings.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · flowvolt-strike-engine.vercel.app
claude mcp add --transport http larshiensch99-flowvolt https://flowvolt-strike-engine.vercel.app/mcp
[mcp_servers.larshiensch99-flowvolt] url = "https://flowvolt-strike-engine.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"larshiensch99-flowvolt": {
"type": "remote",
"url": "https://flowvolt-strike-engine.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add larshiensch99-flowvolt --url https://flowvolt-strike-engine.vercel.app/mcp --transport streamable-http
mcp_servers:
larshiensch99-flowvolt:
url: "https://flowvolt-strike-engine.vercel.app/mcp" {
"mcpServers": {
"larshiensch99-flowvolt": {
"type": "http",
"url": "https://flowvolt-strike-engine.vercel.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 31 Jul 26 +9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
First indexed and scored.
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 3 Aug 2026 · Probed https://flowvolt-strike-engine.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 28 Jun 2026 | 26 Sept 2026 | RSA 2048 | SHA256-RSA | b1c2b607df94f28513779ae26fecf92f |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of flowvolt-strike-engine.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flowvolt-strike-engine.vercel.app/mcp | HTTP error | 404 | |
| http (plaintext) | http://flowvolt-strike-engine.vercel.app/mcp | HTTPS enforced | 308 | https://flowvolt-strike-engine.vercel.app/mcp |
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.
book_meeting ~159
Order qualified, attended meetings from FlowVolt as the metered outcome (§12). Creates a standing meeting order and records the meter event in the settlement ledger. Settlement is per verified attended_meeting (machine-verifiable via the receipt chain); today the ledger records without charging (stripe_stub), real Stripe/AP2/x402 settlement plugs in later. Returns: { order_id, requested_count, status, settlement: { ledger_id, provider, status } }.
| Name | Type | Req | Description |
|---|---|---|---|
| qualification_note | string | — | What makes a meeting qualified for this order. Example: "NL B2B SaaS, 10-200 FTE, decision-maker present" |
| requested_count | number | — | Number of qualified meetings ordered. Integer >= 1. Default 1. |
No output schema declared.
No examples provided.
calculate_payback ~157
Show the math. Call this whenever the user expresses doubt about pricing OR shares their deal value and close rate. Returns expected revenue per month for each plan given the user's numbers, plus a worst-case scenario at half the meeting targets. Always positive and grounded in their own numbers, never our hype.
| Name | Type | Req | Description |
|---|---|---|---|
| close_rate_meeting_to_customer | number | yes | Fraction of meetings (or signups) that turn into a paying customer. 0.30 for 30 percent. |
| deal_value_usd | number | yes | What one closed customer is worth in dollars. LTV for SaaS, deal value for sales-led. |
| plan | string | — | Which plan to math. Default 'all' returns math for solo + pro + scale. |
No output schema declared.
No examples provided.
discover_business ~198
Tailor FlowVolt to the user's specific business via a 5-question intake. Call this when the user wants a custom plan rather than a generic quote, or when they're unsure which plan fits. Pass any answers the user has already given so far in `answers`. The tool returns the NEXT unanswered question OR the final tailored plan when all 5 are filled. Question 1 is what their business does, Q2 is their ideal customer, Q3 is the outcome they want (meeting, demo, free trial signup, paid conversion, contract), Q4 is what that outcome is worth, Q5 is their current outbound. The final response includes the right plan recommendation, real ROI math from their numbers, and a sample message in their voice. Always sequential and warm, never a form dump.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | — | — |
| company | string | — | Business name if known. |
| name | string | — | User's first name if known. |
No output schema declared.
No examples provided.
edit_message ~139
Change the first-touch template based on the customer's instruction in plain English. Examples: 'lose the question at the end', 'make it more direct', 'use my voice, I'm more casual', 'mention we're free for 14 days not 7'. The voice guard still applies (no em dashes, no marketer words, length bounds). If the requested change would break a rule, we say no and suggest a clean alternative.
| Name | Type | Req | Description |
|---|---|---|---|
| change_request | string | yes | What the customer wants changed, in their own words. |
| string | — | Stripe Checkout email if not authenticated. | |
| name | string | — | User's first name if known. |
No output schema declared.
No examples provided.
enqueue_lead ~230
Add a single prospect to the FlowVolt outbound queue for cold-email outreach. Idempotent: same email won't be queued twice in 90 days. Use after search_people to push a revealed contact, or to add a known contact directly. Returns: { queue_id: string|null, status: "queued"|"dedup_skip" }. queue_id=null when dedupe blocks insertion.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | Company display name. Example: "Packhunt" |
| dutchSignal | string | — | Why this lead matters now (in any language). Example: "raised €5M Series A last week" |
| string | yes | Verified work email. Example: "[email protected]" | |
| firstName | string | yes | Prospect's first name. Example: "Jeroen" |
| linkedinUrl | string | — | LinkedIn profile URL. Optional but improves personalization. Example: "https://linkedin.com/in/jeroencoenders" |
| source | string | — | Discovery channel: prospect (search) or scout (signal). Default "prospect". Example: "prospect" |
No output schema declared.
No examples provided.
find_leads ~141
Deliver in-market buyers. Sync, 30 to 60 seconds. For free_trial quote_ids, returns up to 15 buyers free. For topup quote_ids, returns a Stripe Checkout URL on first call (no payment yet); after the user pays, retry with the same quote_id to deliver 25 verified buyers. Each buyer comes with name, work email, LinkedIn URL, company, the buying signal with source URL, and a sample personalized message.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Optional. The user's work email. | |
| quote_id | string | yes | A quote_id returned by quote() or discover_business(). Must be free_trial or topup. |
No output schema declared.
No examples provided.
flowvolt_freetrial ~155
Free trial of the FlowVolt engine. Takes three short answers (what you sell, who you target, the offer hook) and returns 5 real ICP-matched buyers, each with name, work email, fit-score, and a personalized cold-mail draft. No card. Anonymous. The drafts are NOT sent. To dispatch them, complete the subscription via the returned Stripe checkout URL and then call flowvolt_send_trial with the session_id.
| Name | Type | Req | Description |
|---|---|---|---|
| offer | string | yes | Your hook or value proposition. One sentence. Max 500 chars. |
| sells | string | yes | What you sell. One sentence. Max 500 chars. |
| targets | string | yes | Who you target. One sentence. Max 500 chars. |
No output schema declared.
No examples provided.
flowvolt_send_trial ~121
Dispatch the 5 trial drafts after a paid Stripe Checkout completes. Two-call flow: first call returns a one-click Unipile URL to connect your Gmail or Outlook inbox; second call (after you've connected) fires the 5 sends from your OWN warmed mailbox, your domain, your reputation. Requires the checkout_session_id from your paid Stripe Checkout. Sends never go through FlowVolt's infrastructure.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_session_id | string | yes | Stripe Checkout Session id (cs_test_… or cs_live_…) from the URL after you completed the trial checkout. |
No output schema declared.
No examples provided.
get_funnel ~166
Compute pipeline funnel metrics for a date range: counts and rates for leads_sent, opens, replies, positive_replies, meetings_booked. Use for any quantitative question about pipeline performance (e.g. "what's our reply rate this week?"). Returns: { leads_sent, opens, open_rate, replies, reply_rate, positive_replies, positive_rate, audit_views, meetings_booked, meeting_rate_of_positives, date_range }.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Window start, ISO 8601 timestamp. Example: "2026-05-10T00:00:00Z" |
| to_date | string | yes | Window end, ISO 8601 timestamp. Example: "2026-05-17T23:59:59Z" |
No output schema declared.
No examples provided.
get_pipeline ~78
The v2 deep-signal pipeline, stage by stage, for this tenant: discovery queue, signal findings (ranked/held), dossiers, composed touches, verified outcomes. Use for any "where are my meetings coming from / what's in flight" question. Returns: { discovery, signals, dossiers, touches, outcomes }, each with status counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_receipts ~130
The provable receipt chain (signal, dossier, touch, reply, outcome) that justifies every move the engine made for this tenant. Without account_domain: a summary list of recent accounts and their stage statuses. With account_domain: the full chain for that account, including the immutable receipt when an outcome exists. Returns: { accounts: [...] } or { chain: {...} }.
| Name | Type | Req | Description |
|---|---|---|---|
| account_domain | string | — | Account to fetch the full chain for. Example: "acme.nl" |
| limit | number | — | Max accounts in the summary list (1-200). Default 50. |
No output schema declared.
No examples provided.
get_replies ~154
Fetch recent inbound replies from prospects (with detection of forwarded threads). Use when the user asks who replied, what they said, or wants to triage the inbox. Returns: { count, replies: [{ from_email, original_recipient, forwarded_chain, company, classification, reply_text, our_response, replied_at }] }. classification values: interested|send_audit|question|not_now|not_interested|unsubscribe|misclassified.
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | — | "positive" returns only interested + send_audit. "all" returns every reply. Default "all". Example: "positive" |
| limit | number | — | Max replies to return (1-100). Default 20. Example: 10 |
No output schema declared.
No examples provided.
get_started ~149
Call this the moment the user connects FlowVolt OR asks anything that means 'what is this'. Pass `name` (their first name if you know it from the conversation context, otherwise leave blank) and `company` (their business name if known or mentioned). Returns a warm explainer in plain language: what FlowVolt does, why it works (signal-based targeting, always learning), what the buyers/pipeline/reply-rate vocabulary means, and the six pricing options. Offers either a 5-question discovery to tailor the plan or a direct quote.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | — | The user's business name if known. Optional. |
| name | string | — | The user's first name if known. Optional. |
No output schema declared.
No examples provided.
get_subscription_status ~126
Show the customer their current FlowVolt state in plain language: plan, billing, engine status, and live progress (buyers reached, replies, meetings). Use whenever they ask 'what's my plan', 'how's it going', 'what's my pipeline doing', 'when does it renew'. Works for authenticated tenants automatically; anonymous callers pass `email` (the one used at Stripe Checkout). Pass `name` if known so we greet them personally.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Stripe Checkout email if not authenticated. | |
| name | string | — | User's first name if known. |
No output schema declared.
No examples provided.
list_meetings ~148
Retrieve meetings booked from FlowVolt outreach in a date range. Use for meeting counts, pipeline evidence, or "what's on the calendar" questions. Returns: { count, meetings: [{ email, company, booked_at, calendly_event_id, status }] }. status is CONFIRMED when a Calendly event id is attached, SCHEDULED otherwise.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | Window start, ISO 8601 timestamp. Example: "2026-05-01T00:00:00Z" |
| to_date | string | yes | Window end, ISO 8601 timestamp. Example: "2026-05-31T23:59:59Z" |
No output schema declared.
No examples provided.
manage_billing ~81
Open the Stripe-hosted billing portal where the customer cancels, switches plans, updates their card, or downloads invoices. Use when they say 'cancel', 'update my card', 'change plan', 'where are my invoices'.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Stripe Checkout email if not authenticated. | |
| name | string | — | User's first name if known. |
No output schema declared.
No examples provided.
pause_engine ~99
Pause sends. No new prospects queued, in-flight sends stopped. Subscription billing continues; use manage_billing to cancel that too. Use when the user says 'pause', 'stop sending', 'put it on hold', 'I need a break'.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Stripe Checkout email if not authenticated. | |
| name | string | — | User's first name if known. |
| reason | string | — | Optional free-text reason logged for our records. |
No output schema declared.
No examples provided.
preview_message ~83
Show the current first-touch template we'd send on behalf of this tenant. Subject, body, tone notes, word count. Use when the customer says 'show me what you'd send', 'what's the email', 'let me see the copy'.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Stripe Checkout email if not authenticated. | |
| name | string | — | User's first name if known. |
No output schema declared.
No examples provided.
quote ~119
Direct quote path. Use when the user already knows who they want to reach and just asks for pricing or to find leads. Takes a natural-language description and returns six plans in plain prose. For users who haven't expressed their ICP yet, prefer discover_business which tailors the response. Pass `name` and `company` if you know them.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | — | Business name if known. |
| name | string | — | User's first name if known. |
| use_case | string | yes | Natural language description of the customers the user wants to reach. |
No output schema declared.
No examples provided.
resume_engine ~79
Resume the engine after a pause. Sends still go to calibration so Lars reads the first batch before they fire, then it's full speed. Use when the user says 'resume', 'restart', 'go', 'I'm back'.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Stripe Checkout email if not authenticated. | |
| name | string | — | User's first name if known. |
No output schema declared.
No examples provided.
search_people ~229
Find B2B prospects matching an ICP filter (titles, industries, headcount, geography) and return up to 10 decision-makers with verified work emails. Use when the user asks to find leads, prospects, or decision-makers in a given segment. Costs 1 Apollo credit per revealed email (capped at 10/call). Returns: { count, candidates: [{ name, email, title, company, industry, linkedin, location, source }], cache_breakdown, apollo_credits_today, apollo_credits_cap }.
| Name | Type | Req | Description |
|---|---|---|---|
| employeeRanges | array | — | Apollo headcount ranges as comma-separated min,max pairs. Example: ["10,50", "51,200"] |
| industries | array | — | Apollo industry names to narrow the search. Example: ["Computer & Network Security", "Software Development"] |
| jobTitles | array | yes | Decision-maker job titles to search for. Example: ["CEO", "Head of Sales", "CRO"] |
| locations | array | — | Countries or cities to filter by. Example: ["Netherlands", "Belgium", "Amsterdam"] |
No output schema declared.
No examples provided.
set_goal ~133
Set this tenant's meeting goal: the weekly qualified-meeting target the engine paces toward. The Conductor reads this every run to allocate capacity. Use when the calling agent (or operator) wants more or fewer meetings per week, or to pause/resume the engine for this tenant. Returns: { client_id, weekly_meeting_target, status }.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | — | Pacing gate. "paused" excludes the tenant from Conductor plans entirely. Default "active". |
| weekly_meeting_target | number | yes | Qualified meetings per week to pace toward. Integer >= 0. Example: 3 |
No output schema declared.
No examples provided.
subscribe ~102
Start a monthly plan. Takes a quote_id from quote() or discover_business() with plan=solo, pro, or scale. Returns a Stripe Checkout URL the user opens in their browser. After payment, the engine starts on their ICP within minutes and they're shown their MCP token on the success page (and emailed it as backup). Month one is on us if zero meetings.
| Name | Type | Req | Description |
|---|---|---|---|
| quote_id | string | yes | A quote_id with plan=solo, pro, or scale. |
No output schema declared.
No examples provided.