# Agent-Carried Work History (remote · textforagents.com)

Your agent carries its own resume — outcome receipts minted at settlement, held by the agent.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `textforagents.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-textforagents-agent-carried-work-history/products-agent-carried-work-history-mcp.md), [page](https://verifymcp.io/servers/com-textforagents-agent-carried-work-history/products-agent-carried-work-history-mcp)

## Channel facts

- Endpoint: `https://textforagents.com/products/agent-carried-work-history/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.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-11-05.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 373 tokens (~53/item across 7 items; 7 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**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Agent-Carried Work History MCP server?

Agent-Carried Work History is a hosted endpoint at https://textforagents.com/products/agent-carried-work-history/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 com-textforagents-agent-carried-work-history 'https://textforagents.com/products/agent-carried-work-history/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-textforagents-agent-carried-work-history": {
      "url": "https://textforagents.com/products/agent-carried-work-history/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-textforagents-agent-carried-work-history": {
      "type": "http",
      "url": "https://textforagents.com/products/agent-carried-work-history/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-textforagents-agent-carried-work-history]
url = "https://textforagents.com/products/agent-carried-work-history/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-textforagents-agent-carried-work-history": {
      "type": "remote",
      "url": "https://textforagents.com/products/agent-carried-work-history/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-textforagents-agent-carried-work-history --url 'https://textforagents.com/products/agent-carried-work-history/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-textforagents-agent-carried-work-history:
    url: "https://textforagents.com/products/agent-carried-work-history/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-textforagents-agent-carried-work-history": {
      "Transport": "http",
      "Url": "https://textforagents.com/products/agent-carried-work-history/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-textforagents-agent-carried-work-history -t streamable-http -u 'https://textforagents.com/products/agent-carried-work-history/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-textforagents-agent-carried-work-history": {
      "type": "http",
      "url": "https://textforagents.com/products/agent-carried-work-history/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-11-05 (score 74, +1)

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

### 2026-11-03 (score 73, +1)

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

### 2026-10-31 (score 72, +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-10-30 (score 71, 0)

- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-29 (score 71, +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-10-27 (score 70, +1)

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

### 2026-10-25 (score 69, +1)

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

### 2026-10-24 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (7)

### `close_and_mint` (~105 tokens)

Settlement close that mints the outcome receipt into the agent wallet as a condition of SETTLED. First mint free once per agent; then x402 $0.01 (or wallet plan).

Input parameters:

- `agent_id` (string, required)
- `counterparty_class` (string, required)
- `outcome` (string, required)
- `source_kind` (string, required)
- `task_class` (string, required)
- `tx_id` (string, required)
- `value_band` (string, required)

### `mint_receipt` (~90 tokens)

Mint an outcome receipt directly. First mint free once per agent; then x402 $0.01 (or wallet plan).

Input parameters:

- `agent_id` (string, required)
- `counterparty_class` (string, required)
- `outcome` (string, required)
- `source_kind` (string, required)
- `task_class` (string, required)
- `tx_id` (string, required)
- `value_band` (string, required)

### `aggregate_proof` (~61 tokens)

Registry-signed aggregate proof over an agent's history (counts/dispute rate, no receipts surrendered). x402 $0.05 per 1,000 receipts in the set.

Input parameters:

- `agent_id` (string, required)
- `task_class` (string)

### `verify_proof` (~23 tokens)

Verify an aggregate proof. Free.

Input parameters:

- `proof` (object, required)

### `verify_receipts` (~39 tokens)

Completeness check of a surrendered receipt list vs registry ground truth. Free.

Input parameters:

- `agent_id` (string, required)
- `receipts` (array, required)

### `check_tx` (~31 tokens)

MINTED or NEVER_MINTED for a transaction id. Free.

Input parameters:

- `tx_id` (string, required)

### `export_wallet` (~24 tokens)

Export your agent's wallet as JSON.

Input parameters:

- `agent_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-textforagents-agent-carried-work-history/products-agent-carried-work-history-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 69
- 2026-10-25: 69
- 2026-10-24: 68
- 2026-10-23: 68

## Common questions

### What is the Agent-Carried Work History MCP server?

Agent-Carried Work History is an MCP server listed in the public MCP registry as com.textforagents/agent-carried-work-history. Your agent carries its own resume, outcome receipts minted at settlement, held by the agent. This page covers its hosted endpoint (https://textforagents.com/products/agent-carried-work-history/mcp).

### Is the Agent-Carried Work History MCP server safe to use?

Agent-Carried Work History scores 74 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 Agent-Carried Work History MCP server expose?

Agent-Carried Work History exposes 7 tools: close_and_mint, mint_receipt, aggregate_proof, verify_proof, verify_receipts, and 2 more. Their descriptions and schemas cost roughly 373 tokens of context every time the server is loaded.

### Does the Agent-Carried Work History MCP server require authentication?

Yes. Agent-Carried Work History 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 Agent-Carried Work History MCP server still maintained?

Agent-Carried Work History is still listed as active in the MCP registry. We last reached this channel on 5 November 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://textforagents.com/products/agent-carried-work-history/mcp
- Website: https://textforagents.com/products/agent-carried-work-history/
- Changelog RSS feed: https://verifymcp.io/servers/com-textforagents-agent-carried-work-history/products-agent-carried-work-history-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-textforagents-agent-carried-work-history/products-agent-carried-work-history-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-textforagents-agent-carried-work-history/products-agent-carried-work-history-mcp