_ registry / mcp http-sse · checked 52m 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 52m ago). It answered 100% of checks over the last 30 days.
Is bumit free to use?
Not measured yet.
What tools does bumit have?
1 tool: verify_business.
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
100%

90 days 100%· all time 100%

latency
1,070ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 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 1 tools
1 never probed 0 of 1 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.

  • verify_business unknown never probed

    Verify a Swiss business (current scope: Switzerland only) by uid, name and/or address, using evidence from official/public Swiss sources: Zefix (commercial-register index), plus SECO sanctions and FINMA authorisation datasets ingested by the operator. Each check names its source (checks[].sources), data basis, provenance and freshness (observed_at, retrieved_at, source timestamps); explain to the user which source supplied the evidence and when BUMIT observed or retrieved it. A timestamp that is null is unknown — do not infer one. Returns the BUMIT business-verification result (contract 1.0.0-phase13.2); result.outcome is one of VERIFIED, NOT_VERIFIED, REVIEW_REQUIRED, UNAVAILABLE, NOT_FOUND, AMBIGUOUS, UNSUPPORTED — all are business results, not errors. You may call with only a company name; no UID is needed. An exact unique legal-name match is resolved and verified in one call. Otherwise result.outcome is AMBIGUOUS and resolution.candidates lists commercial-register companies (uid, legal_name, seat, canton): BUMIT never selects a partial/similar or duplicate-name candidate. Choose the intended company from your context (or ask the user), then call verify_business again with {"uid": "<candidate uid>"}. NOT_FOUND means the register search returned no candidate. REVIEW_REQUIRED: additional review of the blocking checks is required before acting. UNAVAILABLE: evidence could not currently support a conclusion; it is NOT NOT_VERIFIED. Checks marked UNSUPPORTED have no source and must stay unsupported.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "uid": {
          "type": "string",
          "pattern": "^[\\s._/-]*[Cc][\\s._/-]*[Hh][\\s._/-]*[Ee](?:[\\s._/-]*[0-9]){9}[\\s._/-]*$",
          "maxLength": 64,
          "description": "Swiss UID, canonical (CHE-123.456.789) or compact (CHE123456789). Check digit validated server-side."
        },
        "name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Exact legal name. Name-only resolution needs at least 3 characters. Exact normalized equality only; never fuzzy."
        },
        "address": {
          "type": "object",
          "required": [
            "street",
            "house_number",
            "postcode",
            "locality"
          ],
          "properties": {
            "street": {
              "type": "string",
              "maxLength": 200,
              "minLength": 1
            },
            "locality": {
              "type": "string",
              "maxLength": 100,
              "minLength": 1
            },
            "postcode": {
              "type": "string",
              "maxLength": 10,
              "minLength": 1
            },
            "house_number": {
              "type": "string",
              "maxLength": 20,
              "minLength": 1
            }
          },
          "additionalProperties": false
        }
      },
      "minProperties": 1,
      "additionalProperties": false
    }
    arguments 51 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
50%

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.