_ registry / mcp streamable-http · checked 2h ago

cymosoft

https://cymosoft.com

Registry code: 07c4a3a8547eaaed

api record

Tools for learning about Cymosoft JSC (AI-first software development company, Hanoi) and Japanese text utilities (character count, 全角/半角, 和暦/西暦). Case-study content is available in English and Japanese via the language argument.

endpoint
https://cymosoft.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is cymosoft live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is cymosoft free to use?
Yes — the hub reached it with no key and no payment.
What tools does cymosoft have?
6 tools: get_case_study, convert_fullwidth_halfwidth, convert_japanese_era, get_company_profile, list_case_studies, count_japanese_characters.
Is cymosoft safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.1%

90 days 99.1%· all time 99.1%

latency
98ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 470 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • count japanese characters
  • convert fullwidth and halfwidth text
  • convert japanese era years
  • read software company case studies
takes → gives
text → text, data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_company_profile reads open 2h ago

    Company profile of Cymosoft JSC (株式会社サイモソフト), an AI-first software development company in Hanoi, Vietnam serving international clients including the Japanese market.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "description": "Response language (default: en)"
        }
      }
    }
    arguments 13 lines
  • list_case_studies reads open 18h ago

    List Cymosoft's client project case studies (industry, engagement model, team size, tech stack). Use get_case_study for the full write-up.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "description": "Response language (default: en)"
        }
      }
    }
    arguments 13 lines
  • count_japanese_characters reads open 2h ago

    Count characters in Japanese (or any) text: total, excluding whitespace, and 原稿用紙 pages (400 chars/page).

    mcp-tool

    {
      "type": "object",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_case_study reads unknown 2h ago

    Full case study text by id (ids come from list_case_studies).

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Case study id, e.g. project1"
        },
        "language": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "description": "Response language (default: en)"
        }
      }
    }
    arguments 20 lines
  • convert_fullwidth_halfwidth reads unknown never probed

    Convert Japanese text between fullwidth (全角) and halfwidth (半角) forms for ASCII letters, digits, punctuation and spaces.

    mcp-tool

    {
      "type": "object",
      "required": [
        "text",
        "direction"
      ],
      "properties": {
        "text": {
          "type": "string"
        },
        "direction": {
          "enum": [
            "to_halfwidth",
            "to_fullwidth"
          ],
          "type": "string"
        }
      }
    }
    arguments 19 lines
  • convert_japanese_era reads unknown never probed

    Convert between Japanese era years (和暦: Reiwa/Heisei/Showa/Taisho/Meiji) and Western calendar years (西暦). Provide `year` for 西暦→和暦, or `era` + `era_year` for 和暦→西暦.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "era": {
          "type": "string",
          "description": "Era name, e.g. 令和 or Reiwa"
        },
        "year": {
          "type": "integer",
          "description": "Western year, e.g. 2026"
        },
        "era_year": {
          "type": "integer",
          "description": "Year within the era"
        }
      }
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 07c4a3a8547eaaed.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/07c4a3a8547eaaed/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/07c4a3a8547eaaed/badge.svg)](https://brick.blue/agent/07c4a3a8547eaaed?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.