Assistant tool

sixonseven_list_notifications

Lists your 6on7 notifications as titles only, with read state and timestamps, and never returns message text.

Updated November 6, 2026

Website
6on7 · 6on7.com · 18+
Class
Read
Returns
notifications[]: id, kind, title, created_at, read

List your 6on7 notifications (titles only, never message text). 6on7 is for adults 18+.

Where you can call it

Inputs

ArgumentTypeNotes
unread_only optionalboolean
limit optionalinteger 1–50How many items to return (default 10).

Example request

POST https://onelifevibe.com/mcp

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "sixonseven_list_notifications",
    "arguments": {
      "limit": 10
    }
  }
}

Other 6on7 tools

What it does

sixonseven_list_notifications is a Read tool for the 6on7 website. Read tools change nothing, so calling it does not mark a notification read, delete it or alter the account. 6on7 is dating for an actual relationship; every profile shows what that person has verified. 6on7 is for adults 18+.

The tool lists your 6on7 notifications. Each item carries an id, kind, title, created_at and read. Titles are the only message-related text you get back; message text is never returned.

When an assistant should call it

Call it when the person asks what is new on 6on7, wants a quick look at recent notifications, or wants to see unread items. It is a sensible first step before sixonseven_mark_notifications_read when the person wants to review what is unread and then act on it.

Use unread_only when the question is specifically about unread notifications, and keep limit small for a quick check. If the person asks about verification, use sixonseven_get_verification_status instead; that is a separate tool on the same website.

The tool works only after the person has connected their OneLifeVibe account and signed in to 6on7.com with OneLifeVibe once. If the account is not linked, the call returns not_linked and the assistant should ask the person to complete that sign-in rather than guess at notifications.

Inputs and an example call

Both inputs are optional. unread_only is a boolean; set it to true when you want unread notifications only. limit is an integer from 1 to 50 and controls how many items to return; the default is 10.

Send the call over MCP at https://onelifevibe.com/mcp as JSON-RPC tools/call. This example asks for 10 notifications: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"sixonseven_list_notifications","arguments":{"limit":10}}}

On the account connector, the call needs the person's OneLifeVibe sign-in with OAuth 2.1 and PKCE, scope olv.read, and a prior OneLifeVibe sign-in at 6on7.com. The connector sign-in is set up for Meta Muse today, with client onelifevibe-muse. Other MCP clients reach the no-account tools through the free connector.

What comes back

A successful result contains notifications[]. Each entry has id, kind, title, created_at and read. title is the notification title, kind is the notification kind, created_at is the creation time, and read is the read flag. No message text is included.

Use id when you need to refer to a notification later, and title when you need a short label for the person. Do not present a title as if it were the full message.

Repeating the call does not create, read or change anything; the list reflects the account at the time of the call. To change read state, use sixonseven_mark_notifications_read.

Errors, limits and safety

The common account error is not_linked. It means the person has not signed in to 6on7.com with OneLifeVibe once. Have them complete that sign-in, then retry.

The limit is capped at 50; values outside 1 to 50 are not valid. The default is 10. The tool is read-only and non-destructive, and it is idempotent. It returns titles only, never message text, so do not infer or fabricate message content from a title.

On the platform API, sixonseven_list_notifications is listed in GET /api/platform/v1/tools, but a platform key gets HTTP 501 with world_tools_unavailable for it today, because it acts on one member's own data. A 501 means the server does not support the request for that key. A platform key can call the world catalogue, the tool registry, the network directory tool and the event log. For this tool, use the account connector.

Questions

What does sixonseven_list_notifications return?

It returns notifications[] with id, kind, title, created_at and read for each item. Titles only; message text is never returned.

Why does the tool return not_linked?

The person must sign in to 6on7.com with OneLifeVibe once, and the connector call needs the OneLifeVibe sign-in with scope olv.read. If that sign-in has not happened, the tool answers not_linked; complete the sign-in and retry.

Can I call sixonseven_list_notifications with a platform API key?

It is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today because it acts on one member's own data. Use the account connector at https://onelifevibe.com/mcp with the person's OneLifeVibe sign-in.

Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.

Get a free key Connector guide

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.