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

Qiita MCP

https://qiita-com.fastmcp.app

Registry code: c476731c8f984784

api record

Qiita API と連携する Model Context Protocol (MCP) サーバです。

以下のツールを提供します:

endpoint
https://qiita-com.fastmcp.app/mcp
protocol
http-sse ·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 Qiita MCP live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Qiita MCP free to use?
Yes — the hub reached it with no key and no payment.
What tools does Qiita MCP have?
6 tools: post_qiita_article, update_qiita_article, search_qiita_items, get_my_qiita_articles, get_qiita_item, get_qiita_markdown_rules.
Is Qiita 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
100%

90 days 99.7%· all time 99.7%

latency
2,136ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 323 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
knowledge & reference
used for
  • search qiita articles
  • get a qiita article
  • post an article to qiita
  • update a qiita article
takes → gives
text → data, text
tools
4 reads2 changes data
_ 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
1 open 5 never probed 1 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_qiita_markdown_rules reads open 2h ago

    Qiita の Markdown 仕様やチートシートの参考リンクを返します（説明目的のリソース）。

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • post_qiita_article changes data unknown never probed

    Qiita に新規投稿します (POST /api/v2/items). 要アクセストークン(write_qiita) Args: title: 記事タイトル body: 本文 (Markdown) tags: 例: [{"name":"python","versions":["3.11"]}] private: 下書き/限定公開にしたい場合 True tweet: 投稿時にTwitter連携(現状Qiita側の仕様により無視されることがあります) organization_url_name: 組織アカウントに紐づけたい場合 Returns: 作成された記事オブジェクト

    mcp-tool

    {
  "type": "object",
  "required": [
    "title",
    "body"
  ],
  "properties": {
    "body": {
      "type": "string",
      "title": "Body"
    },
    "tags": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "object",
            "additionalProperties": true
          }
        },
        {
          "type": "null"
        }
      ],
      "title": "Tags",
      "default": null
    },
    "title": {
      "type": "string",
      "title": "Title"
    },
    "tweet": {
      "type": "boolean",
      "title": "Tweet",
      "default": false
    },
    "private": {
      "type": "boolean",
      "title": "Private",
      "default": false
    },
    "organization_url_name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Organization Url Name",
      "default": null
    }
  }
}
    arguments 55 lines
  • update_qiita_article changes data unknown never probed

    既存記事を更新します (PATCH /api/v2/items/:item_id). 要アクセストークン(write_qiita) 指定した項目のみ部分更新します。

    mcp-tool

    {
  "type": "object",
  "required": [
    "item_id"
  ],
  "properties": {
    "body": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Body",
      "default": null
    },
    "tags": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "object",
            "additionalProperties": true
          }
        },
        {
          "type": "null"
        }
      ],
      "title": "Tags",
      "default": null
    },
    "title": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Title",
      "default": null
    },
    "item_id": {
      "type": "string",
      "title": "Item Id"
    },
    "private": {
      "anyOf": [
        {
          "type": "boolean"
        },
        {
          "type": "null"
        }
      ],
      "title": "Private",
      "default": null
    }
  }
}
    arguments 64 lines
  • search_qiita_items reads unknown 14h ago

    Qiita 公開記事を検索します (GET /api/v2/items?query=...). Args: query: 検索クエリ（例: "tag:python fastmcp"） page: ページ番号 (1..) per_page: 件数 (1..100) Returns: results: [{id, title, url, likes_count, stocks_count, created_at, updated_at, user: {id, name}, tags:[...]}]

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "title": "Page",
      "default": 1
    },
    "query": {
      "type": "string",
      "title": "Query"
    },
    "per_page": {
      "type": "integer",
      "title": "Per Page",
      "default": 10
    }
  }
}
    arguments 22 lines
  • get_my_qiita_articles reads unknown 2h ago

    自分の投稿一覧を取得します (GET /api/v2/authenticated_user/items). 要アクセストークン(read_qiita)

    mcp-tool

    {
  "type": "object",
  "properties": {
    "page": {
      "type": "integer",
      "title": "Page",
      "default": 1
    },
    "per_page": {
      "type": "integer",
      "title": "Per Page",
      "default": 20
    }
  }
}
    arguments 15 lines
  • get_qiita_item reads unknown 2h ago

    記事IDで取得します (GET /api/v2/items/:item_id). Returns: {id, title, body(markdown), rendered_body(html), tags, url, user, ...}

    mcp-tool

    {
  "type": "object",
  "required": [
    "item_id"
  ],
  "properties": {
    "item_id": {
      "type": "string",
      "title": "Item Id"
    }
  }
}
    arguments 12 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 c476731c8f984784.

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

_ also on fastmcp.app 22 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

14 more sit on this domain. All of them.