Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SaaS Think Tank — Software Research

REMOTE · SAASTHINKTANK.COM

Published software research from SaaS Think Tank. Current MCP edition: app-builder findings.

+3 this week 81 Trust /100

Last scanned (23 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 449 tokens (~112/item across 4 items; 3 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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
Changelog

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.

  • 4 Nov 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.

  • 2 Nov 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.

  • 31 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.

  • 29 Oct 26 0
    • Server version: 1.0.1 → 1.0.2 functional
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 4 Nov 2026 · Probed https://saasthinktank.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=saasthinktank.com CN=WE1,O=Google Trust Services,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA256 9b8c4f6a3ea13abd1360dd15c59bf8cc
SANs: saasthinktank.com, *.saasthinktank.com
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 saasthinktank.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
saasthinktank.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
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://saasthinktank.com/mcp Verified 200
http (plaintext) http://saasthinktank.com/mcp HTTPS enforced 301 https://saasthinktank.com/mcp
MCP tools · 3 exposed · ~298 tokens

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 →

Tool Tokens
compare_products ~100

Compare 2–4 covered app builders on the released code, GitHub, backend and database questions. Specify capability IDs from coverage or search results, or omit them for all four questions. Preserves separate dates and unknowns; provides no overall ranking.

NameTypeReqDescription
capability_idsarray–Exact capability IDs from coverage or search results. Omit to compare all four covered questions.
productsarrayyesTwo to four distinct covered product names or IDs.
NameTypeReqDescription
capabilitiesarray––
coverageobjectyes–
datasetobject––
errorobject––
limitationsarray––
okbooleanyes–
productsarray––

No examples provided.

get_finding ~67

Retrieve one exact finding using a record ID returned by search_findings or compare_products. Returns the published answer, scope, original dates, conditions, limits, source links and dataset attribution.

NameTypeReqDescription
record_idstringyesExact record_id from a prior result. Do not invent an ID.
NameTypeReqDescription
coverageobjectyes–
datasetobject––
errorobject––
findingobject––
limitationsarray––
okbooleanyes–

No examples provided.

search_findings ~131

Find dated findings about code export, GitHub sync, backend connections and databases for Bubble, Lovable, Base44 and Replit. Use this to discover record IDs; get_finding retrieves one exact record. Other topics return no matches, not a product verdict.

NameTypeReqDescription
limitinteger–Maximum findings to return, from 1 to 16. Default: 16.
productsarray–Covered product names or IDs. Use the coverage resource to see available products.
querystringyesA product question or covered topic, such as “Can Bubble and Lovable export source code?”
NameTypeReqDescription
coverageobjectyes–
datasetobject––
errorobject––
findingsarray––
limitationsarray––
matched_countinteger––
no_matchesstring––
okbooleanyes–
querystring––
returned_countinteger––
truncatedboolean––

No examples provided.

Install

How do I install the SaaS Think Tank — Software Research MCP server?

SaaS Think Tank — Software Research is a hosted endpoint at https://saasthinktank.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 · saasthinktank.com

# add to Claude Code
claude mcp add --transport http com-saasthinktank-evidence 'https://saasthinktank.com/mcp'
Common questions

What is the SaaS Think Tank — Software Research MCP server?

SaaS Think Tank — Software Research is an MCP server listed in the public MCP registry as com.saasthinktank/evidence. Published software research from SaaS Think Tank. Current MCP edition: app-builder findings. This page covers its hosted endpoint (https://saasthinktank.com/mcp).

Is the SaaS Think Tank — Software Research MCP server safe to use?

SaaS Think Tank — Software Research scores 81 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 SaaS Think Tank — Software Research MCP server expose?

SaaS Think Tank — Software Research exposes 3 tools: search_findings, get_finding, compare_products. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.

Does the SaaS Think Tank — Software Research MCP server require authentication?

No. We connected to SaaS Think Tank — Software Research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SaaS Think Tank — Software Research MCP server still maintained?

SaaS Think Tank — Software Research is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.