Proof of concept

Self.me Identity Prototype

Self.me holds your verified record. AI assistants like Claude and ChatGPT can find you, ask about you, and verify you — but only what you choose to share, only with your approval, and you can take it back at any time.

1 · Add it to your AI assistant

Claude

Navigate to Settings → Connectors
Click Add custom connector
Enter the following:
- Name: Self.me
- Remote MCP server URL: https://id-poc.self.me/mcp
Click Add
Next to the new Self.me connector, click Connect
Sign in with your Self.me account — or click Sign up to create one on the spot

ChatGPT

Navigate to Settings → Plugins (turn Developer Mode on)
Click + to create a New Plugin
Enter the following:
- Name: Self.me
- Connection · Server URL: https://id-poc.self.me/mcp
- Authentication: OAuth
Check “I understand and want to continue”, then click Create
Next to the new Self.me plugin, click Connect
Sign in with your Self.me account — or click Sign up to create one on the spot

New Plugin

Name

Self.me

Connection · Server URL

https://id-poc.self.me/mcp

Authentication

OAuth

⚠ Custom MCP servers introduce risk.

☑I understand and want to continue

Create

Signing in is the setup — there are no API keys and nothing to install.

2 · Two roles, one connector

Candidate / Individual

It's your record. See who's asking, approve or deny each request, and revoke access any time — right from the chat.

Recruiter / Verifier

Search the opt-in directory, request access, and get verified, receipt-backed answers instead of unverified résumés.

The role isn't a setting — it's simply whose record it is. You act as an owner on your own record and as a verifier on anyone else's.

2b · Demo accounts & the cast

Recruiter sign-ins

gtuvell+recruiter@self.me — George
mikef+recruiter@self.me — Mike

Recruiter seats own no records — they search, request, and verify.

Candidate sign-ins

gtuvell+candidate@self.me — George, acting as Aisha (and Sam)
mikef+candidate@self.me — Mike, acting as David and Maria

Consent requests for a profile go to the account that owns it. Sign-in codes arrive at the base inbox (gtuvell@ / mikef@).

The cast — who shows up in searches

Aisha Thompson — BSN nursing student, Charlotte NC. Pediatrics interest, ICU/med-surg rotations, issuer-verified clinical screening. Graduates May 2027. (owned by George's candidate seat)
David Okafor — Travel nurse (RN), ICU/step-down, Houston TX. TX compact license (covers NC via NLC), partner background check on record. Available now. (owned by Mike's candidate seat)
Maria Vasquez — Licensed home inspector, Raleigh NC. Post-storm damage assessments, drone-certified. Auto-approves license checks via a standing consent policy. (owned by Mike's candidate seat)
Sam Rivera — HVAC technician, Denver CO. Opted out of the directory — Sam never appears in searches, proving listing is opt-in. (owned by George's candidate seat)

All profiles are fictional test data. Every search returns only these opt-in public cards — private records stay behind consent.

3 · Try it — the whole story in six prompts

Recruiter, in Claude:

Use self.me: find nurses within 20 miles of Charlotte. Request access to Aisha's verifications for a new-grad residency screening.

Candidate, in ChatGPT:

List pending access requests on my records — who is asking, and for what? Approve the residency screening request.

Recruiter again:

Verify Aisha's clinical-placement background screening and her pediatrics rotation — show the signed receipt. Now widen the search: which nurses could legally work in North Carolina today? Compare them and explain each one's licensure.

Candidate, any time:

Show my disclosure log, then revoke that recruiter's access.

What that just proved: discovery, consent before depth, an issuer-verified background screening answered with a cryptographic receipt, real multi-state license logic across candidates, and the individual in control end to end

4 · How your data stays protected

You choose what's public. The directory shows only what you opted to publish — nothing more.
Everything else needs your yes. Private details are shared per request, per scope, and only after you approve. You can revoke at any time.
No scraping, by design. There is no way to bulk-download profiles. Every query comes from a signed-in, identified account (with rate limits coming as we open up).
Answers, not documents. Assistants get scoped answers with a signed receipt — the record itself never leaves Self.me.
Sensitive data stays with the source. Background checks and IDs remain with verifying partners; Self.me stores the verified outcome, not your SSN, DOB, or documents — and responses are automatically screened for personal identifiers.
Every disclosure is on the record. A tamper-evident receipt and an audit log you can read in plain English.

This is a proof of concept by Self.me. All directory profiles are fictional test data (except where noted). Verifications marked “simulated” illustrate partner integrations (e.g., background screening) without real reports. Not a consumer reporting agency; not for making eligibility decisions.