person.work — Agent-maintained CV
REMOTE · PERSON.WORK · SCANNED SEP 22
Maintain your CV with your agent. Review changes, then share one record as web, PDF and open data.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add --transport http work-person-career-record 'https://person.work/api/mcp'
{
"mcpServers": {
"work-person-career-record": {
"url": "https://person.work/api/mcp"
}
}
} {
"servers": {
"work-person-career-record": {
"type": "http",
"url": "https://person.work/api/mcp"
}
}
} [mcp_servers.work-person-career-record] url = "https://person.work/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"work-person-career-record": {
"type": "remote",
"url": "https://person.work/api/mcp",
"enabled": true
}
}
} openclaw mcp add work-person-career-record --url 'https://person.work/api/mcp' --transport streamable-http
mcp_servers:
work-person-career-record:
url: "https://person.work/api/mcp" {
"McpServers": {
"work-person-career-record": {
"Transport": "http",
"Url": "https://person.work/api/mcp"
}
}
} assistant mcp add work-person-career-record -t streamable-http -u 'https://person.work/api/mcp'
{
"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.
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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Sept 26 76
First indexed and scored.
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 22 Sept 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 | 1 Sept 2026 | 30 Nov 2026 | RSA 2048 | SHA256-RSA | 56b2349fc6bd0eecfd17e401980bdcdb033 |
| SANs: *.person.work, 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. | present | 16252 | 8 | Verified |
| person.work. | absent | 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 |
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 →
get_my_career_record Get the authenticated owner's 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 Get an opt-in public Career Record ~52
Returns one public Career Record whose owner explicitly enabled MCP visibility. Contact values are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| include_extensions | boolean | – | – |
| username | string | yes | The person.work profile slug |
No output schema declared.
No examples provided.
propose_my_career_change Propose an ongoing CV change for owner review ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| diff_summary | array | – | – |
| instruction | string | yes | – |
| proposed_patch | object | yes | – |
| source_label | – | – | – |
No output schema declared.
No examples provided.
sync_my_profile Import a complete existing CV for the authenticated owner ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| experiences | array | yes | – |
| 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 | yes | – |
No output schema declared.
No examples provided.
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.