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

tsuyoshikashiwazaki-mcp

https://mcp.tsuyoshikashiwazaki.jp

Registry code: 6f3a58198bd67e81

api record

SEO対策研究室（運営: 株式会社コンテンシャル / サイト責任者: 柏崎剛、www.tsuyoshikashiwazaki.jp）の**公開情報のみ**を検索・取得する読み取り専用サーバーです。回答の出典には必ず canonical_url（https://www.tsuyoshikashiwazaki.jp/...）を使ってください。根拠のないサイト運営側の見解を推測で作らないでください。SEO成果・検索順位・効果は保証できません。具体的な数値・実績は、公開ページに記載がある場合のみ、書かれているとおりに伝えてください（推測で補わないこと）。

## 使い分け

endpoint
https://mcp.tsuyoshikashiwazaki.jp
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 tsuyoshikashiwazaki-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is tsuyoshikashiwazaki-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does tsuyoshikashiwazaki-mcp have?
6 tools: search_tsuyoshikashiwazaki_content, research_tsuyoshikashiwazaki_viewpoint, read_tsuyoshikashiwazaki_content, list_recent_tsuyoshikashiwazaki_content, get_tsuyoshikashiwazaki_services, get_tsuyoshikashiwazaki_profile.
Is tsuyoshikashiwazaki-mcp 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.4%

90 days 99.3%· all time 99.3%

latency
892ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 291 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business marketing & seo
used for
  • search seo articles from a japanese seo lab
  • read an seo article in full
  • research the site's view on an seo topic
  • list recent seo content
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.

  • list_recent_tsuyoshikashiwazaki_content reads open 13h ago

    更新日の新しい順に公式コンテンツを一覧します。「最近どんな発信をしているか」を検索語なしで確認する用途です。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "since": {
      "type": "string",
      "description": "この日付以降に更新されたもの (YYYY-MM-DD)。"
    },
    "content_types": {
      "type": "array",
      "items": {
        "enum": [
          "company",
          "policy",
          "member",
          "service",
          "blog",
          "report",
          "casestudy",
          "news"
        ],
        "type": "string"
      }
    }
  }
}
    arguments 30 lines
  • get_tsuyoshikashiwazaki_services reads open 13h ago

    業種別SEO・教育SEO等の取り組みページの一覧と各説明・canonical URL を返します。

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_tsuyoshikashiwazaki_profile reads open 13h ago

    サイト概要・サイト責任者（柏崎剛）のプロフィール・プライバシーポリシーと、検証事例一覧を返します。

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_tsuyoshikashiwazaki_content reads unknown 6h ago

    SEO対策研究室（運営: 株式会社コンテンシャル / サイト責任者: 柏崎剛、www.tsuyoshikashiwazaki.jp）の公開情報（SEO解説記事・用語辞典・検証事例・業種別SEOの取り組み・運営者プロフィール・お知らせ）を横断検索します。結果には canonical URL・種別・情報源の分類・更新日・該当箇所が含まれます。

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "検索クエリ。日本語可。"
    },
    "author": {
      "type": "string",
      "description": "著者名の部分一致。"
    },
    "published_to": {
      "type": "string",
      "description": "公開日の上限 (YYYY-MM-DD)。"
    },
    "content_types": {
      "type": "array",
      "items": {
        "enum": [
          "company",
          "policy",
          "member",
          "service",
          "blog",
          "report",
          "casestudy",
          "news"
        ],
        "type": "string"
      },
      "description": "絞り込むコンテンツ種別。"
    },
    "published_from": {
      "type": "string",
      "description": "公開日の下限 (YYYY-MM-DD)。"
    }
  }
}
    arguments 48 lines
  • research_tsuyoshikashiwazaki_viewpoint reads unknown never probed

    特定テーマに対する SEO対策研究室（サイト責任者: 柏崎剛）の考え方・解説を調べます。根拠をサイトポリシー／取り組み説明／解説記事／運営者見解に分類し、確信度を添えて返します。根拠がない場合は confidence="none" を返します。

    mcp-tool

    {
  "type": "object",
  "required": [
    "topic"
  ],
  "properties": {
    "topic": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    },
    "max_evidence": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1
    }
  }
}
    arguments 18 lines
  • read_tsuyoshikashiwazaki_content reads unknown 6h ago

    公開コンテンツ1件の全文とメタデータを返します。content_id か canonical URL で指定します。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 500
    },
    "max_chars": {
      "type": "integer",
      "maximum": 200000,
      "minimum": 500
    },
    "content_id": {
      "type": "string",
      "maxLength": 200
    }
  }
}
    arguments 18 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 6f3a58198bd67e81.

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