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

manda

https://manda.bz

Registry code: e2c7669f32ea0da5

api record

MANDA (https://manda.bz) はスモールM&Aのマーケットプレイスです。

このサーバーでは公開中の売り案件(会社・事業の売却希望)を検索・閲覧できます。

endpoint
https://manda.bz/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 manda live?
Yes — it answered the hub's last check (checked 58m ago). It answered 99% of checks over the last 30 days.
Is manda free to use?
Yes — the hub reached it with no key and no payment.
What tools does manda have?
4 tools: get_deal, list_areas, list_industries, search_deals.
Is manda 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
98.9%

90 days 99.2%· all time 99.2%

latency
577ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 497 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· HTTP 500
  • degraded → live
_ what it is for
used for
  • search small business sale listings
  • get details of an m&a deal
  • list industries and regions for deal search
takes → gives
text → data
tools
4 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 4 tools
3 open 1 never probed 3 of 4 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_areas reads open 12h ago

    地域マスタ(地方・都道府県)の一覧を返す。search_deals の areaId にはここで得た ID を指定する。

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • list_industries reads open 12h ago

    業種マスタの一覧を返す。search_deals に業種IDフィルタはないため、絞り込みたい場合はここで得た業種名を query のキーワードとして使う。

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • search_deals reads open 12h ago

    MANDA の公開中の売り案件(M&A・事業承継)をキーワード・地域・売上規模・譲渡額などで検索する。結果は1ページ20件。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "integer",
          "description": "ページ番号(1始まり)。省略時は1"
        },
        "sort": {
          "type": "string",
          "description": "date を指定すると新着順。省略時は関連度順"
        },
        "query": {
          "type": "string",
          "description": "検索キーワード。案件名・業種名・本文にマッチする。スペース区切りで複数指定可"
        },
        "areaId": {
          "type": "string",
          "description": "地域ID。list_areas で得られる地方ID(例: 300)または都道府県ID(例: 306)"
        },
        "priceRange": {
          "type": "string",
          "description": "譲渡希望額レンジ(万円): lt1000 / 1000to5000 / 5000to10000 / 10000to50000 / 50000to100000 / gt100000 / gt10000(1億以上すべて)"
        },
        "salesRange": {
          "type": "string",
          "description": "売上高レンジ(万円): lt1000 / 1000to5000 / 5000to10000 / 10000to50000 / 50000to100000 / gt100000 / gt10000(1億以上すべて)"
        },
        "sellerType": {
          "type": "string",
          "description": "owner を指定すると売り手本人が MANDA に直接掲載した案件のみに絞り込む"
        },
        "successionOnly": {
          "type": "boolean",
          "description": "true で事業承継案件(後継者不在が売却理由=高齢経営者の事業承継)のみに絞り込む"
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • get_deal reads unknown 20h ago

    売り案件1件の詳細(事業内容の全文・属性情報など)を取得する。domain と localId は search_deals の結果から得る。

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain",
        "localId"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "search_deals の結果の domain"
        },
        "localId": {
          "type": "string",
          "description": "search_deals の結果の localId"
        }
      },
      "additionalProperties": false
    }
    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 e2c7669f32ea0da5.

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

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.