Server Details
Write better IR reports, improve security writing, and plan cybersecurity product strategy.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
14 toolsget_articleInspect
Get the full content of a specific article from Lenny Zeltser's Website by URL path. Security articles on malware analysis, incident response, and security leadership. Returns title, date, topics, summary, and full body text.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Article URL path (e.g., '/about', '/article-slug') |
get_capabilitiesInspect
List all capabilities and tools available from the Lenny Zeltser's Website MCP server, including search tools and any specialized features like IR report writing assistance.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_index_infoInspect
Get statistics about the Lenny Zeltser's Website search index including total pages indexed, last update time, and available tools.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_security_writing_guidelinesInspect
Get Lenny Zeltser's expert writing guidelines for security reports and assessments. Provides guidance on tone, structure, clarity, executive summaries, and avoiding common writing mistakes. Works for any security document. Your documents are never sent to this server—guidelines flow to your AI for local analysis. Note: For incident response reports specifically, use the ir_* tools which provide deeper section-by-section review criteria.
| Name | Required | Description | Default |
|---|---|---|---|
| focus | No | Which aspects of writing to focus on. 'tone': voice, do/avoid examples. 'structure': paragraphs, report qualities, formatting. 'clarity': sentences, jargon alternatives. 'executive_summary': exec summary best practices. 'critique': writing as critique not criticism. 'analytical': evidence attribution, confidence language, comparative language, gap acknowledgment. 'all' or omit for everything. | |
| include_examples | No | Include before/after examples. Default: true. Set to false for smaller response. |
ir_get_guidelinesInspect
Get Lenny Zeltser's expert writing guidelines for incident response reports. Topics: tone, words, structure, executive_summary, voice, articles, or summary for quick reference. Your incident data is never sent to this server—guidelines flow to your AI for local analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Specific topic: tone (collaborative framing), words (clarity, jargon), structure (paragraphs, headings), executive_summary (exec summary rules), voice (style guidelines), articles (related reading), or summary for a quick reference card. Omit for full guidelines. |
ir_get_templateInspect
Get Lenny Zeltser's structured incident response report template. Covers all critical IR sections with field-by-field guidance. Your incident data is never sent to this server—guidelines flow to your AI for local analysis.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
ir_load_contextInspect
Load Lenny Zeltser's IR report writing context for local analysis. Returns expert guidelines for field completeness, incident identification, notification triggers, and writing quality. Your AI uses this context to analyze your incident notes locally—your notes are never sent to this server. Use detail_level to control response size: "minimal" (~2k tokens), "standard" (~5k tokens), or "comprehensive" (~11k tokens).
| Name | Required | Description | Default |
|---|---|---|---|
| topics | No | Specific topics to load. Overrides detail_level for fine-grained control. Options: completeness (field guidance), incidents (type identification), notifications (regulatory triggers), writing (style analysis), actions (urgency categorization), stakeholders (party identification), sections (review criteria). | |
| detail_level | No | Level of detail to return. 'minimal': core field guidance only (~2k tokens). 'standard': field guidance + writing analysis + notifications (~5k tokens, default). 'comprehensive': everything including examples and all incident types (~11k tokens). | |
| incident_type | No | Load guidance for a specific incident type only (saves tokens). Omit to load all types when 'incidents' topic is included. | |
| include_examples | No | Include good/poor examples in field guidance. Default: false. Set to true for learning/training. |
ir_review_reportInspect
Get Lenny Zeltser's expert criteria for reviewing an existing IR report. Returns focused guidance for constructive critique — what to check in each section, writing quality issues to identify, and how to frame feedback collaboratively. Your AI uses this to analyze your report locally—your report is never sent to this server.
| Name | Required | Description | Default |
|---|---|---|---|
| focus | No | What aspects to focus on. 'completeness': is everything covered? 'clarity': jargon, passive voice, vague terms. 'tone': collaborative framing. 'structure': sentence/paragraph organization. | |
| sections | No | Specific sections to get review criteria for. Omit or use 'all' for complete review criteria. |
product_compare_contextInspect
Load Lenny Zeltser's comparative analysis framework for evaluating multiple security companies side by side. Returns structured scoring rubric, evaluation dimensions, evidence tiering guidance, and comparison-type-specific instructions. Requires comparative analysis content. Your product plans are never sent to this server—guidelines flow to your AI for local analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| company_count | Yes | Number of companies being compared (2-10). | |
| comparison_type | Yes | Type of comparison. 'competition': direct/adjacent competitors. 'market_segment': companies in same segment. 'portfolio': cohort evaluation. | |
| include_scoring_rubric | No | Include the structured 1-5 scoring rubric. Default: true. |
product_get_guidelinesInspect
Get Lenny Zeltser's expert strategic guidelines for a specific product strategy topic. Topics: market (segmentation), capabilities (AI, agents, MVP, positioning), sales (GTM, channels, distribution, POCs), pricing (models, retention), delivery (deployment, APIs), trust (compliance, security program), platform (ecosystem positioning), team (expertise, gaps), competitive (differentiation, moats), smb (SMB market dynamics), endpoint (endpoint viability), ai_security (AI security vertical), role (product manager responsibilities), category_creation (new category strategy), comparative (multi-company analysis), evidence_tiering (evidence classification framework). Your product plans are never sent to this server—guidelines flow to your AI for local analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Specific topic to get guidelines for. Omit or use 'all' for a complete overview. |
product_get_templateInspect
Get Lenny Zeltser's fill-in-the-blank template for planning a security product strategy. Includes strategic questions organized by section with evidence columns. Your product plans are never sent to this server—guidelines flow to your AI for local analysis. The template is Copyright (c) 2026 Lenny Zeltser; any content you create using it is entirely yours.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
product_load_contextInspect
Load Lenny Zeltser's product strategy context for local analysis. Returns expert strategic frameworks, principles, and guidance for evaluating or creating security product plans. Your AI uses this context to analyze your product plans locally—your plans are never sent to this server. Use detail_level to control response size: "minimal" (~2k tokens), "standard" (~5k tokens), "compact" (~3-4k tokens, all sections but stripped), or "comprehensive" (~12k tokens). Use market_segment: "smb" for SMB-specific guidance. Use product_focus: "endpoint" for endpoint security viability assessment. Set include_template: true to include the fill-in-the-blank template in the response.
| Name | Required | Description | Default |
|---|---|---|---|
| topics | No | Specific topics to include. Overrides detail_level for fine-grained control. | |
| detail_level | No | Level of detail to return. "minimal": market + capabilities only (~2k tokens). "standard": core strategy sections (~5k tokens, default). "compact": all sections with stripped subsections (~3-4k tokens, good for batch analysis). "comprehensive": everything + examples (~12k tokens). | |
| analysis_mode | No | 'internal': planning your own product (default). 'external': evaluating another company from outside. External mode reframes questions and adjusts evidence standards. | |
| product_focus | No | Include vertical-specific guidance. 'endpoint': platform entrapment, defensibility. 'ai_security': AI threat landscape, buyer personas, regulatory alignment. | |
| market_segment | No | Include SMB-specific guidance (distribution, buying triggers, readiness). | |
| company_context | No | Filter guidance to startup or large company perspective. Stage values (pre_seed, seed, series_a, series_b, growth, late_stage) imply startup context with stage-specific emphasis. | |
| include_examples | No | Include examples in framework sections. Default: false. | |
| include_template | No | Include the fill-in-the-blank strategy template at the end of the context response. Default: false. Saves a separate product_get_template call. | |
| evaluation_perspective | No | Emphasize framework sections relevant to a specific perspective. Composes with analysis_mode. |
product_review_planInspect
Get Lenny Zeltser's expert criteria for reviewing an existing product strategy plan. Returns focused guidance for constructive critique—what to check in each section, strategic coherence issues, and how to frame feedback collaboratively. Your AI uses this to analyze your plan locally—your plan is never sent to this server. Use market_segment: "smb" to include SMB-specific review criteria. Use product_focus: "endpoint" to include endpoint viability assessment.
| Name | Required | Description | Default |
|---|---|---|---|
| focus | No | What aspects to focus on. 'completeness': is everything covered? 'strategy': are decisions coherent? 'feasibility': can this team execute? | |
| sections | No | Specific sections to get review criteria for. Omit or use 'all' for complete review criteria. | |
| review_type | No | 'internal': reviewing your own plan (default). 'external-analysis': reviewing an analysis of another company. Adjusts criteria to focus on evidence tiering, source attribution, and marketing language. | |
| product_focus | No | Include vertical-specific review criteria. 'endpoint': endpoint viability. 'ai_security': AI security market assessment. | |
| market_segment | No | Include SMB-specific review criteria. |
search_zeltserInspect
Search Lenny Zeltser's Website by keywords. Security articles on malware analysis, incident response, and security leadership. Searches across titles, abstracts, full content, and topics.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (default: 10, max: 25) | |
| query | Yes | Search terms to find relevant content |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Last verification attempt failed.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!