# 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.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `person.work`: 82/100 (this document), [markdown](https://verifymcp.io/servers/work-person-career-record/api-mcp.md), [page](https://verifymcp.io/servers/work-person-career-record/api-mcp)

## Channel facts

- Endpoint: `https://person.work/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 377 tokens (~94/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 27% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http work-person-career-record 'https://person.work/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "work-person-career-record": {
      "url": "https://person.work/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "work-person-career-record": {
      "type": "http",
      "url": "https://person.work/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.work-person-career-record]
url = "https://person.work/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "work-person-career-record": {
      "type": "remote",
      "url": "https://person.work/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add work-person-career-record --url 'https://person.work/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  work-person-career-record:
    url: "https://person.work/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "work-person-career-record": {
      "Transport": "http",
      "Url": "https://person.work/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add work-person-career-record -t streamable-http -u 'https://person.work/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "work-person-career-record": {
      "type": "http",
      "url": "https://person.work/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 77, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-09 (score 76)

First indexed and scored.

## MCP tools (4)

### `get_profile` (~52 tokens)

Get an opt-in public Career Record

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

Input parameters:

- `format` (string)
- `include_extensions` (boolean)
- `username` (string, required): The person.work profile slug

### `sync_my_profile` (~192 tokens)

Import a complete existing CV for the authenticated owner

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.

Input parameters:

- `experiences` (array, required)
- `extension` (object): Typed profession fields (e.g. primaryLanguages, seniority). Replaces the stored fields of that extension; omit to leave them untouched.
- `identity` (object): Required only when this initial sync creates the authenticated owner's private person.work profile.
- `profile` (object, required)

### `get_my_career_record` (~38 tokens)

Get the authenticated owner's Career Record

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.

### `propose_my_career_change` (~95 tokens)

Propose an ongoing CV change for owner review

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.

Input parameters:

- `diff_summary` (array)
- `instruction` (string, required)
- `proposed_patch` (object, required)
- `source_label`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/work-person-career-record/api-mcp#diagnostics

## Score history

- 2026-09-22: 82
- 2026-09-21: 82
- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76

## 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 82 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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://person.work/api/mcp
- Website: https://person.work/onboarding/agent
- Changelog RSS feed: https://verifymcp.io/servers/work-person-career-record/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/work-person-career-record/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/work-person-career-record/api-mcp