# JomoBench (remote · jomobench.com)

fomo app spot fee quotes, the measured realized fee rate, referral facts, site search. Read-only.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `jomobench.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-jomobench-mcp/jomobench.md), [page](https://verifymcp.io/servers/com-jomobench-mcp/jomobench)

## Channel facts

- Endpoint: `https://jomobench.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1087 tokens (~271/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the JomoBench MCP server?

JomoBench is a hosted endpoint at https://jomobench.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.

### Claude

```bash
claude mcp add --transport http com-jomobench-mcp 'https://jomobench.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-jomobench-mcp": {
      "url": "https://jomobench.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-jomobench-mcp": {
      "type": "http",
      "url": "https://jomobench.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-jomobench-mcp]
url = "https://jomobench.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jomobench-mcp": {
      "type": "remote",
      "url": "https://jomobench.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-jomobench-mcp --url 'https://jomobench.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-jomobench-mcp:
    url: "https://jomobench.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-jomobench-mcp": {
      "Transport": "http",
      "Url": "https://jomobench.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-jomobench-mcp -t streamable-http -u 'https://jomobench.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-jomobench-mcp": {
      "type": "http",
      "url": "https://jomobench.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +1)

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

### 2026-11-19 (score 73, +1)

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

### 2026-11-17 (score 72, +1)

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

### 2026-11-15 (score 71, +1)

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

### 2026-11-13 (score 70, +1)

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

### 2026-11-12 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 69)

First indexed and scored.

## MCP tools (4)

### `fee_quote` (~370 tokens)

fomo spot fee quote

fomo's own fee for ONE spot trade (a buy or a sell) of a given USD size, computed from fomo's published schedule (help centre "Trading fees on fomo"). Route: "solana-low" (Solana, lowest-fee route: $0.10 under $5, 2% to $47.50, $0.95 flat to $190, then 0.50%), "solana-other" (Solana, other routes: 0.50%, $0.95 minimum), "evm" (Base, BNB Chain, Monad, Ethereum, Robinhood Chain, Arc, Elysium: 0.50% plus the network fee you pay) or "major" (selected major tokens: 0.05%). Chain names work too. Returns the fee in USD, the rate, the rule that applied, and the same trade with and without a referral code. Spot only: on perps fomo charges up to 0.05% of the position size per trade, plus Hyperliquid's fee. Excludes pool fees, price impact, network fees and token taxes. Computed, not measured.

Input parameters:

- `amount_usd` (number, required): Trade size in USD (required), e.g. 25, 100, 1000.
- `code` (boolean): True if the account signed up with a referral code (default false). A code only changes the 0.50% rate, to 0.45%.
- `round_trip` (boolean): Also price selling the same size (buy + sell).
- `route` (string): solana-low (default), solana-other, evm or major; or a chain name such as "base" or "robinhood chain".

### `realized_fee` (~123 tokens)

fomo realized spot fee rate (measured)

What fomo spot traders actually paid in fomo fees as a share of spot volume, measured from DefiLlama's fomo Wallet fee and volume data (fees on all chains divided by volume, same days, closed days only), against the 0.50% sticker rate. Returns the last 30 days, the last 7 days, the last complete month and every month since July 2026; pass month ("YYYY-MM") for one month.

Input parameters:

- `month` (string): Optional month, "YYYY-MM" (from 2026-07).

### `get_referral_info` (~117 tokens)

fomo referral facts and JomoBench's referral state

What a fomo referral code does for the trader (0.50% becomes 0.45%; nothing else changes), when it can be applied, what fomo pays the referrer, and whether JomoBench has a fomo code (today it does not). Pass venue "fomo" (default), another app JomoBench links to, or "all".

Input parameters:

- `venue` (string): "fomo" (default), "axiom", "phantom", "hyperliquid", ... or "all".

### `search_site` (~98 tokens)

Search JomoBench

Find JomoBench pages (fees, the bench measurements, guides, explainers, comparisons, data, news) for a question or keyword. Returns titles, one-line summaries and URLs; read the page for its dated short answer.

Input parameters:

- `limit` (integer): Max results (default 8, max 20).
- `q` (string, required): e.g. "fomo fees", "is fomo legit", "fomo copy trading"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-jomobench-mcp/jomobench#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69
- 2026-11-11: 69

## Common questions

### What is the JomoBench MCP server?

JomoBench is an MCP server listed in the public MCP registry as com.jomobench/mcp. fomo app spot fee quotes, the measured realized fee rate, referral facts, site search. Read-only. This page covers its hosted endpoint (https://jomobench.com/mcp).

### Is the JomoBench MCP server safe to use?

JomoBench scores 74 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 JomoBench MCP server expose?

JomoBench exposes 4 tools: fee_quote, realized_fee, get_referral_info, search_site. Their descriptions and schemas cost roughly 708 tokens of context every time the server is loaded.

### Does the JomoBench MCP server require authentication?

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

### Is the JomoBench MCP server still maintained?

JomoBench is still listed as active in the MCP registry. We last reached this channel on 21 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 JomoBench MCP server?

VerifyMCP ran 13 checks on JomoBench, 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.

## Links

- Remote endpoint: https://jomobench.com/mcp
- Website: https://jomobench.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-jomobench-mcp/jomobench.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jomobench-mcp/jomobench/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-jomobench-mcp/jomobench.json
- HTML version of this page: https://verifymcp.io/servers/com-jomobench-mcp/jomobench
