Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Obento

REMOTE · OBENTOAPP.COM

Live USDC rates on Base, any address's Obento position, and deposits and withdrawals to sign.

Available components

+4 this week 88 Trust /100

Last scanned (9 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 645 tokens (~107/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Probed https://obentoapp.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.obentoapp.com CN=YR2,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 RSA 2048 SHA256-RSA 56bc9eddc773ccae3d303a9c09c18f31531
SANs: *.obentoapp.com, obentoapp.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of obentoapp.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
obentoapp.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; child-src https://auth.privy.io https://verify.walletconnect.com https://verify.walletconnect.org; frame-src https://auth.privy.io https://verify.walletconnect.com https://verify.walletconnect.org https://challenges.cloudflare.com; connect-src 'self' https://mainnet.base.org https://www.walletlink.org https://rpc.wallet.coinbase.com https://rpc.walletconnect.org https://verify.walletconnect.com https://verify.walletconnect.org https://auth.privy.io wss://relay.walletconnect.com wss://relay.walletconnect.org wss://www.walletlink.org https://*.rpc.privy.systems https://explorer-api.walletconnect.com https://api.relay.link https://api.testnets.relay.link; worker-src 'self'; manifest-src 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://obentoapp.com/mcp Verified 200
http (plaintext) http://obentoapp.com/mcp HTTPS enforced 308 https://obentoapp.com/mcp
MCP tools · 6 exposed · ~477 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
autopilot_journal ~44

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

position ~61

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.

NameTypeReqDescription
addressstringyesA Base address, 0x followed by 40 hex characters

No output schema declared.

No examples provided.

prepare_deposit ~120

Deposits are closed while Obento is paused, so this returns an error. 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.

NameTypeReqDescription
addressstringyesThe address that holds the USDC and receives the obUSD
amountstringyesUSDC to deposit, in dollars, such as "100" or "25.50"

No output schema declared.

No examples provided.

prepare_withdrawal ~144

Withdrawals are closed while Obento is paused, so this returns an error. 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.

NameTypeReqDescription
addressstringyesThe address that holds the obUSD
amountstring–USDC to withdraw, in dollars; leave out to withdraw everything
receiverstring–Where the USDC goes; the address itself if left out

No output schema declared.

No examples provided.

read_docs ~60

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

NameTypeReqDescription
pagestringyesThe page, such as "risks", "fees" or "agents"

No output schema declared.

No examples provided.

vault_status ~48

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Obento MCP server?

Obento is a hosted endpoint at https://obentoapp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · obentoapp.com

# add to Claude Code
claude mcp add --transport http com-obentoapp-obento 'https://obentoapp.com/mcp'
Common questions

What is the Obento MCP server?

Obento is an MCP server listed in the public MCP registry as com.obentoapp/obento. Live USDC rates on Base, any address's Obento position, and deposits and withdrawals to sign. This page covers its hosted endpoint (https://obentoapp.com/mcp).

Is the Obento MCP server safe to use?

Obento scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Obento MCP server expose?

Obento exposes 6 tools: vault_status, position, autopilot_journal, prepare_deposit, prepare_withdrawal, read_docs. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.

Does the Obento MCP server require authentication?

No. We connected to Obento without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Obento MCP server still maintained?

Obento is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Obento MCP server?

VerifyMCP ran 13 checks on Obento, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.