Cymosoft
REMOTE · CYMOSOFT.COM · SCANNED AUG 3
Cymosoft JSC profile and case studies (EN/JA) plus Japanese text utilities (文字数・全角半角・和暦)
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 Security46
- 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 6 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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 443 tokens (~73/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 · cymosoft.com
claude mcp add --transport http com-cymosoft-cymosoft https://cymosoft.com/mcp
[mcp_servers.com-cymosoft-cymosoft] url = "https://cymosoft.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-cymosoft-cymosoft": {
"type": "remote",
"url": "https://cymosoft.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-cymosoft-cymosoft --url https://cymosoft.com/mcp --transport streamable-http
mcp_servers:
com-cymosoft-cymosoft:
url: "https://cymosoft.com/mcp" {
"mcpServers": {
"com-cymosoft-cymosoft": {
"type": "http",
"url": "https://cymosoft.com/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.
- 3 Aug 26 54
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 3 Aug 2026 · Probed https://cymosoft.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cymosoft.com | CN=WE1,O=Google Trust Services,C=US | 2 Aug 2026 | 31 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 84da1a8fc846ae11373c69579da4ebc |
| SANs: cymosoft.com, *.cymosoft.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 insecure
Validation of cymosoft.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cymosoft.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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cymosoft.com/mcp | Verified | 200 | |
| http (plaintext) | http://cymosoft.com/mcp | Inconclusive | 405 |
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.
convert_fullwidth_halfwidth Convert 全角⇔半角 ~53
Convert Japanese text between fullwidth (全角) and halfwidth (半角) forms for ASCII letters, digits, punctuation and spaces.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | — |
| text | string | yes | — |
No output schema declared.
No examples provided.
convert_japanese_era Convert 和暦⇔西暦 ~124
Convert between Japanese era years (和暦: Reiwa/Heisei/Showa/Taisho/Meiji) and Western calendar years (西暦). Provide `year` for 西暦→和暦, or `era` + `era_year` for 和暦→西暦.
| Name | Type | Req | Description |
|---|---|---|---|
| era | string | — | Era name, e.g. 令和 or Reiwa |
| era_year | integer | — | Year within the era |
| year | integer | — | Western year, e.g. 2026 |
No output schema declared.
No examples provided.
count_japanese_characters Count Japanese characters (文字数カウント) ~44
Count characters in Japanese (or any) text: total, excluding whitespace, and 原稿用紙 pages (400 chars/page).
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | — |
No output schema declared.
No examples provided.
get_case_study Get one Cymosoft case study ~54
Full case study text by id (ids come from list_case_studies).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Case study id, e.g. project1 |
| language | string | — | Response language (default: en) |
No output schema declared.
No examples provided.
get_company_profile Get Cymosoft company profile ~56
Company profile of Cymosoft JSC (株式会社サイモソフト), an AI-first software development company in Hanoi, Vietnam serving international clients including the Japanese market.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | — | Response language (default: en) |
No output schema declared.
No examples provided.
list_case_studies List Cymosoft case studies ~55
List Cymosoft's client project case studies (industry, engagement model, team size, tech stack). Use get_case_study for the full write-up.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | — | Response language (default: en) |
No output schema declared.
No examples provided.