Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"agentseal": {
"env": {
"AGENTSEAL_API_KEY": "as_sk_your_key_here"
},
"args": [
"-y",
"agentseal-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for AgentSeal. Tamper-proof audit logs for AI agents, using SHA-256 hash chains.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'agentseal-sdk' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked agentseal-sdk against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security / devops
MCP server for using the GitLab API
All-in-One Sandbox for AI Agents that combines Browser, Shell, File, MCP and VSCode Server in a single Docker container.
A Unified MCP Server Management App (MCP Manager).
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
MCP Security Weekly
Get CVE alerts and security updates for io.github.JoeyBrar/agentseal and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"agentseal": {
"command": "npx",
"args": ["-y", "agentseal-mcp"],
"env": {
"AGENTSEAL_API_KEY": "as_sk_your_key_here"
}
}
}
}
Restart Claude Desktop after saving.
Same configuration — add the server with your API key.
| Variable | Required | Description |
|---|---|---|
AGENTSEAL_API_KEY | Yes | Your API key from agentseal.io |
AGENTSEAL_URL | No | Custom API base URL (defaults to production) |
record_actionRecord 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_actionsLook 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_chainVerify 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.
Each recorded action is hashed with SHA-256. That hash includes the previous entry's hash, forming a chain. Modify any record and every hash after it changes — verify_chain catches it instantly.
Sign up at agentseal.io. Free to use.
For direct integration without MCP: pip install agentseal-sdk. See agentseal-sdk.
MIT