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

bumit

https://bumit.ai

Registry code: a75d6e9e5eb3e20b

api record

Swiss business verification with per-check source provenance and evidence freshness.

from a public catalogue that lists it, not from the operator

endpoint
https://bumit.ai/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 bumit live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is bumit free to use?
Yes — the hub reached it with no key and no payment.
What tools does bumit have?
3 tools: get_company_profile, verify_business, search_companies.
Is bumit 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.4%· all time 99.4%

latency
1,120ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 179 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • verify a swiss business by uid or name
  • check a company's registry evidence
takes → gives
text → data
tools
1 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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_company_profile unknown 11h ago

    Retrieve the canonical Swiss commercial-register (Zefix) profile for one company by UID: legal name, legal form, register status, seat, canton, registered address, purpose and official register links, with provenance, attribution and a freshness envelope (evidence age, freshness threshold, stale flag and source state). The UID is normalized and its check digit validated before any source request. FOUND means a register record was retrieved, not that the business passed verification. For sanctions, FINMA and full verification outcomes, use verify_business.

    mcp-tool

    {
      "type": "object",
      "required": [
        "uid"
      ],
      "properties": {
        "uid": {
          "type": "string",
          "description": "Swiss UID (e.g. CHE-116.281.549). Formatting is normalized; the mod-11 check digit is validated before any source request."
        }
      },
      "description": "Retrieve the canonical Swiss commercial-register (Zefix) profile for one company by UID. Retrieval only: FOUND means a register record was retrieved, not that the business passed verification.",
      "additionalProperties": false
    }
    arguments 14 lines
  • verify_business reads unknown never probed

    Verify a Swiss company using official commercial-register data (Zefix), SECO sanctions data, and FINMA authorisation data. Search by UID or company name (optionally narrowed by address); a UID is not required. Returns structured verification outcomes, source provenance, and data freshness. If a name matches multiple companies, returns candidates for the agent or user to disambiguate; never assume a partial match is the intended company. Unavailable evidence must not be interpreted as a failed verification.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "uid": {
          "type": "string",
          "pattern": "^[\\s._/-]*[Cc][\\s._/-]*[Hh][\\s._/-]*[Ee](?:[\\s._/-]*[0-9]){9}[\\s._/-]*$",
          "maxLength": 64,
          "description": "Optional Swiss UID, canonical (CHE-123.456.789) or compact (CHE123456789). When present it identifies the company directly. Check digit validated server-side; an invalid UID is rejected before any source lookup."
        },
        "name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Optional company legal name; use it when no UID is known. Name-only resolution needs at least 3 characters. A company is resolved only on a unique exact normalized legal-name match — never fuzzy. Otherwise candidates are returned for explicit selection: do not guess; resubmit with the chosen candidate's uid. With uid, the name is compared against the registered name instead."
        },
        "address": {
          "type": "object",
          "required": [
            "street",
            "house_number",
            "postcode",
            "locality"
          ],
          "properties": {
            "street": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1,
              "description": "Street name, without house number."
            },
            "locality": {
              "type": "string",
              "maxLength": 100,
              "minLength": 1,
              "description": "Locality (town). Also compared with the registered seat when narrowing exact name matches."
            },
            "postcode": {
              "type": "string",
              "maxLength": 10,
              "minLength": 1,
              "description": "Postcode."
            },
            "house_number": {
              "type": "string",
              "maxLength": 20,
              "minLength": 1,
              "description": "House number."
            }
          },
          "description": "Optional Swiss postal address; all four fields are required when address is supplied. It is checked against the official building-address directory (this never proves the company is at that address). With name, locality may narrow several exact legal-name matches by registered seat; it never turns a non-exact match into an identity. Address alone cannot identify a company.",
          "additionalProperties": false
        }
      },
      "description": "Identify a Swiss company by uid or name; supply at least one of them. A uid is not required when a name is given. address is optional and only assists; address alone is not supported (result outcome UNSUPPORTED). If uid is given, it identifies the company and a supplied name is checked against the registered name. Only uid, name and address are accepted.",
      "minProperties": 1,
      "additionalProperties": false
    }
    arguments 57 lines
  • search_companies unknown 11h ago

    Search the Swiss commercial register (Zefix) by company name and receive bounded, deduplicated candidate summaries (UID, legal name, legal form, register status, seat, canton) with source attribution. Use this to find a company's UID before calling get_company_profile, or to review candidates after verify_business reports an ambiguous name. Discovery only: no candidate is selected automatically, results are not ranked or scored, and a name match is not a verification result. For direct one-call verification, use verify_business.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 3,
          "description": "Company name to search for. Trimmed; 3–300 characters. Do not guess spellings; use the name as claimed."
        }
      },
      "description": "Search the Swiss commercial register (Zefix) by company name. Discovery only: returns bounded register candidates; nothing is selected, ranked or verified.",
      "additionalProperties": false
    }
    arguments 16 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 a75d6e9e5eb3e20b.

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

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.