# OnceAsk (remote · onceask.com)

MCP server for OnceAsk, the AI-native current-address layer for people and agents.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

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

## Channel facts

- Endpoint: `https://onceask.com/_api/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-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_delivery_permission).
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 493 tokens (~123/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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 current MCP spec version (2026-07-28).

## Install

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

OnceAsk is a hosted endpoint at https://onceask.com/_api/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 rsb6061-onceask 'https://onceask.com/_api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "rsb6061-onceask": {
      "url": "https://onceask.com/_api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.rsb6061-onceask]
url = "https://onceask.com/_api/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  rsb6061-onceask:
    url: "https://onceask.com/_api/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "rsb6061-onceask": {
      "type": "http",
      "url": "https://onceask.com/_api/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-09-28 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 71, +1)

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

### 2026-09-25 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 69, +1)

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

### 2026-09-21 (score 68, +1)

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

### 2026-09-19 (score 67, +1)

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

### 2026-09-17 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 65)

First indexed and scored.

## MCP tools (4)

### `resolve_delivery` (~110 tokens)

Resolve private delivery

Preferred privacy-preserving way to send something to a person. Searches OnceAsk first and, when connected, can discover a missing person from Google Contacts or Gmail interactions. Resolves to a short-lived one-time delivery token when recipient permission and a current address exist. Does not return the street address.

Input parameters:

- `contactId` (string): Known OnceAsk contact ID
- `purpose` (string): Purpose for the physical delivery
- `query` (string): Name or email to resolve when contact ID is not known

### `request_delivery_permission` (~131 tokens)

Request private delivery permission

After the user explicitly confirms they want the recipient contacted, ask OnceAsk to request a current delivery address/permission. Accepts either a recipientId from resolve_delivery or a person's name/email. OnceAsk searches its contacts and connected Google/Gmail-derived people, then emails the secure request when possible without revealing the recipient email or street address to the agent.

Input parameters:

- `contactId` (string): recipientId returned by resolve_delivery
- `customMessage` (string): Optional message shown to the recipient
- `query` (string): Person's name or email when recipientId is not known, e.g. Aunt Theresa

### `list_handwritten_cards` (~34 tokens)

Browse handwritten cards

List available Handwrytten card designs and handwriting styles for privacy-preserving fulfillment. Does not expose recipient address data.

### `send_handwritten_card` (~115 tokens)

Send handwritten card

Fulfill a handwritten card using a delivery token returned by resolve_delivery. OnceAsk sends the recipient address directly to the fulfillment provider; the agent does not receive it.

Input parameters:

- `cardId` (number, required): Card ID from list_handwritten_cards
- `deliveryToken` (string, required): Opaque token returned by resolve_delivery
- `fontLabel` (string): Handwriting label from list_handwritten_cards; defaults to Casual David
- `message` (string, required): Handwritten message
- `wishes` (string): Optional closing/signoff

## Diagnostics

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

## Score history

- 2026-09-28: 71
- 2026-09-27: 71
- 2026-09-26: 70
- 2026-09-25: 70
- 2026-09-24: 69
- 2026-09-23: 69
- 2026-09-22: 68
- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65

## Common questions

### What is the OnceAsk MCP server?

OnceAsk is an MCP server listed in the public MCP registry as io.github.rsb6061/onceask. MCP server for OnceAsk, the AI-native current-address layer for people and agents. This page covers its hosted endpoint (https://onceask.com/_api/mcp).

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

OnceAsk scores 71 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 OnceAsk MCP server expose?

OnceAsk exposes 4 tools: resolve_delivery, request_delivery_permission, list_handwritten_cards, send_handwritten_card. Their descriptions and schemas cost roughly 390 tokens of context every time the server is loaded.

### Does the OnceAsk MCP server require authentication?

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

### Is the OnceAsk MCP server still maintained?

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

## Links

- Remote endpoint: https://onceask.com/_api/mcp
- Repository: https://github.com/rsb6061/onceask-mcp
- Website: https://onceask.com/
- Changelog RSS feed: https://verifymcp.io/servers/rsb6061-onceask/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/rsb6061-onceask/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/rsb6061-onceask/api-mcp