株式会社一創コーポレートサイト

REMOTE · WWW.ISSOH.CO.JP · SCANNED AUG 20

株式会社一創（issoh.co.jp）の技術記事・サービス・制作実績を検索できる MCP サーバー。システム開発・AI・クラウド・Web 制作の日本語情報

Available components

64 64 Trust /100

Trust breakdown (6 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 →

Endpoint Security63

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 5 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 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 Usability76

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 721 tokens (~144/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

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.issoh.co.jp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http jp-co-issoh-corporate-site https://www.issoh.co.jp/mcp

# ~/.codex/config.toml

[mcp_servers.jp-co-issoh-corporate-site]
url = "https://www.issoh.co.jp/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jp-co-issoh-corporate-site": {
      "type": "remote",
      "url": "https://www.issoh.co.jp/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add jp-co-issoh-corporate-site --url https://www.issoh.co.jp/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  jp-co-issoh-corporate-site:
    url: "https://www.issoh.co.jp/mcp"

// mcp.json

{
  "mcpServers": {
    "jp-co-issoh-corporate-site": {
      "type": "http",
      "url": "https://www.issoh.co.jp/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

20 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
19 Aug 26 63

First indexed and scored.

Show 1 earlier entry Hide earlier entries

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 20 Aug 2026 · Probed https://www.issoh.co.jp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=issoh.co.jp	CN=WE1,O=Google Trust Services,C=US	16 Aug 2026	14 Nov 2026	ECDSA 256	ECDSA-SHA256	cb806419f49f80cf0e5c6ac40b56b97d
SANs: issoh.co.jp, *.issoh.co.jp
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 www.issoh.co.jp. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
jp.	present	33631	8	Verified
co.jp.	absent			Delegated
issoh.co.jp.	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
strict-transport-security	max-age=15552000
x-content-type-options	nosniff

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://www.issoh.co.jp/mcp	Verified	200
http (plaintext)	http://www.issoh.co.jp/mcp	HTTPS enforced	301	https://www.issoh.co.jp/mcp

MCP tools · 5 exposed · ~573 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.

Tool Tokens

get_article 記事の本文を取得する ~136

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.

Input Output Examples

Name	Type	Req	Description
id	integer	–	記事ID（url を使う場合は不要）
post_type	string	–	id 指定のときの投稿タイプ。url 指定なら不要
url	string	–	記事URL（id を使う場合は不要）

No output schema declared.

No examples provided.

get_company_info 会社情報と問い合わせ先を取得する ~50

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.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_articles 記事を検索する ~163

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.

Input Output Examples

Name	Type	Req	Description
limit	integer	–	返す件数（1〜20、既定5）
post_type	string	–	any=両方 / column=発注者向け / tech=実装者向け
query	string	yes	検索キーワード（日本語可）。例: "コンテナオーケストレーション", "RAG 精度"

No output schema declared.

No examples provided.

search_case_studies 制作実績・導入事例を検索する ~95

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

Input Output Examples

Name	Type	Req	Description
limit	integer	–	返す件数（1〜20、既定8）
query	string	–	検索キーワード。省略すると新しい順に一覧する

No output schema declared.

No examples provided.

search_services サービスを検索する ~129

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.

Input Output Examples

Name	Type	Req	Description
limit	integer	–	返す件数（省略時は10。全件見るときは大きめの値を渡す）
query	string	–	検索キーワード。省略すると全サービスを一覧する。例: "OCR", "SEO", "AWS"

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

19 Aug 20 Aug