General Tools
ventureinsights.com.sa
Provides venture concept diagnostic services to founders.
ENDPOINT 1
https://solutions.ventureinsights.com.sa/api/mcp
MCP server metadata
- Name
- venture-insights
- Version
- 1.0.0
Venture Insights is a decision-grade venture advisory in Jeddah, Saudi Arabia. Through this server an AI agent can (1) read the live service catalogue, (2) request the FREE Concept Diagnostic for a founder, and (3) poll its progress. Trust model: calling start_free_diagnostic never generates anything and never charges anyone. Venture Insights emails the founder a one-click confirmation link; the free study starts only after the founder personally clicks it. Always relay that expectation to your user, then poll with check_diagnostic_status (every 30-60 seconds is plenty) using the intake_id and token the start call returned. Starting a diagnostic — ALWAYS use the form: when the user wants to start (or check the viability of) an idea, call open_diagnostic_intake to show the interactive form. This is the default, strongly-preferred path. The form starts BLANK and the founder enters their own name, email and concept and submits — this keeps the destination email accurate (each founder gets one free diagnostic, emailed to the address they enter). Do NOT pre-state or assume their email, and do NOT call start_free_diagnostic directly with remembered or assumed details — let the founder fill the form themselves. Only call start_free_diagnostic directly in the rare case the founder has just typed out every field in this conversation and explicitly asked you to submit without the form. One diagnostic per founder email: the start call itself never reveals whether a founder is already on file (to avoid an email-enumeration oracle) — the one-per-founder rule resolves at CONFIRM time. If polling check_diagnostic_status returns an "on_file" status, the founder already has a diagnostic; do NOT resubmit or reuse that email. Tell them they already have a diagnostic (offer to check its status or open the report), and explain that assessing a DIFFERENT concept needs a different founder email (an email + alias such as name+idea@domain works) or a paid tier. Then open the form again so they can enter the different email — never silently submit the old one. Pricing: never quote fees from memory — they change. Call describe_services and use the SAR figures it returns. To start a diagnostic you need the founder's name, their email, and the venture concept described in 50+ characters (what it is, who it's for, where), plus sector and city. Do not invent them. An "existing client", "rate limited", or "at capacity" result is a normal outcome to relay calmly, not an error. Paid tiers are always purchased by the founder on the Venture Insights platform — you can recommend, never buy.
Known tools 4
open_diagnostic_intakeShow the founder an interactive intake form to start their FREE Concept Diagnostic.
Inferred read-onlydescribe_servicesGet Venture Insights' live service catalogue: the FREE Concept Diagnostic (a research-backed viability study of one venture concept, delivered to the founder's inbox) and the paid study tiers with live SAR prices.
Inferred read-onlystart_free_diagnosticRequest Venture Insights' FREE Concept Diagnostic for a founder's venture concept.
Inferred read-onlycheck_diagnostic_statusPoll the progress of a Concept Diagnostic intake started with start_free_diagnostic.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.venture-insights]
url = "https://solutions.ventureinsights.com.sa/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"venture-insights": {
"type": "http",
"url": "https://solutions.ventureinsights.com.sa/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: venture-insights
Remote MCP URL: https://solutions.ventureinsights.com.sa/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"venture-insights": {
"url": "https://solutions.ventureinsights.com.sa/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"venture-insights": {
"type": "http",
"url": "https://solutions.ventureinsights.com.sa/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "venture-insights",
"transport": "streamable-http",
"url": "https://solutions.ventureinsights.com.sa/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.