OnceAsk

io.github.rsb6061Published by GitHub account rsb6061v1.0.0Updated Oct 24, 2026

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

The publisher's own server: ONCE

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

OnceAsk is a remote MCP server that lets an assistant check whether a person's mailing address is current and authorized, then send physical mail such as a card

What you can do
Resolve a person to a delivery state: authorized, permission required, address update required, ambiguous or not found, optionally looking them up in connected Google Contacts or Gmail interactions when connected to OnceAsk's own contacts and Google-derived people, then emailing the recipient to ask for a current address or permission, after the user explicitly confirms the contact should be made. List available handwritten card designs and handwriting styles without exposing recipient data. Fulfill a handwritten card using a short-lived one-time delivery token, with the address sent directly to the fulfillment provider rather than returned to the agent.
When to use it
Useful when an assistant needs to send something physical to a known person, such as a birthday card, thank-you gift, invitation or document, and the address in an existing contact record may be stale or unconfirmed. Also suited to asking a recipient to confirm or update their address before mailing.
Requirements
A remote Streamable HTTP endpoint at onceask.com; no packages, environment variables or headers are declared. Recipient permission and a current address are needed before a delivery token is issued. Google Contacts or Gmail discovery applies only when the OnceAsk account is connected to those sources.
Before you install
Sending a handwritten card is a real-world action that mails physical mail and may involve costs through the fulfillment provider. The server emails recipients to request addresses or permission, so only do this after the user explicitly confirms. Recipient street addresses are passed to the fulfillment provider and are not returned to the agent. The manifest declares no authentication, so check how the endpoint is secured before use.

Installation

In SourceWeft

  1. Open OnceAsk in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rsb6061%2Fonceask/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "onceask": {
      "type": "http",
      "url": "https://onceask.com/_api/mcp"
    }
  }
}

README

OnceAsk MCP — Contacts + Current Mailing Addresses

Official MCP discovery repo for OnceAsk, a contacts and address-book MCP for AI agents that need a person's current mailing address, not just the last address stored in a contact record.

Addresses change. OnceAsk keeps them current.

OnceAsk helps an AI assistant resolve a known person to a current, permissioned delivery destination or request an update when the address is missing or stale.

MCP endpoint

https://onceask.com/_api/mcp

Transport: Streamable HTTP

Registry identity: io.github.rsb6061/onceask

What makes OnceAsk different

A conventional contacts integration can tell an agent who a person is and expose whatever fields are stored for that contact. OnceAsk focuses on the next problem: is this person's mailing address current and usable for this physical-delivery action?

OnceAsk can return an explicit delivery state instead of treating a saved address as automatically current:

  • authorized — the recipient is ready for an authorized delivery action.
  • permission_required — request recipient permission.
  • address_update_required — ask the recipient to confirm or update the current address.
  • ambiguous — ask the user which matching person they mean.
  • not_found — collect or create the recipient first.

Core MCP tools

resolve_delivery

Resolve a known person or contact to a current delivery state. This is the preferred primitive for AI agents that need to send something physical.

request_delivery_permission

Trigger the recipient-confirmation flow when an address is missing, stale, or not yet authorized.

list_handwritten_cards

List supported Handwrytten card designs and handwriting styles without exposing recipient data.

send_handwritten_card

Fulfill an authorized card delivery using an opaque delivery token. The preferred flow does not return the recipient's raw street address as ordinary model output.

Example agent workflows

  • "Send Aunt Theresa a birthday card."
  • "Mail this client a thank-you gift."
  • "Get John's current mailing address before we send the invitation."
  • "Ask Sarah for her new address."
  • "Send the document to Mike without relying on the address in our old CRM record."

The agent can identify the person from its existing context, then use OnceAsk to resolve the current delivery state.

Useful links

Live directory listings

These listings point to the same production endpoint and registry identity: io.github.rsb6061/onceask.

MCP Registry

The registry metadata is defined in server.json.

To verify the official registry listing:

bash
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.rsb6061/onceask"

Website

https://onceask.com

Contact

[email protected]

Source: README.md at commit 8ea8583

Tools

4

resolve_delivery

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.

ParametersquerypurposecontactId

request_delivery_permission

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.

ParametersquerycontactIdcustomMessage

list_handwritten_cards

Browse handwritten cards

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

Takes no parameters.

send_handwritten_card

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.

ParameterscardIdrequiredwishesmessagerequiredfontLabeldeliveryTokenrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Once integrations