MCP Protocol Tracker
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Protocol TrackerStart a new initialization protocol session"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Protocol Tracker
A Model Context Protocol (MCP) tool for tracking protocol adherence, logging initialization sequences, and maintaining comprehensive audit trails of Claude's activities.
Purpose
This tool was created to address a fundamental limitation in MCP workflows: the lack of protocol adherence tracking and audit trails. It provides systematic monitoring of whether documented procedures are being followed and maintains detailed logs of all activities.
Related MCP server: PiQrypt MCP Server
Features
Core Functionality
Session Tracking: Detailed logging of every Claude session with unique IDs
Protocol Compliance Scoring: Calculates adherence to documented procedures (0-100 scale)
Activity Logging: Records every significant action with context and timestamps
Violation Detection: Flags when protocols are bypassed or skipped
Comprehensive Reporting: Detailed session reports with compliance metrics
Available Tools
protocol_start_session
Start tracking a new protocol session
{
"sessionType": "initialization|work|exploration|debugging",
"expectedProtocols": ["protocol1", "protocol2"] // optional
}protocol_log_step
Log completion of a protocol step
{
"protocolName": "brain_init_sequence",
"step": "brain_init() executed",
"status": "completed|skipped|failed" // optional, defaults to completed
}protocol_log_activity
Log any significant activity or tool usage
{
"activity": "Description of what was done",
"tool": "tool_name", // optional
"context": "Why this was done" // optional
}protocol_log_violation
Log a protocol violation or compliance issue
{
"violation": "Description of what went wrong",
"severity": "low|medium|high|critical",
"protocolName": "violated_protocol" // optional
}protocol_check_compliance
Check current protocol compliance status
Returns compliance score (0-100)
Shows protocols followed, violations, and activity count
Provides session duration
protocol_get_session_report
Get comprehensive session activity report
{
"includeDetails": true|false // optional, includes detailed activity log
}protocol_suggest_missing
Suggest missing protocol steps based on current activity
{
"currentContext": "Description of current work context"
}Compliance Scoring
Score Calculation:
Base score: (Completed required protocols / Total required protocols) × 70%
Violation penalty: Up to 30 points deducted based on severity and count
Final range: 0-100
Score Interpretation:
80-100: ✅ Excellent
60-79: ⚠️ Good
40-59: 🔶 Poor
0-39: ❌ Critical
Installation & Setup
Install Dependencies
npm installAdd to Claude Desktop Config Add to your
claude_desktop_config.json:{ "mcpServers": { "protocol-tracker": { "command": "node", "args": ["/path/to/mcp-protocol-tracker/src/index.js"], "description": "Protocol adherence tracking and audit trail system" } } }Restart Claude Desktop
Usage Examples
Starting a Session
protocol_start_session({
"sessionType": "initialization",
"expectedProtocols": ["brain_init_sequence", "architecture_maintenance"]
})Logging Protocol Steps
protocol_log_step({
"protocolName": "brain_init_sequence",
"step": "Read Boot Loader Index - CRITICAL"
})Checking Compliance
protocol_check_compliance()
// Returns: Compliance Score: 60/100 ⚠️ GoodIntegration with Workflow
This tool integrates with Claude's workflow by:
Gentle Reminders: Added to frequently-used tools like
brain_statusandcheck_remindersProtocol Enforcement: Can be extended to block actions until prerequisites are met
Continuous Monitoring: Tracks all activities for post-session analysis
Session Logs
Session logs are stored in ~/mcp/protocol_logs/session_[timestamp].json with:
Session metadata and timing
Complete activity log with timestamps
Protocol compliance tracking
Violation records with severity levels
Compliance score history
Development
Project Structure
mcp-protocol-tracker/
├── src/
│ └── index.js # Main MCP server implementation
├── package.json # Dependencies and metadata
└── README.md # This documentationKnown Protocols
The tool currently tracks these built-in protocols:
brain_init_sequence: Brain initialization stepsarchitecture_maintenance: System documentation updatessession_handover: Clean context transitions
Additional protocols can be added by extending the KNOWN_PROTOCOLS object.
Future Enhancements
Git repository integration
Automated testing suite
Protocol auto-detection and suggestions
Integration with Master Protocol Index
Web dashboard for compliance trends
Export capabilities (JSON, HTML, CSV)
Pattern recognition for workflow optimization
Created
July 28, 2025 - In response to identified gaps in MCP protocol adherence tracking.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MikeyBeez/mcp-protocol-tracker'
If you have feedback or need assistance with the MCP directory API, please join our Discord server