# VESPER Agent (remote · mcp.vesperagent.ai)

Estimates automation time savings, drafts automation specs, and checks Japanese ad copy. Read-only.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.vesperagent.ai`: 65/100 (this document), [markdown](https://verifymcp.io/servers/ai-vesperagent-vesper/mcp.md), [page](https://verifymcp.io/servers/ai-vesperagent-vesper/mcp)

## Channel facts

- Endpoint: `https://mcp.vesperagent.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 272 tokens (~90/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 VESPER Agent MCP server?

VESPER Agent is a hosted endpoint at https://mcp.vesperagent.ai/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 ai-vesperagent-vesper 'https://mcp.vesperagent.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-vesperagent-vesper": {
      "url": "https://mcp.vesperagent.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-vesperagent-vesper": {
      "type": "http",
      "url": "https://mcp.vesperagent.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-vesperagent-vesper]
url = "https://mcp.vesperagent.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-vesperagent-vesper --url 'https://mcp.vesperagent.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-vesperagent-vesper:
    url: "https://mcp.vesperagent.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-vesperagent-vesper": {
      "Transport": "http",
      "Url": "https://mcp.vesperagent.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-vesperagent-vesper -t streamable-http -u 'https://mcp.vesperagent.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-vesperagent-vesper": {
      "type": "http",
      "url": "https://mcp.vesperagent.ai/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 65, +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-19 (score 64, +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-17 (score 63, +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-16 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 62)

First indexed and scored.

## MCP tools (3)

### `estimate_automation_savings` (~74 tokens)

業務自動化の削減効果試算

Estimate monthly and annual time savings and JPY equivalents from task assumptions; rank tasks by time saved. Estimates do not guarantee outcomes. 業務ごとの前提から削減時間と円換算を試算します。

Input parameters:

- `hourly_cost_jpy` (number)
- `tasks` (array, required)

### `draft_automation_spec` (~97 tokens)

自動化仕様書の下書き

Draft a ten-section automation specification from existing steps, marking human approval gates and automation candidates. No actions are executed. 現行手順から承認箇所を明示した仕様書の下書きを作成します。

Input parameters:

- `current_steps` (array, required)
- `frequency` (string)
- `owner_role` (string)
- `task_name` (string, required)
- `tools_used` (array)

### `check_japanese_ad_copy` (~61 tokens)

日本向け広告文の表現チェック

Mechanically flag potentially misleading Japanese advertising claims with severity, quoted context, and alternative wording. This is not a legal determination. 日本向け広告・LPの表現を機械的に点検します。

Input parameters:

- `text` (string, required)

## Diagnostics

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

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 62
- 2026-11-15: 62

## Common questions

### What is the VESPER Agent MCP server?

VESPER Agent is an MCP server listed in the public MCP registry as ai.vesperagent/vesper. Estimates automation time savings, drafts automation specs, and checks Japanese ad copy. Read-only. This page covers its hosted endpoint (https://mcp.vesperagent.ai/mcp).

### Is the VESPER Agent MCP server safe to use?

VESPER Agent scores 65 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 VESPER Agent MCP server expose?

VESPER Agent exposes 3 tools: estimate_automation_savings, draft_automation_spec, check_japanese_ad_copy. Their descriptions and schemas cost roughly 232 tokens of context every time the server is loaded.

### Does the VESPER Agent MCP server require authentication?

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

### Is the VESPER Agent MCP server still maintained?

VESPER Agent 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 VESPER Agent MCP server?

VerifyMCP ran 12 checks on VESPER Agent, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about VESPER Agent: HTTPS. 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://mcp.vesperagent.ai/mcp
- Website: https://mcp.vesperagent.ai/docs
- Changelog RSS feed: https://verifymcp.io/servers/ai-vesperagent-vesper/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-vesperagent-vesper/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-vesperagent-vesper/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-vesperagent-vesper/mcp
