Execution Trace Logger Connector for AI agents.
3 live capabilities
Create unchangeable cryptographic audit trails for agent workflows
Waiting for input…
Why people use Execution Trace Logger
Stop agent tampering with Execution Trace Tamper-Evident Logger
This MCP changes the game by moving from text logs to cryptographic proofs. Instead of just writing a line of text, every action is hashed into a Merkle tree. This creates a mathematical link between every step. If anyone tries to change a single bit of data in the past, the entire chain breaks, and you'll know immediately. You get a permanent, unchangeable record of truth.
What Vinkius changes
You get a mathematically unchangeable record of everything your agent does.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
Auditing financial transactions
An agent managing a budget uses log_execution_step to record every transfer, creating a trail that cannot be faked.
- Real-world use case 02
Debugging autonomous software agents
When an agent breaks a build, use verify_trace_integrity to confirm the exact sequence of events that led to the error.
- Real-world use case 03
Regulatory compliance for AI
A legal tech agent uses get_step_verification_proof to provide undeniable evidence of how it reached a specific conclusion.
Complete set · 3capabilities
The complete Execution Trace Logger capability set.
These are the exact actions your AI can choose when you ask it to work with Execution Trace Logger.
01—03
3 capabilities in this set.
Part of 3 available through Execution Trace Logger.
- 01 Capability
Get step verification proof
Retrieves the specific cryptographic proof for a single action. This allows you to validate one step in isolation.
- 02 Capability
Log execution step
Records a new action into the cryptographic log. This updates the Merkle tree to include the new step.
- 03 Capability
Verify trace integrity
Checks the entire execution history for tampering. It compares the current state against a trusted root.
Set up in minutes
One URL. Then ask Execution Trace Logger to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Execution Trace Logger from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_GW8BvCg5B7MVAIjoMOnFVFF0MUD4HLRgzh1x9P0c/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Execution Trace Logger, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Execution Trace Logger for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_GW8BvCg5B7MVAIjoMOnFVFF0MUD4HLRgzh1x9P0c/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Execution Trace Logger URL.
- Step 03
Save and start
Save the connection and enable Execution Trace Logger in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"execution-trace-tamper-evident-logger": {
"url": "https://edge.vinkius.com/vk_preview_GW8BvCg5B7MVAIjoMOnFVFF0MUD4HLRgzh1x9P0c/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Execution Trace Logger
Open Agent mode in chat and ask: "Using Execution Trace Logger, help me...". 3 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"execution-trace-tamper-evident-logger": {
"url": "https://edge.vinkius.com/vk_preview_GW8BvCg5B7MVAIjoMOnFVFF0MUD4HLRgzh1x9P0c/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Execution Trace Logger
Ask Copilot: "Using Execution Trace Logger, help me...". 3 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"execution-trace-tamper-evident-logger": {
"url": "https://edge.vinkius.com/vk_preview_GW8BvCg5B7MVAIjoMOnFVFF0MUD4HLRgzh1x9P0c/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Execution Trace Logger
Open Cascade and ask: "Using Execution Trace Logger, help me...". 3 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"execution-trace-tamper-evident-logger": {
"url": "https://edge.vinkius.com/vk_preview_GW8BvCg5B7MVAIjoMOnFVFF0MUD4HLRgzh1x9P0c/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Execution Trace Logger
Ask Cline: "Using Execution Trace Logger, help me...". 3 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add execution-trace-tamper-evident-logger --transport http "https://edge.vinkius.com/vk_preview_GW8BvCg5B7MVAIjoMOnFVFF0MUD4HLRgzh1x9P0c/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Execution Trace Logger
Ask Claude: "Using Execution Trace Logger, show me...". 3 tools are ready
Where the request belongs
Work Execution Trace Logger can move forward.
This is for engineers and security teams who can't afford 'black box' AI behavior and need a verifiable paper trail for autonomous workflows.
AI Security Engineer
Ensures that agentic workflows haven't been compromised by verifying the integrity of the execution logs.
DevOps Engineer
Uses the audit trails to debug complex, multi-step agentic processes in production environments.
Compliance Officer
Relies on the tamper-evident logs to meet regulatory requirements for automated decision-making.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsPiLAB
Manage infrastructure and security via PiLAB. control PiVirt virtual machines, inspect PiTrust certificates, and oversee 3SO OAuth clients directly from any AI agent.
Sentry
Grant your AI agent full access to Sentry's Application Performance Monitoring capabilities to track raw exceptions, resolve error logs, and inspect crash stack traces dynamically.
Doppler
Manage secrets and environment variables via Doppler. list projects, audit secrets, and track activity logs from any AI agent.
OOPSpam
Block spam submissions on your forms and comments with an AI-powered filter that catches bots without annoying real users.
X Ads (Twitter)
Connect your X Ads account to any AI agent. audit campaigns, analyze line item performance, and pull engagement reports through natural conversation.
Box
Store, share, and collaborate on files securely with enterprise-grade cloud content management and governance controls.
Bring your own AI
Change the model, client or framework. Keep Execution Trace Logger connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Execution Trace Logger.
The practical details behind the request, access and result.
How does the Execution Trace Tamper-Evident Logger protect my agent's history?
It uses Merkle trees and SHA-256 hashing to create a chain of events where every step is mathematically linked. This makes it impossible to change any past action without breaking the entire chain, alerting you to tampering.
Can I use the Execution Trace Tamper-Evident Logger to audit specific agent decisions?
Yes. You can extract specific cryptographic proofs for any individual step in the execution history, allowing you to verify the exact path taken for any specific decision.
Is the Execution Trace Tamper-Evident Logger compatible with my existing AI client?
Yes, as long as your client is MCP-compatible, such as Claude, Cursor, or Windsurf, you can connect this to start recording secure logs immediately.
What happens if an agent's log is actually tampered with?
The integrity check will fail. When you run a verification command, the calculated root won't match the stored root, signaling that the history has been altered.
Does the Execution Trace Tamper-Evident Logger slow down my agent?
The cryptographic hashing is extremely fast. While there is a tiny amount of overhead for each step, it is designed to run in the background without impacting the agent's core logic.
How does this ensure the logs haven't been changed?
The server builds a Merkle tree where the root hash represents the entire trace. If any step is altered, the root hash will no longer match, which you can detect using verify_trace_integrity.
What is an execution step?
An execution step is the atomic unit of an agent's activity, such as a single thought or action. You record these using log_execution_step to build the audit trail.
Can I verify a single step without checking the whole log?
Yes, you can use get_step_verification_proof to retrieve the specific cryptographic proof needed to validate a single step hash against the Merkle root.
One connection away
Give your agent a direct line to Execution Trace Logger.
Connect Execution Trace Logger once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available