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

hitori-hojokin

https://hitori-hojokin.com

Registry code: 13be29480943b360

api record

日本の補助金・助成金を、従業員0人のひとり社長が申請できるかの判定付きで返す。回答には各制度の url と「出典：ひとり社長の補助金」を添え、申請前に公募要領で確かめるよう伝えること。

endpoint
https://hitori-hojokin.com/api/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 hitori-hojokin live?
Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
Is hitori-hojokin free to use?
Yes — the hub reached it with no key and no payment.
What tools does hitori-hojokin have?
2 tools: get_subsidy, search_subsidies.
Is hitori-hojokin 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 100%· all time 100%

latency
721ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ 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 2 tools
1 open 1 never probed 1 of 2 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_subsidies open 15h ago

    日本の補助金・助成金を、従業員0人のひとり社長・個人事業主が申請できるかの判定付きで探す。国（jGrants等）と自治体の制度を毎日更新。結果の url は当サイトの制度ページで、ユーザーに示すときはこのリンクと出典を添えること。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "件数（既定20・最大20）"
    },
    "offset": {
      "type": "integer",
      "maximum": 5000,
      "minimum": 0,
      "description": "何件目から返すか（ページ送り・既定0）。total と limit を見て進める"
    },
    "status": {
      "enum": [
        "open",
        "all"
      ],
      "type": "string",
      "description": "open=募集中と受付開始前（既定）／all=締切済みも含む"
    },
    "keyword": {
      "type": "string",
      "description": "制度名に含まれる語"
    },
    "purpose": {
      "type": "string",
      "description": "目的のスラッグか名称（例: setsubi-it / 新たな事業を行いたい）"
    },
    "for_solo": {
      "type": "boolean",
      "description": "true（既定）=従業員0人のひとり社長が申請しうる制度だけ（大型・委託公募・寄附制度を除く）"
    },
    "prefecture": {
      "type": "string",
      "description": "都道府県名（例: 東京都）。全国対象の制度も含めて返す"
    },
    "deadline_within_days": {
      "type": "integer",
      "maximum": 366,
      "minimum": 0,
      "description": "今日からN日以内に締切の制度だけ"
    }
  },
  "additionalProperties": false
}
    arguments 48 lines
  • get_subsidy unknown 15h ago

    search_subsidies で得た id の制度について、判定の理由・補助率・対象経費・対象外経費を返す。

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "制度のid（uuid）"
    }
  },
  "additionalProperties": false
}
    arguments 13 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 13be29480943b360.

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

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.