SynergyBoat
REMOTE · WWW.SYNERGYBOAT.COM · SCANNED AUG 17
SynergyBoat's public company data — services, case studies, AI use cases, team — and lead capture.
Available components
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 →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 627 tokens (~69/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.synergyboat.com
claude mcp add --transport http com-synergyboat-website https://www.synergyboat.com/api/mcp
[mcp_servers.com-synergyboat-website] url = "https://www.synergyboat.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-synergyboat-website": {
"type": "remote",
"url": "https://www.synergyboat.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-synergyboat-website --url https://www.synergyboat.com/api/mcp --transport streamable-http
mcp_servers:
com-synergyboat-website:
url: "https://www.synergyboat.com/api/mcp" {
"mcpServers": {
"com-synergyboat-website": {
"type": "http",
"url": "https://www.synergyboat.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Aug 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.
- 15 Aug 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.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 67
First indexed and scored.
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 17 Aug 2026 · Probed https://www.synergyboat.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=synergyboat.com | CN=WE1,O=Google Trust Services,C=US | 16 Jul 2026 | 14 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 49026ade73c5c657136ee3a7791117d9 |
| SANs: synergyboat.com, www.synergyboat.com, *.www.synergyboat.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 |
DNSSEC secure
Validation of www.synergyboat.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| synergyboat.com. | present | 2371 | 13 | Verified |
| www.synergyboat.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.synergyboat.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.synergyboat.com/api/mcp | HTTPS enforced | 301 | https://www.synergyboat.com/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.
get_case_study ~40
Get one SynergyBoat case study by slug from list_case_studies.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Case-study slug from list_case_studies. |
No output schema declared.
No examples provided.
get_company_overview ~37
Get a factual overview of SynergyBoat: what the company does, founders, contact channels, service areas, and verified client rating.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_service ~53
Get one SynergyBoat service in full, by id from list_services.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Service id from list_services. |
| locale | string | – | Optional localized content variant. Defaults to the global English content. |
No output schema declared.
No examples provided.
list_ai_use_cases ~35
List SynergyBoat AI capabilities and use cases as shown on the AI hub: slug, title, category, and overview.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_case_studies ~52
List SynergyBoat case studies: slug, title, client, industry, and outcome summary. Use get_case_study for one in full.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20). |
No output schema declared.
No examples provided.
list_services ~55
List SynergyBoat services as shown on synergyboat.com: id, name, and outcome summary for each. Use get_service for full details.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Optional localized content variant. Defaults to the global English content. |
No output schema declared.
No examples provided.
list_team ~39
List the SynergyBoat team as shown on synergyboat.com/team: name, title, whether the person is leadership, expertise, and public profile links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_demo ~140
Request a SynergyBoat demo (name, email, consent; optional company, context, and AI use case of interest). Creates a lead the team follows up on. Requires explicit user consent.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Optional company name. |
| consent | boolean | yes | Must be true to confirm consent to submit lead details. |
| context | string | – | Optional context on the workflow/bottleneck to discuss in the demo. |
| string | yes | Work email used for follow-up. | |
| name | string | yes | Full name of the person requesting the demo. |
| useCase | string | – | Optional AI use case of interest (slug or title). |
No output schema declared.
No examples provided.
submit_lead ~137
Submit a contact enquiry to SynergyBoat (name, email, enquiry, consent; optional company). Creates a lead the team follows up on. Requires explicit user consent.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Optional company or organisation name. |
| consent | boolean | yes | Must be true to confirm consent to Privacy Policy and Terms of Service. |
| string | yes | Business or personal email for follow-up. | |
| enquiry | string | yes | Enquiry details, goals, and what support is required. |
| name | string | yes | Full name of the person submitting the enquiry. |
| transcript | string | – | Optional transcript captured from voice or chat interactions. |
No output schema declared.
No examples provided.