Assistant tool
sixonseven_mark_notifications_read
Marks one notification or all notifications as read on 6on7. It changes only the person's read state and tells nobody else.
Updated November 6, 2026
- Website
- 6on7 · 6on7.com · 18+
- Class
- Write
- Returns
marked
Mark one notification, or all of them, as read on 6on7. Nobody else is told. 6on7 is for adults 18+.
Where you can call it
- Account connector https://onelifevibe.com/mcp: needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE), scope olv.write, and the person must have signed in to 6on7.com with OneLifeVibe once, otherwise the tool answers not_linked. Its sign-in is set up for Meta Muse today (client onelifevibe-muse); other MCP clients reach the no-account tools through the free connector.
- Platform API registry: 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; a platform key can call the world catalogue, the tool registry, the network directory tool and the event log.
Inputs
| Argument | Type | Notes |
|---|---|---|
notification_id optional | string ≤80 | One notification id; omit to mark all as read. |
Example request
POST https://onelifevibe.com/mcp
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "sixonseven_mark_notifications_read",
"arguments": {}
}
}Other 6on7 tools
- sixonseven_list_notifications notifications
- sixonseven_get_verification_status verification status
What it does
sixonseven_mark_notifications_read is a Write tool for 6on7, the adults-only dating site for an actual relationship where every profile shows what that person has verified. It marks one notification as read when you pass a notification id, or marks all notifications as read when you omit the id. Nobody else is told.
6on7 is for adults 18+. A Write tool changes only the signed-in person's own data on that site. This tool is not destructive and it is idempotent: repeating the call leaves the notification read.
When an assistant should call it
Call it when the person asks to mark a notification read, mark their notifications read, or catch up on notifications after a list call. Use sixonseven_list_notifications first when you need the id for one item; then pass that id here. Omit the id only when the person wants all notifications marked read.
Keep the scope narrow. This tool changes read state, not verification status; use sixonseven_get_verification_status for that check. It does not fetch the notification list, so a workflow that needs ids should start with sixonseven_list_notifications.
Inputs and an example call
The only input is notification_id, an optional string of 80 characters or fewer. Pass one id to mark that notification read. Omit it to mark all notifications read.
Send a tools/call request to https://onelifevibe.com/mcp with params.name sixonseven_mark_notifications_read and params.arguments.notification_id set to the id. To mark all, leave params.arguments empty. This is an account-connector call: the person signs in with OneLifeVibe using OAuth 2.1 with PKCE and grants scope olv.write, and must have signed in to 6on7.com with OneLifeVibe once.
What comes back
A successful call returns marked. If you passed an id, that one notification is now read; if you omitted the id, all notifications are read.
The call is idempotent, so a retry after a timeout is safe. If the first request already succeeded, the second returns marked and the read state stays the same. Nobody else is told.
Errors, limits and safety
If the person has not signed in to 6on7.com with OneLifeVibe once, the tool answers not_linked. Have them complete that sign-in, then retry. The connector call needs a OneLifeVibe sign-in with scope olv.write; the account connector uses OAuth 2.1 with PKCE. The account connector's sign-in is set up for Meta Muse today, client onelifevibe-muse; other MCP clients reach the no-account tools through the free connector.
The platform API registry lists this tool 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. 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.
notification_id must be a string of no more than 80 characters. The tool is not destructive and is idempotent, so it is safe to repeat. As a Write tool it changes only the signed-in person's own data, and 6on7 is for adults 18+.
Questions
Why does sixonseven_mark_notifications_read return not_linked?
The person has not signed in to 6on7.com with OneLifeVibe once. Complete that sign-in and retry. The call also needs a OneLifeVibe sign-in with scope olv.write.
Can I call sixonseven_mark_notifications_read with a platform API key?
The tool is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today. Use the account connector at https://onelifevibe.com/mcp, which acts on the member's own data.
Does marking a notification read tell anyone else?
No. It changes only that person's own data on 6on7 and nobody else is told. The tool is not destructive and is idempotent.
Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.