Assistant tool
sixonseven_get_verification_status
Reads your 6on7 trust level, tier and the state of your email, phone, photo and ID verifications, plus whether you can message.
Updated November 6, 2026
- Website
- 6on7 · 6on7.com · 18+
- Class
- Read
- Returns
trust_level, tier {level, name}, verifications {email, phone, photo, id}, can_message
Show your 6on7 trust level, tier and which verifications are approved, pending or missing. 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.read, 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 |
|---|---|---|
| No arguments. | ||
Example request
POST https://onelifevibe.com/mcp
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "sixonseven_get_verification_status",
"arguments": {}
}
}Other 6on7 tools
- sixonseven_list_notifications notifications
- sixonseven_mark_notifications_read mark notifications read
What it does
sixonseven_get_verification_status reports your 6on7 trust standing in a single call. 6on7 is dating for an actual relationship, and every profile shows what that person has verified, so the status this tool returns is the same information other people see about you.
It answers four things: your trust level, your tier as a level and a name, the state of the email, phone, photo and id verifications, and whether you can message. Each verification comes back as approved, pending or missing. It is a Read tool, which means it changes nothing on the account.
You pass no input. There is no member id or handle to supply, because the connector resolves the person from their OneLifeVibe sign-in.
When an assistant should call it
Call it when someone asks where they stand on 6on7, what their profile shows as verified, or whether they can send messages. It is the right first check before you suggest any work: if id is pending, the honest answer is that it is pending, not that they should start it.
It also works as a cheap pre-check before other 6on7 actions. Pair it with sixonseven_list_notifications when someone wants a full picture of what needs attention, and reach for sixonseven_mark_notifications_read only after they confirm they have read those notifications.
Because the call is read-only, you can run it at the top of a conversation and again later to show what changed, without touching anything in between.
Inputs and an example call
There are no inputs. The request is the tools/call method naming sixonseven_get_verification_status with an empty arguments object, sent to https://onelifevibe.com/mcp.
Account connector: the person signs in with OneLifeVibe using OAuth 2.1 with PKCE and the scope olv.read. They must also have signed in to 6on7.com with OneLifeVibe at least once, otherwise the tool answers not_linked. The connector's sign-in is set up for Meta Muse today under the client onelifevibe-muse; other MCP clients reach the no-account tools through the free connector.
Platform API: the tool 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. A platform key is for the world catalogue, the tool registry, the network directory tool and the event log.
What comes back
The response carries trust_level, tier with level and name, verifications with email, phone, photo and id, and can_message. Each verification entry tells you whether that check is approved, pending or missing, which is exactly what you need to say what is done and what is not.
Read the fields together. A pending item is not a failure; the check was started and has not come back approved yet. A missing item has not been submitted. Use trust_level and tier when someone asks how their standing is described, and can_message when they ask whether messaging is available to them.
Report the values as they come back rather than translating them into a rating of your own.
Errors, limits and safety
not_linked means the connector has a valid OneLifeVibe sign-in but the person has not signed in to 6on7.com with OneLifeVibe yet. Ask them to do that once, then call again; retrying without that sign-in returns the same answer.
501 world_tools_unavailable means the call came from a platform key. Move it to the account connector at https://onelifevibe.com/mcp with the olv.read scope.
The tool is read-only and idempotent, so retries are safe and there is nothing to confirm before running it. It accepts no member identifier, so it only ever reports the signed-in person's own status. 6on7 is for adults 18 and over.
Questions
Why does sixonseven_get_verification_status return not_linked?
The connector has a OneLifeVibe sign-in, but the person has not signed in to 6on7.com with OneLifeVibe yet. Have them sign in there once with OneLifeVibe, then call the tool again.
Can I call this tool 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 olv.read scope instead.
Does calling it change anything on the account?
No. It is a Read tool and it is idempotent, so repeated calls return the same status and nothing on the account is modified.
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.