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.

OnceAsk

REMOTE · ONCEASK.COM · SCANNED SEP 28

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

Available components

+3 this week 71 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 493 tokens (~123/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

remote · onceask.com

# add to Claude Code
claude mcp add --transport http rsb6061-onceask 'https://onceask.com/_api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "rsb6061-onceask": {
      "url": "https://onceask.com/_api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rsb6061-onceask": {
      "type": "http",
      "url": "https://onceask.com/_api/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add rsb6061-onceask --url 'https://onceask.com/_api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  rsb6061-onceask:
    url: "https://onceask.com/_api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rsb6061-onceask": {
      "Transport": "http",
      "Url": "https://onceask.com/_api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add rsb6061-onceask -t streamable-http -u 'https://onceask.com/_api/mcp'
// mcp.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 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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +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.

  • 25 Sept 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
  • 23 Sept 26 +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.

  • 21 Sept 26 +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.

  • 19 Sept 26 +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.

  • 17 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Sept 26 65

    First indexed and scored.

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 28 Sept 2026 · Probed https://onceask.com/_api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onceask.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 7 Sept 2026 23 Mar 2027 RSA 2048 SHA256-RSA a4c13df97193593e9cf64902c8c2464
SANs: onceask.com, *.onceask.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of onceask.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onceask.com. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://onceask.com/_api/mcp Verified 200
http (plaintext) http://onceask.com/_api/mcp HTTPS enforced 301 https://onceask.com/_api/mcp
MCP tools · 4 exposed · ~390 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
list_handwritten_cards ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_delivery_permission ~131

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.

NameTypeReqDescription
contactIdstring–recipientId returned by resolve_delivery
customMessagestring–Optional message shown to the recipient
querystring–Person's name or email when recipientId is not known, e.g. Aunt Theresa

No output schema declared.

No examples provided.

resolve_delivery ~110

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.

NameTypeReqDescription
contactIdstring–Known OnceAsk contact ID
purposestring–Purpose for the physical delivery
querystring–Name or email to resolve when contact ID is not known

No output schema declared.

No examples provided.

send_handwritten_card ~115

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.

NameTypeReqDescription
cardIdnumberyesCard ID from list_handwritten_cards
deliveryTokenstringyesOpaque token returned by resolve_delivery
fontLabelstring–Handwriting label from list_handwritten_cards; defaults to Casual David
messagestringyesHandwritten message
wishesstring–Optional closing/signoff

No output schema declared.

No examples provided.

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.