Official description10 sourcesMCP servers8d ago

JoeyBrar/agentseal-mcp

Action logs for AI agents: recor

View on GitHub ↗Direct link · no redirect page

Config template (adjust for your client)

claude mcp add agentseal-mcp -- npx -y agentseal-mcp

A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.

Star count: 2 ★ · JoeyBrar/agentseal-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source: collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history: first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 10 sources
Score: score 1,003 · 2 ★ · 10 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

repository JoeyBrar/agentseal-mcp；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

agentseal-mcp

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

MCP server for AgentSeal. Tamper-proof audit logs for AI agents, using SHA-256 hash chains.
Every agent action is recorded in a hash chain. With this, you can actually prove to your clients that your agent did what it said it did.
Setup
Claude Desktop
Add to your claude_desktop_config.json:
Restart Claude Desktop after saving.
Cursor / Other MCP hosts
Same configuration — add the server with your API key.
Environment variables
| Variable | Required | Description |
|---|---|---|
| AGENTSEAL_API_KEY | Yes | Your API key from agentseal.io |
| AGENTSEAL_URL | No | Custom API base URL (defaults to production) |
Tools
record_action
Record an agent action to the audit trail. Call this after significant actions to create a cryptographically chained record of what happened and why.
| Parameter | Type | Required | Description |
|---|---|---|---|
| agent_id | string | Yes | Identifier for the agent (e.g. research-bot) |
| action_type | string | Yes | What kind of action (e.g. email:send, file:write, api:call) |
| action_params | object | No | Details of the action |
| reasoning | string | No | Why the agent decided to take this action |
| authorized_by | string | No | Who or what approved the action |
Returns a sequence number and SHA-256 hash confirming the entry was chained.
query_actions
Look up previously recorded actions from the audit trail. Use this to check what actions have been taken or recall past decisions.
| Parameter | Type | Required | Description |
|---|---|---|---|
| agent_id | string | No | Filter by agent |
| action_type | string | No | Filter by action type |
| limit | number | No | Max entries to return (default 20) |
verify_chain
Verify the integrity of the hash chain. Each entry's SHA-256 hash includes the previous entry's hash — if any record was modified, the chain breaks and this reports where.
| Parameter | Type | Required | Description |
|---|---|---|---|
| agent_id | string | No | Verify chain for a specific agent. If omitted, verifies all entries. |
Returns the number of entries verified and whether the chain is intact.
How it works