_ registry / mcp streamable-http · checked 53m ago

issoh-co-jp

https://www.issoh.co.jp

Registry code: d5fe82000671a308

api record

株式会社一創(issoh.co.jp)の公開情報を検索するサーバです。

システム開発・AI・クラウド・Web制作に関する日本語の技術記事、

endpoint
https://www.issoh.co.jp/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 issoh-co-jp live?
Yes — it answered the hub's last check (checked 53m ago). It answered 99% of checks over the last 30 days.
Is issoh-co-jp free to use?
Yes — the hub reached it with no key and no payment.
What tools does issoh-co-jp have?
5 tools: search_articles, get_article, search_case_studies, get_company_info, search_services.
Is issoh-co-jp 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.2%

90 days 99.2%· all time 99.2%

latency
313ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 374 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search japanese tech articles
  • read an article
  • search a development company's services
  • search case studies
takes → gives
text → text, data
tools
5 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 5 tools
3 open 2 never probed 3 of 5 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.

  • search_case_studies reads open 7h ago

    Search the published project portfolio (制作実績) and customer references (導入企業の声) of 株式会社一創. Use this to answer "do they have experience with X?" style questions.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 20,
          "minimum": 1,
          "description": "返す件数(1〜20、既定8)"
        },
        "query": {
          "type": "string",
          "description": "検索キーワード。省略すると新しい順に一覧する"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_company_info reads open 11h ago

    Return the company profile of 株式会社一創 and the canonical URLs for services, portfolio and the contact form. Use this when the user asks who they are or how to contact / request a quote.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_services reads open 11h ago

    Search the services offered by 株式会社一創 (system development, AI, web, DX consulting, infrastructure). Use this when the user is looking for a development vendor, a quote, or a partner for a specific technology. Omit the query to list every service.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 96,
          "minimum": 1,
          "description": "返す件数(省略時は10。全件見るときは大きめの値を渡す)"
        },
        "query": {
          "type": "string",
          "description": "検索キーワード。省略すると全サービスを一覧する。例: \"OCR\", \"SEO\", \"AWS\""
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • search_articles reads unknown 7h ago

    Search Japanese articles published on issoh.co.jp (株式会社一創). Covers system development, AI/LLM, cloud (AWS/Azure/GCP), security, and web. "column" = business/decision-maker oriented, "tech" = implementation oriented. Returns titles, URLs and excerpts. Call get_article afterwards to read the full text.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "返す件数(1〜20、既定5)"
        },
        "query": {
          "type": "string",
          "description": "検索キーワード(日本語可)。例: \"コンテナ オーケストレーション\", \"RAG 精度\""
        },
        "post_type": {
          "enum": [
            "any",
            "column",
            "tech"
          ],
          "type": "string",
          "default": "any",
          "description": "any=両方 / column=発注者向け / tech=実装者向け"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • get_article reads unknown 11h ago

    Fetch the full text of one issoh.co.jp article by URL or by id. Accepts URLs such as https://www.issoh.co.jp/column/details/16170/ or https://www.issoh.co.jp/tech/details/16216/. HTML is stripped and the body is truncated at 15000 characters.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "id": {
          "type": "integer",
          "description": "記事ID(url を使う場合は不要)"
        },
        "url": {
          "type": "string",
          "description": "記事URL(id を使う場合は不要)"
        },
        "post_type": {
          "enum": [
            "column",
            "tech"
          ],
          "type": "string",
          "description": "id 指定のときの投稿タイプ。url 指定なら不要"
        }
      },
      "additionalProperties": false
    }
    arguments 22 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 d5fe82000671a308.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d5fe82000671a308/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/d5fe82000671a308/badge.svg)](https://brick.blue/agent/d5fe82000671a308?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
90%

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.