GoNoGo
REMOTE · MCP.GONOGO.TEAM
Pressure-test a startup idea in a live voice interview with an AI mentor; get a GO/NO-GO verdict.
Available components
Last scanned (9 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability41
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 435 tokens (~87/item across 5 items; 4 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://mcp.gonogo.team/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.gonogo.team | CN=YE2,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 64f82556547568cb535caa5583d5366f9a3 |
| SANs: mcp.gonogo.team | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.gonogo.team. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| team. | present | 38380 | 8 | Verified |
| gonogo.team. | 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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.gonogo.team/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.gonogo.team/mcp | HTTPS enforced | 308 | https://mcp.gonogo.team/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 →
get_project_result Result of a GoNoGo project ~86
Use this when the user asks for the verdict, score or research status of one of their GoNoGo projects, for example after finishing an interview with Alex. Returns the GO / NO-GO verdict and score, or that the research is still running; the full reports are on the project page. Do not use to start a new interview.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| project | object | yes | – |
No examples provided.
interview_with_alex Pressure-test a startup idea with Alex ~260
Use this when the user wants to find out whether their own startup, app or business idea is worth building: whether there is a market, who has the problem and would pay for it, whether to quit a job or spend months on it, or to rehearse the questions an accelerator or investor will ask about the idea. Opens a live voice interview with Alex, GoNoGo's AI startup mentor (a talking video avatar): he asks who has the problem, what they do about it today, who pays and why now, and records the answers; GoNoGo then researches the market and competitors behind the answers and gives a GO / NO-GO verdict with reasons. One interview per idea: to compare several ideas, run one for each. Creates a project on the user's GoNoGo account. Do not use for running an existing business, writing a business plan document, naming or branding, coding help, or legal, tax or investment advice. The user taps Start and talks; stay silent while the interview runs.
| Name | Type | Req | Description |
|---|---|---|---|
| idea | string | – | The idea in the user's words, if they already said it |
| language | string | – | Interview language as an ISO 639-1 code (the language of the chat), default en |
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| project_url | string | yes | – |
No examples provided.
list_my_projects My GoNoGo projects ~54
Use this when the user asks about their GoNoGo projects: which ideas they have tested, their GO / NO-GO verdicts, or whether the research is still running. Do not use to start a new interview.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| projects | array | yes | – |
No examples provided.
whoami Your GoNoGo account ~19
Returns the GoNoGo account connected to ChatGPT.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No examples provided.
How do I install the GoNoGo MCP server?
GoNoGo is a hosted endpoint at https://mcp.gonogo.team/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 · mcp.gonogo.team
claude mcp add --transport http team-gonogo-gonogo 'https://mcp.gonogo.team/mcp'
What is the GoNoGo MCP server?
GoNoGo is an MCP server listed in the public MCP registry as team.gonogo/gonogo. Pressure-test a startup idea in a live voice interview with an AI mentor; get a GO/NO-GO verdict. This page covers its hosted endpoint (https://mcp.gonogo.team/mcp).
Is the GoNoGo MCP server safe to use?
GoNoGo scores 78 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 GoNoGo MCP server expose?
GoNoGo exposes 4 tools: whoami, interview_with_alex, list_my_projects, get_project_result. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.
Does the GoNoGo MCP server require authentication?
No. We connected to GoNoGo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GoNoGo MCP server still maintained?
GoNoGo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.