Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

person.work — Agent-maintained CV

REMOTE · PERSON.WORK

Maintain your CV with your agent. Review changes, then share one record as web, PDF and open data.

Available components

0 this week 90 Trust /100

Last scanned (19 hours ago)

Scores higher than 97% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 377 tokens (~94/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 27% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Oct 26 0
    • Authorization: unverified → pass ▲ security
  • 13 Oct 26 0
    • Authorization: pass → unverified ▼ security
  • 10 Oct 26 0
    • Stability: 0.93 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://person.work/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=person.work CN=YR1,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 RSA 2048 SHA256-RSA 515b1cb80cc671490ce13a121581d8be59a
SANs: person.work
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of person.work. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
work. DS published 33659 13 Verified
person.work. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Missing Authorization header", scope="upstand:unclassified-tool-deny", resource_metadata="https://person.work/.well-known/oauth-protected-resource/api/mcp"

Bearer error="invalid_token", error_description="Missing Authorization header", scope="upstand:unclassified-tool-deny", resource_metadata="https://person.work/.well-known/oauth-protected-resource/api/mcp"
Header Value
strict-transport-security max-age=63072000

Protected resource metadata

Document https://person.work/.well-known/oauth-protected-resource/api/mcp
Retrieved Yes
Resource https://person.work/api/mcp
Authorisation server https://ekgcdubapswckxdgxgei.supabase.co/auth/v1

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://person.work/api/mcp Verified 200
http (plaintext) http://person.work/api/mcp HTTPS enforced 308 https://person.work/api/mcp
MCP tools · 4 exposed · ~377 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_my_career_record ~38

Returns the OAuth-authenticated owner's canonical record. Read this before proposing an ongoing CV update so stable experience identifiers and confirmed facts are preserved.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_profile ~52

Returns one public Career Record whose owner explicitly enabled MCP visibility. Contact values are excluded.

NameTypeReqDescription
formatstring––
include_extensionsboolean––
usernamestringyesThe person.work profile slug

No output schema declared.

No examples provided.

propose_my_career_change ~95

Adds a structured, human-readable diff to the owner's review inbox. Experience upserts may include a public HTTPS company_logo_url; person.work imports its own protected copy only after owner approval. Use this for normal maintenance after the initial import; the agent cannot apply or publish it.

NameTypeReqDescription
diff_summaryarray––
instructionstringyes–
proposed_patchobjectyes–
source_label–––

No output schema declared.

No examples provided.

sync_my_profile ~192

Explicit initial-import operation for structured facts already interpreted by the calling agent. It does not accept or store a raw CV, PDF, or source text, and person.work does not run a second AI interpretation. The operation deterministically validates the payload and atomically creates a private profile when needed or replaces the owner's profile facts and complete experience list. Experiences may include a public HTTPS company_logo_url; person.work imports a protected copy. Use null to remove a logo and omit the field to preserve it. Identity is required only for first creation. Never use this for routine updates.

NameTypeReqDescription
experiencesarrayyes–
extensionobject–Typed profession fields (e.g. primaryLanguages, seniority). Replaces the stored fields of that extension; omit to leave them untouched.
identityobject–Required only when this initial sync creates the authenticated owner's private person.work profile.
profileobjectyes–

No output schema declared.

No examples provided.

Install

How do I install the person.work — Agent-maintained CV MCP server?

person.work — Agent-maintained CV is a hosted endpoint at https://person.work/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · person.work

# add to Claude Code
claude mcp add --transport http work-person-career-record 'https://person.work/api/mcp'
Common questions

What is the person.work — Agent-maintained CV MCP server?

person.work — Agent-maintained CV is an MCP server listed in the public MCP registry as work.person/career-record. Maintain your CV with your agent. Review changes, then share one record as web, PDF and open data. This page covers its hosted endpoint (https://person.work/api/mcp).

Is the person.work — Agent-maintained CV MCP server safe to use?

person.work — Agent-maintained CV scores 90 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the person.work — Agent-maintained CV MCP server expose?

person.work — Agent-maintained CV exposes 4 tools: get_profile, sync_my_profile, get_my_career_record, propose_my_career_change. Their descriptions and schemas cost roughly 377 tokens of context every time the server is loaded.

Does the person.work — Agent-maintained CV MCP server require authentication?

Yes. person.work — Agent-maintained CV asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the person.work — Agent-maintained CV MCP server still maintained?

person.work — Agent-maintained CV is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the person.work — Agent-maintained CV MCP server?

VerifyMCP ran 13 checks on person.work — Agent-maintained CV, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.