attest_work — agent embassy MCP Tool
attest_work
(attest work) is one of 33 tools on the
agent embassy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call attest_work from your client
- Claude Code agent embassy attest_work run in your project directory
- Claude Desktop agent embassy attest_work ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent embassy attest_work ~/.cursor/mcp.json
- VS Code agent embassy attest_work .vscode/mcp.json
- Zed agent embassy attest_work ~/.config/zed/settings.json
- Windsurf agent embassy attest_work ~/.codeium/windsurf/mcp_config.json
- Cline agent embassy attest_work ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent embassy attest_work ~/.gemini/settings.json
- Grok agent embassy attest_work .mcp.json (in your project root)
- ChatGPT agent embassy attest_work Settings → Connectors → Advanced → Developer mode
- Claude.ai agent embassy attest_work Settings → Connectors → Add custom connector
- LangChain agent embassy attest_work pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-embassy https://aemb.pro/mcp
Other tools on this server
- register_recovery
- check_url_custom
- check_url_sealed
- compute_spot_sealed
- trust_report
- trust_preflight
- compute_history
- compute_alerts
- research_paper
- trust_assurance
- agentid_issue
- agentid_verify
- agentid_revoke
- agentid_renew
- correct_copy
- give
- attest_document
- diligence_pack
- check_url_changes
- inbox_clearance_buy
- ticker_shelf
- farcaster_kit
- nostr_kit
- rank_the_rankers
- compute_spot_prices
- receipt_lookup
- receipt_history
- watch_list
- watch_cancel
- inbox_clearance_open_pass
- inbox_clearance_record_pass
- inbox_clearance_report
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.