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

ulup-life-mcp

https://www.uluplife.com

Registry code: 67ea09a6aa71f52b

api record

Create and search memories in your personal life constellation, UluP Life.

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

endpoint
https://www.uluplife.com/api/mcp
protocol
streamable-http ·2024-11-05
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 ulup-life-mcp live?
Yes — it answered the hub's last check (checked 36m ago). It answered 100% of checks over the last 30 days.
Is ulup-life-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does ulup-life-mcp have?
2 tools: create_moment, list_moments.
Is ulup-life-mcp 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 99.7%· all time 99.7%

latency
963ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 327 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
productivity & business
used for
  • record a personal life moment
  • search personal memories and goals
takes → gives
text, data → data
tools
1 reads1 changes data
_ 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 auth-required 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.

  • list_moments reads auth-required 8h ago

    Cerca e restituisce i momenti della costellazione dell'utente su UluP Life, con filtri opzionali.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "color": {
      "enum": [
        "gold",
        "blue",
        "pink",
        "green"
      ],
      "type": "string",
      "description": "Filtra per categoria."
    },
    "search": {
      "type": "string",
      "description": "Cerca questo testo nel titolo o nella descrizione dei momenti."
    },
    "life_name": {
      "type": "string",
      "description": "Filtra solo i momenti di questa \"vita\" (galassia). Se omesso, cerca in tutte."
    },
    "only_unachieved_goals": {
      "type": "boolean",
      "description": "Se true, restituisce SOLO gli obiettivi futuri non ancora avverati (capsule del tempo ancora spente)."
    }
  }
}
    arguments 27 lines
  • create_moment changes data unknown never probed

    Crea un nuovo momento (una stella) nella costellazione dell'utente su UluP Life.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Data del momento — formato YYYY-MM-DD per il giorno esatto, YYYY-MM per il solo mese, o solo YYYY per il solo anno. Se omessa del tutto, il momento non ha data (l'utente potrà posizionarlo liberamente)."
    },
    "color": {
      "enum": [
        "gold",
        "blue",
        "pink",
        "green"
      ],
      "type": "string",
      "description": "Categoria: gold=traguardo, blue=viaggio, pink=relazione, green=crescita. Default: gold."
    },
    "title": {
      "type": "string",
      "description": "Titolo breve del momento, es. \"Firmato il contratto della casa\""
    },
    "important": {
      "type": "boolean",
      "description": "Se true, la stella pulserà come momento importante."
    },
    "life_name": {
      "type": "string",
      "description": "Nome della \"vita\" (galassia) a cui aggiungere il momento. Se omesso, viene usata la prima vita dell'utente."
    },
    "description": {
      "type": "string",
      "description": "Descrizione opzionale, più dettagliata"
    },
    "is_future_goal": {
      "type": "boolean",
      "description": "Se true, il momento è un obiettivo/sogno futuro non ancora avverato — appare come una stella \"spenta\" (capsula del tempo), anche se la data è nel futuro."
    }
  }
}
    arguments 42 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 67ea09a6aa71f52b.

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