FounderBrain
REMOTE · MCP.THINKREASONLEARN.COM
See how a founder came across in a pitch or investor call, compared with 773 founder interviews.
Available components
Last scanned (6 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Education and Research
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 Usability32
- 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
- Context-footprint check failed: tool/resource definitions use about 1452 tokens (~242/item across 6 items; 3 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 3 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 current MCP spec version (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.
- 24 Oct 26 0
- Resource “FounderBrain report” now points somewhere else: ui://founderbrain/panel-18.html → ui://founderbrain/panel-17.html security
- Resource “FounderBrain report” now points somewhere else: ui://founderbrain/panel-16.html → ui://founderbrain/panel-17.html security
- 23 Oct 26 +1
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “open_in_terminal” was removed ▼ security
- Resource “FounderBrain report” now points somewhere else: ui://founderbrain/panel-16.html → ui://founderbrain/panel-17.html security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 286 → 242 ▲ functional
- New tool “get_transcript_upload_command” functional
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “analyse_transcript” rewrote its description, which is the text the model reads security
- Tool “check_transcript” rewrote its description, which is the text the model reads security
- Tool “open_in_terminal” rewrote its description, which is the text the model reads security
- Schema quality: 235 → 286 ▼ functional
- 20 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “analyse_transcript” rewrote its description, which is the text the model reads security
- Tool “check_transcript” rewrote its description, which is the text the model reads security
- Tool coverage: 67% → 100% ▲ functional
- Tool “analyse_transcript” now declares an output schema ▲ functional
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 14 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 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 24 Oct 2026 · Probed https://mcp.thinkreasonlearn.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.thinkreasonlearn.com | CN=WR3,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | ed053a013ef1ce4f097f271e5a6d03b4 |
| SANs: mcp.thinkreasonlearn.com | ||||||
| CN=WR3,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 | 7ff005a91568d63abc22861684aa4b5a |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.thinkreasonlearn.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| thinkreasonlearn.com. | 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 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.thinkreasonlearn.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.thinkreasonlearn.com/mcp | HTTPS enforced | 302 | https://mcp.thinkreasonlearn.com/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 →
analyse_transcript Analyse a meeting transcript ~255
Compare one speaker in a meeting transcript with public founder and operator interviews and return the report as data: speaking type, style positions, similar well-known people, standout habits and takeaways. transcript: the complete prepared transcript, never just a file preview, one speaker turn per line ("Name: words"). Restricted information must be removed before transfer, as described in the server instructions; a user-selected excerpt is allowed. speaker: one speaker label as it appears in the text. name: the person's display name when the label is generic (Me, Them, Speaker 2), or "You" when the speaker is the user; required for a generic label other than Me. role: "answering" when they were pitching or answering questions, "asking" when they mostly asked them. Needs at least 300 words from the speaker and at most 15,000 words in all; usually takes under a minute, up to about two minutes when the service is starting up. Clients that support MCP Apps also show the visual report.
| Name | Type | Req | Description |
|---|---|---|---|
| name | – | – | – |
| role | string | – | – |
| speaker | string | – | – |
| transcript | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| archetype | object | yes | The speaking type: name, sketch, description and best-known members. |
| closest_match | object | yes | The well-known founder or operator whose style is closest. |
| coverage | object | yes | How much of the transcript was analysed, and whether the result is settled. |
| headline | string | yes | One line on where the speaker differs most from the reference interviews. |
| how_to_read | object | – | – |
| how_to_use | string | – | How the assistant should coach from these results. |
| least_like_you | object | – | The well-known person whose style is least alike. |
| method | string | – | – |
| note | string|null | – | A note on reading the report, such as for a speaker who mostly asked questions. |
| person | string | yes | The speaker as named in the report. |
| role | string | yes | – |
| similar_people | array | – | Other well-known people with a similar style, with match percentages. |
| speaker | string | yes | The speaker label analysed, as it appears in the transcript. |
| standout_habits | array | – | Habits whose rate differs most from the reference interviews. |
| styles | array | yes | Positions on four speaking styles, as percentiles against the reference interviews. |
| takeaways | array | yes | What to try next time and what to keep. |
| words_received | integer | yes | Words in the transcript received. |
No examples provided.
check_transcript List the speakers in a transcript ~90
List the speakers in a meeting transcript and how many words each said, without scoring anything. transcript: the complete prepared transcript, never just a file preview, one speaker turn per line ("Name: words"). This tool also receives the text: restricted information must be removed before transfer, as described in the server instructions. A user-selected excerpt is allowed.
| Name | Type | Req | Description |
|---|---|---|---|
| transcript | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_transcript_upload_command Get a transcript upload command ~189
Return a curl upload command as text for a prepared local transcript copy. The caller runs the command in the user's terminal to send the copy to FounderBrain. This tool only constructs the command; it does not open a terminal, read the file, upload data or execute anything. path: the full local path of a temporary plain-text copy prepared by the client, containing only speaker turns with restricted information removed before upload. The tool does not inspect or clean the file. speaker, name and role: the speaker label to analyse, the person's display name when the label is generic, and "answering" or "asking". Without a speaker the command only lists the speakers and their word counts.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| path | string | yes | – |
| role | string | – | – |
| speaker | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the FounderBrain MCP server?
FounderBrain is a hosted endpoint at https://mcp.thinkreasonlearn.com/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.thinkreasonlearn.com
claude mcp add --transport http com-thinkreasonlearn-founderbrain 'https://mcp.thinkreasonlearn.com/mcp'
What is the FounderBrain MCP server?
FounderBrain is an MCP server listed in the public MCP registry as com.thinkreasonlearn/founderbrain. See how a founder came across in a pitch or investor call, compared with 773 founder interviews. This page covers its hosted endpoint (https://mcp.thinkreasonlearn.com/mcp).
Is the FounderBrain MCP server safe to use?
FounderBrain scores 72 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 FounderBrain MCP server expose?
FounderBrain exposes 3 tools: analyse_transcript, get_transcript_upload_command, check_transcript. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.
Does the FounderBrain MCP server require authentication?
No. We connected to FounderBrain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FounderBrain MCP server still maintained?
FounderBrain is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.