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

obento

https://obentoapp.com

Registry code: f181070595099b93

api record

Obento puts USDC to work on Base (chain ID 8453). Autopilot lends deposits across vetted lending markets and moves them when rates change; one fee, 10% of new lending profit; withdraw any time.

Call vault_status before preparing a transaction, and only prepare one while it reports open. prepare_deposit and prepare_withdrawal return calls in order for the user's own wallet to sign and send on Base; Obento never holds keys or sends anything. They tag the gateway calls with partner ID 2 for agents.

endpoint
https://obentoapp.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 obento live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is obento free to use?
Yes — the hub reached it with no key and no payment.
What tools does obento have?
6 tools: prepare_deposit, prepare_withdrawal, read_docs, position, autopilot_journal, vault_status.
Is obento 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
268ms

last good check

priced tools
0

of 6 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 6 tools
2 open 4 never probed 2 of 6 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.

  • autopilot_journal open 1h ago

    Every move Autopilot made in the last 30 days: money lent to or taken from each place, queued withdrawals it paid, and any pause, newest first.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • vault_status open 1h ago

    Obento's live state: whether deposits are open, the yearly rate after the fee, the obUSD share price, deposits, ready cash for instant withdrawals, and where the money is.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • prepare_deposit unknown never probed

    Builds the two calls that deposit USDC into Obento for an address: approve the gateway, then deposit with a 0.5% minimum out and partner ID 2. The address signs and sends them in order on Base. Sends nothing itself.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address",
    "amount"
  ],
  "properties": {
    "amount": {
      "type": "string",
      "description": "USDC to deposit, in dollars, such as \"100\" or \"25.50\""
    },
    "address": {
      "type": "string",
      "description": "The address that holds the USDC and receives the obUSD"
    }
  }
}
    arguments 18 lines
  • prepare_withdrawal unknown never probed

    Builds the two calls that withdraw from Obento: approve the gateway to take the obUSD, then redeem with a 0.5% minimum out and partner ID 2. Leave out the amount to withdraw everything. Says whether the USDC arrives at once or on Autopilot's next pass. Sends nothing itself.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "amount": {
      "type": "string",
      "description": "USDC to withdraw, in dollars; leave out to withdraw everything"
    },
    "address": {
      "type": "string",
      "description": "The address that holds the obUSD"
    },
    "receiver": {
      "type": "string",
      "description": "Where the USDC goes; the address itself if left out"
    }
  }
}
    arguments 21 lines
  • read_docs unknown never probed

    One page of Obento's docs as Markdown: how it works, fees, risks, security, contracts, withdrawals, the agent guide and more.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "page"
  ],
  "properties": {
    "page": {
      "enum": [
        "index",
        "getting-started",
        "autopilot",
        "journal",
        "places",
        "withdrawals",
        "fees",
        "security",
        "risks",
        "status",
        "contracts",
        "builders",
        "agents",
        "faq"
      ],
      "type": "string",
      "description": "The page, such as \"risks\", \"fees\" or \"agents\""
    }
  }
}
    arguments 29 lines
  • position unknown 1h ago

    What an address put into Obento, took out, holds now and earned, Autopilot's fee in dollars, and its latest deposits and withdrawals with their status.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "A Base address, 0x followed by 40 hex characters"
    }
  }
}
    arguments 13 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 f181070595099b93.

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

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.