MCP Protocol Tracker

by MikeyBeez

Overview Schema Related Servers Score Discussions

JavaScript

Local

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.1
Disambiguation4/5
Most tools have clear, distinct purposes: logging steps, logging activities, and logging violations are differentiated by their descriptions. However, protocol_log_step and protocol_log_activity could be confused since both involve logging, and protocol_check_compliance and protocol_get_session_report both provide status-related information, though one focuses on compliance and the other on a full report.
Naming Consistency4/5
The naming pattern is highly consistent with a protocol_ prefix followed by verb_noun (start_session, log_step, log_activity, log_violation, check_compliance, get_session_report, suggest_missing). The only deviation is the generic 'help' tool, which breaks the pattern but is a common utility.
Tool Count5/5
Eight tools is well within the typical 3-15 range and feels appropriate for a protocol tracking server. Each tool addresses a core function like starting sessions, logging events, checking compliance, and generating reports, with no unnecessary bloat.
Completeness3/5
The surface covers session start, logging, compliance checks, reporting, and suggestions, but lacks an explicit end_session or close_session tool, which would be a natural lifecycle step. Additionally, there is no tool to update or correct logged steps/activities, which could be a limitation if mistakes occur.
Average 3.3/5 across 8 of 8 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.
MCP servers without a LICENSE cannot be installed.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get comprehensive session activity report' without explaining what the report contains, whether it requires an active session, if it modifies data, or any limitations. This is a significant gap for a read operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no redundant words. It is front-loaded with the action verb 'Get' and immediately conveys the resource, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema and no annotations, so the description should clarify what the report includes. It only says 'comprehensive', which is vague, and omits any mention of what data is aggregated or how the report relates to session logging. The description is under-specified for a tool of this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter includeDetails is fully described in the schema with 'Include detailed step-by-step breakdown', achieving 100% schema description coverage. The description does not add any further meaning, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get comprehensive session activity report' clearly identifies the action (get) and the resource (session activity report). It is distinct from sibling tools like protocol_start_session or protocol_log_step, but it does not explicitly distinguish itself from them beyond the resource type.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, use cases, or exclusions. Sibling tools such as protocol_check_compliance or protocol_log_activity are not referenced, leaving the agent without context for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden. It only states the action ('Log') without disclosing side effects, persistence, required permissions, or return behavior. This is minimal and leaves much unknown.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that is easy to parse. However, it is extremely sparse and could include more guidance without becoming verbose. It earns credit for brevity but not perfection.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the existence of multiple logging siblings, the description lacks necessary context to differentiate usage. It does not explain what 'significant activity' means or how this tool relates to protocol_log_step/violation. The absence of an output schema or annotations amplifies the gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with each parameter individually described. The description itself adds no meaning beyond the schema; it does not explain how parameters relate or provide examples. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a clear verb ('Log') and specifies a resource ('any significant activity or tool usage'). It is not a tautology, but it fails to distinguish from sibling tools like protocol_log_step and protocol_log_violation, which serve similar logging purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description implies a broad logging function but does not state exclusions or contrast with sibling tools, leaving the agent to guess the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Log completion' and omits the fact that the tool supports 'skipped' and 'failed' statuses, potential side effects on session state, or any error conditions. The wording even contradicts the schema's status enum, which is a notable transparency gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, grammatically complete sentence of six words. It is maximally concise with zero wasted words, front-loading the verb and resource. This is appropriate for a simple logging tool, though it sacrifices behavioral detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has three parameters, a status enum, and sibling tools, the description is insufficiently complete. It does not explain the role of the 'status' parameter, how this relates to protocol sessions, or when to use it over protocol_log_activity/violation. The absence of output schema could be acceptable, but the missing usage context and behavioral nuances leave clear gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds no additional semantic meaning beyond the schema—it merely echoes the 'completion' idea found in the step parameter description, which is itself somewhat misleading relative to the status enum. No supplementary parameter context is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Log') and resource ('protocol step'), making the primary action clear. It implicitly distinguishes from sibling tools like protocol_log_activity and protocol_log_violation by focusing on 'step,' but the phrase 'completion' is slightly misleading given the status parameter allows 'skipped' and 'failed.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The description does not mention protocol sessions, prerequisites, or any exclusions for when this tool is inappropriate. It simply states the action without contextual direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Start tracking a new protocol session' without mentioning side effects such as whether previous sessions are closed, if multiple sessions can coexist, or whether a session ID is returned for subsequent calls. This is a mutation operation lacking any side-effect disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no extraneous words. It is front-loaded with the verb and resource, making it immediately understandable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without an output schema, the description should explain what the tool returns or how the session is identified for future protocol logging calls, but it does not. It also fails to mention the relationship to sibling tools, leaving the agent without knowledge of the session lifecycle.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both sessionType and expectedProtocols having descriptive text. The tool description adds no additional parameter semantics, so the baseline of 3 is appropriate because the schema already provides clear meanings.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Start tracking a new protocol session' clearly states the action (start tracking) and the resource (protocol session). It is distinct from sibling tools like protocol_log_step and protocol_log_activity, which focus on logging events rather than initialization.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives. It does not mention that this should be called before logging steps, nor does it note any prerequisites or exclusions. The sibling context suggests other protocol tools, but no usage relationship is described.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for disclosing behavior. The verb 'check' implies a non-mutating operation, but the description does not explicitly state that it leaves state unchanged, nor does it explain what 'compliance status' entails or what errors may occur. It adds some transparency but leaves room for ambiguity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It states the action and target clearly, making it concise and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters and no output schema, the description should explain what the caller receives or how compliance status is determined. It does not, and it also fails to distinguish itself from the similar-looking protocol_get_session_report. The description is minimally viable but leaves gaps about output format and usage context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema is empty, meaning there is nothing to document. The baseline for 0-parameter tools is 4, and the description's purpose statement adds contextual meaning, even though it does not mention parameter details (as none exist).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'check' and the resource 'protocol compliance status', clearly indicating a read-only diagnostic action. It is unambiguous about the operation. However, it does not differentiate itself from the sibling tool protocol_get_session_report, which may also report on compliance status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as protocol_get_session_report or protocol_suggest_missing. The description lacks any context about prerequisites, typical invocation scenarios, or which sibling tools are better suited for specific needs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the transparency burden. It only states that the tool logs, without disclosing whether it stores, validates, requires authentication, or returns any confirmation. The behavioral impact remains opaque.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, compact sentence conveys the essential purpose. It is appropriately sized and front-loaded with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the schema fully documents parameters, the description omits contextual details such as how log entries are stored, whether a protocol session must be active, and what callers should expect as a result. The absence of an output schema and annotations makes this minimal description insufficient for confident invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for every parameter, so the baseline is 3. The description adds no semantic detail beyond the schema; it simply restates the tool's purpose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the verb 'log' and the resource 'protocol violation or compliance issue', making it distinct from sibling logging tools like protocol_log_step and protocol_log_activity which target different event types.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when a violation occurs, but provides no explicit guidance on when to prefer this over alternative logging tools such as protocol_log_activity, nor does it mention prerequisites like an active session.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states that the tool suggests missing steps, but does not explain how it determines 'missing', whether it requires an active session, if it has side effects, or what the response format looks like. This lack of detail leaves significant behavioral ambiguity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with no redundant information. It efficiently conveys the core purpose without unnecessary detail, making it highly concise and appropriately structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With only one parameter and no output schema, the description should provide enough context for an agent to understand what the tool returns and how to use it effectively. It only mentions 'suggest missing protocol steps' but does not describe the output format, return types, or any prerequisites, leaving the tool incomplete for practical use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides 100% coverage for the single parameter 'currentContext', with a description of 'Current work context or situation'. The tool description mentions 'current activity', which aligns with the schema description but does not add further semantic meaning, such as examples, formatting, or allowed values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific action verb 'Suggest' and identifies the resource as 'missing protocol steps', making the tool's purpose clear. It also distinguishes itself from sibling tools like protocol_log_step and protocol_check_compliance, as it is focused on proactively suggesting gaps rather than logging or checking.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'based on current activity' gives an implicit context for when to use the tool, but there is no explicit guidance on when not to use it or how it differs from alternatives like protocol_check_compliance. The description does not mention exclusions or alternative tools, leaving the usage scenario only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It indicates the tool returns documentation but does not explicitly state that it is a read-only operation or describe the output format. The read-only nature is inferred from the verb 'Get' but not fully disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that places the action verb upfront and contains no wasted words. It is concise while conveying the complete purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simple nature and empty schema, the description provides the essential context. It does not describe the output format, but this is partially excused by the absence of an output schema. The description is adequate for a help tool, though it could benefit from indicating the form of documentation returned.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, so the description does not need to explain parameter semantics. Per the rubric, a tool with no parameters receives a baseline of 4, and the empty schema confirms there is nothing to elaborate on.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb ('Get') and resource ('comprehensive documentation for all protocol-tracker functions'). This distinguishes it from sibling tools that perform protocol operations like logging or compliance checking.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use case (when to access documentation) is self-evident from the description, but no explicit guidance is given about when to prefer this over alternatives or what circumstances call for it. The usage is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![mcp-protocol-tracker MCP server](https://glama.ai/mcp/servers/MikeyBeez/mcp-protocol-tracker/badges/card.svg)](https://glama.ai/mcp/servers/MikeyBeez/mcp-protocol-tracker)

Score Badge

Copy to your README.md:

[![mcp-protocol-tracker MCP server](https://glama.ai/mcp/servers/MikeyBeez/mcp-protocol-tracker/badges/score.svg)](https://glama.ai/mcp/servers/MikeyBeez/mcp-protocol-tracker)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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