Venture Foundry QA
REMOTE · VENTURE-FOUNDRY-QA.JENVAN.CHATGPT.SITE
Preflight QA for AI-agent deliverables with structured verdicts and repair guidance.
Available components
Last scanned (22 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Testing and QA
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 → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Sept 26 0
- Tool “venture_foundry_create_quote” changed its title: Create a Venture Foundry QA quote → Create a Preflight QA Lab quote cosmetic
- Tool “venture_foundry_get_report” changed its title: Read a paid Venture Foundry QA report → Read a paid Preflight QA Lab report cosmetic
- Tool “venture_foundry_prepare_checkout” changed its title: Prepare a Venture Foundry QA checkout → Prepare a Preflight QA Lab checkout cosmetic
- Tool “venture_foundry_service_info” changed its title: Describe Venture Foundry QA → Describe Preflight QA Lab cosmetic
4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://venture-foundry-qa.jenvan.chatgpt.site/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.jenvan.chatgpt.site | CN=WE1,O=Google Trust Services,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 358f25ee2583dd63136413d95ecb53f8 |
| SANs: *.jenvan.chatgpt.site | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of venture-foundry-qa.jenvan.chatgpt.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| site. | DS published | 31826 | 13 | Verified |
| chatgpt.site. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
| Header | Value |
|---|---|
| referrer-policy | no-referrer |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://venture-foundry-qa.jenvan.chatgpt.site/api/mcp | Auth required | 401 | |
| http (plaintext) | http://venture-foundry-qa.jenvan.chatgpt.site/api/mcp | HTTPS enforced | 302 | https://venture-foundry-qa.jenvan.chatgpt.site/api/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. 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 →
venture_foundry_create_quote Create a Preflight QA Lab quote ~99
Use before delivering a structured AI report, recommendation, research summary, or multi-agent handoff. Validate the QA job and bind a ten-minute quote to its exact content and paying Base wallet. This creates no transaction and moves no funds.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerAddress | string | yes | – |
| idempotencyKey | string | yes | Caller-generated unique key. Reuse it only when retrying the exact same operation. |
| job | object | yes | – |
No output schema declared.
No examples provided.
venture_foundry_get_report Read a paid Preflight QA Lab report ~61
Read one settled report using its job ID and secret bearer token. This tool cannot initiate payment.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
| reportToken | string | yes | Secret report token returned by prepare_checkout. Never disclose it outside the paying workflow. |
No output schema declared.
No examples provided.
venture_foundry_prepare_checkout Prepare a Preflight QA Lab checkout ~93
Reserve the unchanged quoted job and return one exact Base USDC transfer boundary plus a protected report token. This tool does not sign, approve, or submit the transfer.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerAddress | string | yes | – |
| idempotencyKey | string | yes | Caller-generated unique key. Reuse it only when retrying the exact same operation. |
| job | object | yes | – |
| quoteId | string | yes | – |
No output schema declared.
No examples provided.
venture_foundry_service_info Describe Preflight QA Lab ~51
Use this first when an agent needs pre-release AI output verification. Return the exact scope, price, schemas, examples, limitations, payment safety boundary, and integration links. This tool cannot move funds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
venture_foundry_settle_checkout Verify payment and release a QA report ~78
Verify an already-submitted Base transaction against the prepared exact-payment boundary and release its report. This tool cannot create or repeat a wallet transfer.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
| reportToken | string | yes | Secret report token returned by prepare_checkout. Never disclose it outside the paying workflow. |
| transaction | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Venture Foundry QA MCP server?
Venture Foundry QA is a hosted endpoint at https://venture-foundry-qa.jenvan.chatgpt.site/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · venture-foundry-qa.jenvan.chatgpt.site
claude mcp add --transport http ventureagent-ai-venture-foundry-qa 'https://venture-foundry-qa.jenvan.chatgpt.site/api/mcp'
What is the Venture Foundry QA MCP server?
Venture Foundry QA is an MCP server listed in the public MCP registry as io.github.ventureagent-ai/venture-foundry-qa. Preflight QA for AI-agent deliverables with structured verdicts and repair guidance. This page covers its hosted endpoint (https://venture-foundry-qa.jenvan.chatgpt.site/api/mcp).
Is the Venture Foundry QA MCP server safe to use?
Venture Foundry QA scores 33 out of 100 on VerifyMCP. 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 Venture Foundry QA MCP server expose?
Venture Foundry QA exposes 5 tools: venture_foundry_service_info, venture_foundry_create_quote, venture_foundry_prepare_checkout, venture_foundry_settle_checkout, venture_foundry_get_report. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.
Does the Venture Foundry QA MCP server require authentication?
Yes. Venture Foundry QA asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Venture Foundry QA MCP server still maintained?
Venture Foundry QA is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Venture Foundry QA MCP server?
VerifyMCP ran 5 checks on Venture Foundry QA, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Venture Foundry QA: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.