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

ninthlifelab

https://ninthlifelab.com

Registry code: 7e3802a3d92b4d5d

api record

Ninth Life Lab builds custom software for small and mid-sized companies from parts that already run in 27 shipped projects: live in weeks, fixed price, then hosted for a monthly fee. Use match_business when someone describes their business or a problem; search_catalog for a topic; get_assistant for details; book_a_call when they want to talk to the team.

endpoint
https://ninthlifelab.com/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 ninthlifelab live?
Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
Is ninthlifelab free to use?
Yes — the hub reached it with no key and no payment.
What tools does ninthlifelab have?
4 tools: get_assistant, match_business, book_a_call, search_catalog.
Is ninthlifelab 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
175ms

last good check

priced tools
0

of 4 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 4 tools
1 open 3 never probed 1 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.

  • search_catalog open 19h ago

    Search the Ninth Life Lab catalog of ready-made business assistants by words, e.g. 'inbox', 'stock', 'invoice'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "tr"
          ],
          "type": "string",
          "default": "en",
          "description": "Answer language: en or tr."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 30,
          "minimum": 1
        },
        "query": {
          "type": "string"
        }
      }
    }
    arguments 26 lines
  • get_assistant unknown 19h ago

    Full details of one catalog assistant by id (e.g. P01): the problem, what it does, who it is for, setup time, where it already runs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Catalog id such as P01."
        },
        "lang": {
          "enum": [
            "en",
            "tr"
          ],
          "type": "string",
          "default": "en",
          "description": "Answer language: en or tr."
        }
      }
    }
    arguments 21 lines
  • match_business unknown 19h ago

    Describe a business or a problem in plain words (English or Turkish), e.g. 'we lose track of supplier invoices and approvals'. Returns the Ninth Life Lab assistants that already run in shipped projects and fit it, what each matched on, systems mentioned, and what would be built new.

    mcp-tool

    {
      "type": "object",
      "required": [
        "description"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "tr"
          ],
          "type": "string",
          "default": "en",
          "description": "Answer language: en or tr."
        },
        "description": {
          "type": "string",
          "description": "The business or problem, a sentence or more."
        }
      }
    }
    arguments 21 lines
  • book_a_call unknown never probed

    How to start with Ninth Life Lab: the 30-minute call link and the four steps from first call to running software.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "tr"
          ],
          "type": "string",
          "default": "en",
          "description": "Answer language: en or tr."
        }
      }
    }
    arguments 14 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 7e3802a3d92b4d5d.

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