Local MCP capabilities provider for Expo
Website Search is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Improve security writing, score it against rubrics, plan IR, CTI, vuln, and product strategy.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http website-search-mcp https://website-mcp.zeltser.com/mcp
# 2 — ask your agent for something these tools do
# search_zeltser, get_article, get_index_info and 50 more
Website Search costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http website-search-mcp https://website-mcp.zeltser.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
53 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms to find relevant content |
| limit | number | no | Maximum number of results to return (default: 10, max: 25) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Article URL path or full URL (e.g., '/about', '/article-slug', or the full URL printed by search results) |
Get statistics about the Lenny Zeltser's Website search index including total pages indexed, last update time, and available tools.
No parameter schema on file.
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.
No parameter schema on file.
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. Includes rating-sheet items (the four lens sheets: structure, look, words, tone) as concrete reference points for grounded feedback. Works for any security document. This server never requests your documents an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| focus | array | 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 summ |
| include_examples | boolean | no | Include before/after examples. Default: true. Set to false for smaller response. |
Get Lenny Zeltser's structured incident response template. Covers all critical IR sections with field-by-field guidance. Pass kind: "report" (default — full incident-response report) or "brief" (one-page executive brief, IR 1.5.0+). This server never requests your incident notes and instructs your AI to keep them local—guidelines flow to your AI for local analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Which artifact to return: 'report' (full incident-response report — default for backward compatibility) or 'brief' (one-page executive brief). |
Get Lenny Zeltser's expert writing guidelines for incident response reports. Topics: tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance, IR 1.5.0+), frameworks (regulatory + maturity frameworks), handoffs (cross-server routing). When the topic maps to a lens (tone, words, structure), the response includes a rating-sheet checklist appendix as
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Specific topic: tone (collaborative framing), words (clarity, jargon), structure (paragraphs, headings), executive_summary (exec summary rules), voice (style guidelines), articles (related reading), s |
Load Lenny Zeltser's IR report writing context for local analysis. Returns expert guidelines for field completeness, incident identification, notification triggers, and writing quality. Includes rating-sheet items (lens taxonomy plus the IR-specific Information sheet) as concrete reference points for grounded feedback. This server never requests your incident notes and instructs your AI to keep th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_level | string | 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 |
| topics | array | no | Specific topics to load. Overrides detail_level for fine-grained control. Options: completeness (field guidance), incidents (type identification), notifications (regulatory triggers), writing (style a |
| incident_type | string | no | Load guidance for a specific incident type only (saves tokens). Omit to load all types when 'incidents' topic is included. |
| include_examples | boolean | no | Include good/poor examples in field guidance. Default: false. Set to true for learning/training. |
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. Includes rating-sheet items (lens taxonomy plus the IR-specific Information sheet) as concrete reference points for grounded feedback. This server never requests yo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sections | array | no | Specific sections to get review criteria for. Omit or use 'all' for complete review criteria. |
| focus | array | no | What aspects to focus on. 'completeness': is everything covered? 'clarity': jargon, passive voice, vague terms. 'tone': collaborative framing. 'structure': sentence/paragraph organization. |
Get Lenny Zeltser's fill-in-the-blank template for planning a security product strategy. Includes strategic questions organized by section with evidence columns. This server never requests your product plans and instructs your AI to keep them local—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.
No parameter schema on file.
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), de
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Specific topic to get guidelines for. Omit or use 'all' for a complete overview. |
Load Lenny Zeltser's product strategy context for local analysis. Returns expert strategic frameworks, principles, and guidance for evaluating or creating security product plans. Includes rating-sheet items (the lens taxonomy: structure, words, tone) as concrete reference points for grounded feedback on the plan's writing. This server never requests your plans and instructs your AI to keep them lo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_level | string | 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 |
| topics | array | no | Specific topics to include. Overrides detail_level for fine-grained control. |
| company_context | string | 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. |
| market_segment | string | no | Include SMB-specific guidance (distribution, buying triggers, readiness). |
| product_focus | string | no | Include vertical-specific guidance. 'endpoint': platform entrapment, defensibility. 'ai_security': AI threat landscape, buyer personas, regulatory alignment. |
| include_examples | boolean | no | Include examples in framework sections. Default: false. |
| include_template | boolean | 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. |
| analysis_mode | string | no | 'internal': planning your own product (default). 'external': evaluating another company from outside. External mode reframes questions and adjusts evidence standards. |
| evaluation_perspective | string | no | Emphasize framework sections relevant to a specific perspective. Composes with analysis_mode. |
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. Includes rating-sheet items (the lens taxonomy: structure, words, tone) as concrete reference points for grounded feedback on the plan's writing. This server neve
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sections | array | no | Specific sections to get review criteria for. Omit or use 'all' for complete review criteria. |
| focus | array | no | What aspects to focus on. 'completeness': is everything covered? 'strategy': are decisions coherent? 'feasibility': can this team execute? |
| market_segment | string | no | Include SMB-specific review criteria. |
| product_focus | string | no | Include vertical-specific review criteria. 'endpoint': endpoint viability. 'ai_security': AI security market assessment. |
| review_type | string | 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. |
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. This server never requests your product plans and instructs your AI to keep them local—guidelines flow to your AI for local
| Parameter | Type | Required | Notes |
|---|---|---|---|
| comparison_type | string | yes | Type of comparison. 'competition': direct/adjacent competitors. 'market_segment': companies in same segment. 'portfolio': cohort evaluation. |
| company_count | integer | yes | Number of companies being compared (2-10). |
| include_scoring_rubric | boolean | no | Include the structured 1-5 scoring rubric. Default: true. |
Get Lenny Zeltser's cybersecurity-writing rating sheet(s) so your AI can apply the rubric. Returns the structured rubric (groups, items, scoring bands) WITHOUT computing a score. Use rating_score_writing if you also want a numeric score, gap analysis, or rubric-anchored feedback. This server never requests your draft and instructs your AI to keep it local—rating sheets and scoring instructions f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sheet | string | no | Which sheet to return. 'structure' / 'look' / 'words' / 'tone' apply to any document. 'info-ir' / 'info-assessment' / 'info-threat' are document-type-specific. 'all' returns the full bundle (default). |
Get Lenny Zeltser's scoring playbook so your AI can score a draft locally against a cybersecurity-writing rating sheet. THIS IS THE ONLY TOOL THAT PRODUCES NUMERIC SCORES — the writing-coach tools (get_security_writing_guidelines, ir_*, product_*) never score. Returns the rubric plus step-by-step instructions for applying it. This server never requests your draft and instructs your AI to kee
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sheet | string | yes | Which sheet to apply. The 7 canonical IDs name a specific rubric. 'auto' picks among the three Information sheets (info-ir / info-assessment / info-threat) based on the document type the user describe |
| mode | string | no | score: per-item pass/fail + total + band classification (default). gaps: enumerate items the draft does NOT satisfy (best fit for Information sheets). feedback: per-item pass/fail + total + band, then |
| detail_level | string | no | minimal: scoring playbook only. standard: rubric + scoring playbook (default). comprehensive: rubric + scoring playbook + cross-references to writing guidelines + related articles. |
Load Lenny Zeltser's complete cybersecurity-writing rating toolkit: all 7 sheets, scoring policy, scoring playbook, and cross-references to the writing guidelines. This server never requests your draft and instructs your AI to keep it local—rating sheets and scoring instructions flow to your AI.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_level | string | no | minimal: sheet metadata + scoring playbook only (~2k tokens). standard: full sheets + scoring playbook + cross-references (~6k tokens, default). comprehensive: everything including related articles an |
Load Lenny Zeltser's AI Defense Matrix context: the 8-asset x 6-NIST-CSF-2.0-function matrix, nine cross-walked frameworks (NIST IR 8596, CSA AICM, ISO 42001, Google SAIF, SANS Critical AI Security Guidelines, MITRE ATLAS, OWASP AI Exchange, OWASP LLM Top 10, OWASP Agentic Top 10), and the evaluation + cross-mapping playbooks. This server never requests your program docs or product roadmap and ins
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purpose | string | no | evaluate_program: practitioner playbook for assessing an AI security program. cross_map_product: vendor playbook for mapping product capabilities to matrix cells. general: both playbooks (default). |
| detail_level | string | no | minimal: matrix summary counts only, no playbooks or framework rows. standard: full matrix, framework alignments, and the selected playbook(s) (default). comprehensive: everything including related ar |
Get the structured AI Defense Matrix: 8 AI-specific asset rows x 6 NIST CSF 2.0 function columns. Each cell describes a control category for defending that asset class. Supports optional filtering by asset or function. This server never requests your program docs or product roadmap and instructs your AI to keep them local—the matrix, framework alignments, and playbooks flow to your AI for local an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| format | string | no | structured: typed JSON of assets, functions, and cells (default). markdown: human-readable rendering grouped by asset. |
| asset | string | no | Optional: filter to one asset class (e.g., 'ai-model', 'training-data'). Returns the 6 cells for that row. |
| function | string | no | Optional: filter to one NIST CSF function ('govern', 'identify', 'protect', 'detect', 'respond', 'recover'). Returns the 8 cells for that column. |
Get AI Defense Matrix cross-mappings to nine external frameworks: NIST IR 8596, CSA AI Controls Matrix, ISO 42001, Google SAIF, SANS Critical AI Security Guidelines, MITRE ATLAS, OWASP AI Exchange, OWASP LLM Top 10, OWASP Agentic Security Top 10. Each row maps an AI asset class to how that framework applies. Each returned framework also carries a 'concepts' array of the structured IDs (MITRE ATLAS
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | no | Optional: scope to one framework slug (e.g., 'mitre-atlas', 'owasp-llm-top10'). Omit to get all nine. Wins over 'buyer' if both are passed. |
| buyer | string | no | Optional: scope to a buyer archetype's framework subset. federal: NIST IR 8596 + ISO 42001. ai-governance: ISO 42001 + CSA AICM. app-security: OWASP LLM Top 10 + OWASP AI Exchange. threat-modeler: MIT |
Get the AI Defense Matrix evaluation playbook for assessing an AI security program: per-cell prompts, gap-inventory template, and a workflow that walks each asset class first and rolls findings up to the Govern column. Supports mode='gate' for binary deployment-gate decisions (returns the deployment-gate workflow plus gate-tier prompts only) and consumerPattern for scoping to consumed-vs-built AI
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | no | Optional: focus the prompts on one asset class. |
| assets | array | no | Optional: focus the prompts on multiple asset classes (e.g., for a deployment that touches orchestration + runtime data + agent identities). Takes precedence over asset if both are set. |
| function | string | no | Optional: focus the prompts on one NIST CSF function. |
| mode | string | no | assessment (default): full program assessment — all maturity tiers. gate: binary deployment-gate decision — returns the deploymentGateWorkflow plus only gate-tier prompts (drops 90-day and mature prom |
| consumer_pattern | string | no | consumed: organization consumes a third-party model (GPT-4 via API) — drops AI-Workload Platforms, Training Data, AI-Generated Code rows, and AI Model identify/protect/detect/respond/recover (keeps ai |
| framework | string | no | Optional: scope cellPrompts to those whose 'sources' field cites the named framework. Accepts a bare slug ('iso-42001') for any prompt citing that framework, or a 'framework:concept-id' form ('mitre-a |
Get the AI Defense Matrix cross-mapping playbook for mapping product capabilities to matrix cells: coverage taxonomy (primary, secondary, partial, aspirational), differentiation guidance, disambiguation block, worked examples, and out-of-scope examples. The response always includes an inScopeCheck. Products that USE AI to solve a non-AI security problem (deepfake detection, AI-for-fraud, AI featur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework | string | no | Optional: include only one external framework's cross-mapping (e.g., 'owasp-llm-top10') alongside the playbook. |
| whitespace | boolean | no | Optional: when true, surface a whitespace.sparseCells block scoped to cells with at most one product in the AI Defense Matrix Catalog where a product can plausibly succeed (vendorDensity <= 1 AND co |
| include_process_shaped | boolean | no | Optional: when true with whitespace, lift the coverageType filter so process and cdm-rollup cells with at most one cataloged product appear too. Use when you want to see all sparse cells regardless of |
| include_framework_alignment | boolean | no | Optional: when false, the framework alignment block (~half the response) is omitted in favor of a short note pointing to aidefense_get_framework_alignment. Use when the caller will fetch alignment sep |
Reverse-lookup a single concept ID (MITRE ATLAS technique like 'AML.T0051', OWASP LLM Top 10 risk like 'LLM01', OWASP Agentic Top 10 issue like 'ASI03', or ISO 42001 Annex A clause like 'A.6') across the AI Defense Matrix. Returns which framework the concept belongs to, the asset rows whose alignment cites it, the cells whose evaluation cellPrompts cite it, and those prompts themselves. Useful whe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| concept | string | yes | A single concept ID. Recognized patterns: 'AML.T<4 digits>(.<3 digits>)?' (MITRE ATLAS), 'LLM<2 digits>' (OWASP LLM Top 10), 'ASI<2 digits>' (OWASP Agentic Top 10), 'A.<digits>' (ISO 42001 Annex A cla |
Get Lenny Zeltser's IR one-page executive brief template. Standalone variant of ir_get_template for callers that only want the brief without the long-form report. This server never requests your incident notes and instructs your AI to keep them local—guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's IR cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of ir_load_context. This server never requests your incident notes and instructs your AI to keep them local—guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's IR frameworks (primary frameworks the brief structurally derives from) plus optional sibling frames (adjacent frameworks that aren't the structural backbone). Pass include_siblings: false to skip sibling blocks. This server never requests your incident notes and instructs your AI to keep them local—guidelines flow to your AI for local analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_siblings | boolean | no | Include the siblingFrames block (adjacent frameworks with whyOmitted notes) and the siblingArtifacts block (related templates) in the response. Default: true. |
Get Lenny Zeltser's cyber threat intel template. The long report covers Executive Summary, Actor Snapshot, Methodology, Activity Overview, Representative Adversary Techniques, Indicators of Compromise, Defensive Implications, Attribution Analysis, Anticipated Activity, optional Strategic Analysis and Competing Hypotheses, plus About this Report. The one-page brief covers Bottom Line, Quick Facts,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| template | string | no | Which artifact to return: 'report' (12-section long report, default) or 'brief' (one-page executive brief). |
Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (sig
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Which topic to surface. Defaults to a 'summary' overview when omitted. |
| field_id | string | no | Only meaningful with topic='fields'. When supplied, returns guidance for the named field id. When omitted under topic='fields', returns a directory of available field ids. |
Load Lenny Zeltser's CTI writing context for local analysis. Returns a JSON payload with section guidance, completeness criteria, framework grounding (12 frameworks), the six attribution signals, ICD-203 confidence levels and ladder, and the Pyramid of Pain. The 'profile' parameter ANNOTATES sections (internal/public applicability label) rather than filtering — every section is returned so cross-p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_level | string | no | Response size: minimal (~2-3k tokens), standard (~5-7k), comprehensive (~12k+). |
| topics | array | no | Narrow the response to specific topics; 'all' includes everything. |
| profile | string | no | Annotate sections by their applicability to this profile (internal or public). Sections are NOT filtered — annotated only. |
| template | string | no | Foreground 'report' or 'brief' sections; both lists stay in the payload. |
| include_examples | boolean | no | Include exampleGood/examplePoor in fieldGuidance entries. |
Get Lenny Zeltser's expert criteria for reviewing an existing CTI report or brief. Surfaces per-theme review criteria (framework, confidence, attribution, defense, distribution, etc.), cross-cutting criteria, the six anti-patterns to watch for, and focus-driven writing analysis. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and gu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sections | array | no | Narrow to specific report sections; 'all' includes every section. |
| focus | array | no | Focus areas: completeness, clarity, tone, structure, attribution, confidence, or all. |
Get Lenny Zeltser's CTI one-page executive brief template. Standalone variant of cti_get_template for callers that only want the brief without the long-form report. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's CTI cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of cti_load_context. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's CTI frameworks (primary frameworks the brief structurally derives from) plus optional sibling frames (adjacent frameworks that aren't the structural backbone). Pass include_siblings: false to skip sibling blocks. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_siblings | boolean | no | Include the siblingFrames block (adjacent frameworks with whyOmitted notes) and the siblingArtifacts block (related templates) in the response. Default: true. |
Get Lenny Zeltser's malware analysis report template. The report covers Executive Summary, Sample Snapshot, Malware Family Identification, Component Inventory, Runtime Requirements, Sources, Capabilities, Indicators of Compromise, Analysis Details, What We Don't Know, optional Infection Vector, optional Detection Engineering, About this Report, Appendix: Analysis Environment, and optional Appendix
No parameter schema on file.
Get Lenny Zeltser's expert malware analysis report writing guidelines. Topics include capabilities, confidence, pyramid_of_pain, anti_patterns, methodology, fields, handoffs, frameworks, plus tone, words, structure, and executive_summary topics that defer to get_security_writing_guidelines for canonical Five Elements guidance. Pair the 'fields' topic with field_id for single-field guidance. This
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Which topic to surface. Defaults to a 'summary' overview when omitted. |
| field_id | string | no | Only meaningful with topic='fields'. When supplied, returns guidance for the named field id. When omitted under topic='fields', returns a directory of available field ids. |
Load Lenny Zeltser's malware analysis report writing context for local analysis. Returns a JSON payload with section guidance, the MBC capability model, ICD-203 confidence scoped to the family call, Pyramid-of-Pain IOC tiering, and a briefPolicy explaining why there is no companion brief. The 'profile' parameter ANNOTATES sections (organizationalReport/researcherNarrative applicability label) rath
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_level | string | no | Response size: minimal, standard, or comprehensive. |
| topics | array | no | Narrow the response to specific topics; 'all' includes everything. |
| profile | string | no | Annotate sections by their applicability to this profile. Sections are NOT filtered — annotated only. |
| include_examples | boolean | no | Include exampleGood/examplePoor in fieldGuidance entries. |
Get Lenny Zeltser's expert criteria for reviewing an existing malware analysis report. Surfaces per-theme review criteria for identification, capabilities, indicators, evidence, ecosystem, detection, reproducibility, and distribution; cross-cutting criteria; anti-patterns; and focus-driven writing analysis. This server never requests your sample, analysis notes, or indicators and instructs your AI
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sections | array | no | Narrow to specific report sections; 'all' includes every section. |
| focus | array | no | Focus areas: completeness, clarity, tone, structure, capabilities, confidence, anti_patterns, or all. |
Get Lenny Zeltser's Malware cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of malware_load_context. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's Malware frameworks (primary frameworks the brief structurally derives from) plus optional sibling frames (adjacent frameworks that aren't the structural backbone). Pass include_siblings: false to skip sibling blocks. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_siblings | boolean | no | Include the siblingFrames block (adjacent frameworks with whyOmitted notes) and the siblingArtifacts block (related templates) in the response. Default: true. |
Get Lenny Zeltser's one-page Vulnerability Advisory Brief template. Covers Bottom Line, Quick Facts, Are We Affected?, Defensive Actions (with What/Why/When/Who), What We Don't Know, and More Information. This server never requests your vulnerability notes and instructs your AI to keep them local—the brief template and guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's expert vulnerability-brief writing guidelines. Topics include tone, words, structure, voice, articles, summary, fields (per-field guidance), handoffs (cross-server routing), and vuln-specific topics: significance (calibrated insecurity, no vendor passthrough — note this is the Vuln Brief's Significance row, distinct from CVSS/vendor severity scoring), actions (action-enabling W
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Which topic to surface. Defaults to a 'summary' overview when omitted. |
| field_id | string | no | Only meaningful with topic='fields'. When supplied, returns guidance for the named field id. When omitted under topic='fields', returns a directory of available field ids. |
Load Lenny Zeltser's Vulnerability Investigation Brief context for local analysis. Returns a JSON payload with brief section guidance, completeness criteria, significance discipline (renamed from 'severity' in 1.1.0 — the Vuln Brief's Significance row, distinct from CVSS or vendor severity scoring), evidence-source guidance, frameworks (CVSS / CVE / NVD / CISA KEV / Vendor Advisory), and ALWAYS em
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_level | string | no | Response size: minimal, standard, or comprehensive. |
| topics | array | no | Narrow the response to specific topics; 'all' includes everything. |
| include_examples | boolean | no | Include exampleGood/examplePoor in fieldGuidance entries. |
Get Lenny Zeltser's expert criteria for reviewing an existing Vulnerability Investigation Brief. Surfaces per-theme review criteria (significance, scope, actions, gaps, sources), cross-cutting criteria, anti-patterns, and inline mcpHandoffs pointers when the requested focus triggers scoring or writing-mechanics themes (e.g., focus=tone surfaces rating_score_writing). This server never requests you
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sections | array | no | Narrow to specific brief sections; 'all' includes every section. |
| focus | array | no | Focus areas: completeness, clarity, tone, structure, significance, actions, sources, or all. |
Get Lenny Zeltser's Vuln one-page executive brief template. Standalone variant of vuln_get_template for callers that only want the brief without the long-form report. This server never requests your vulnerability notes and instructs your AI to keep them local—the brief template and guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's Vuln cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of vuln_load_context. This server never requests your vulnerability notes and instructs your AI to keep them local—the brief template and guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's Vuln frameworks (primary frameworks the brief structurally derives from) plus optional sibling frames (adjacent frameworks that aren't the structural backbone). Pass include_siblings: false to skip sibling blocks. This server never requests your vulnerability notes and instructs your AI to keep them local—the brief template and guidelines flow to your AI for local analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_siblings | boolean | no | Include the siblingFrames block (adjacent frameworks with whyOmitted notes) and the siblingArtifacts block (related templates) in the response. Default: true. |
Get Lenny Zeltser's security assessment template. The report is a reader-first findings report: Executive Summary, Assessment Scope, Findings Summary, Detailed Findings, Remediation Priorities, optional Attack Path Narrative and Detection and Response Observations, Methodology, Limitations and Disclaimer, Appendices, and About this Report. The one-page brief covers Bottom Line, Key Findings, Recom
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Which artifact to return: 'report' (full findings report, default) or 'brief' (one-page executive brief). |
Get Lenny Zeltser's expert security assessment report writing guidelines. Topics: severity (the risk-adjusted severity model — the spine), findings, remediation, methodology, scope, strengths, brief (one-page brief section guidance), executive_summary, analysis, anti_patterns, frameworks, handoffs, and summary. The general 'tone' topic defers to get_security_writing_guidelines for the canonical
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Which topic to surface. Defaults to a 'summary' overview when omitted. |
Load Lenny Zeltser's security assessment report writing context for local analysis. Returns a JSON payload with the risk-adjusted severity model (the spine), reader-first section guidance, completeness criteria, frameworks (NIST SP 800-115/800-30, OWASP WSTG/Risk Rating, CVSS, MITRE ATT&CK, PTES, PCI DSS, CREST), and the mcpHandoffs array. The 'profile' parameter ANNOTATES sections (internal/exter
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail_level | string | no | Response size: minimal, standard, or comprehensive. |
| topics | array | no | Narrow the response to specific topics; 'all' includes everything. |
| profile | string | no | Annotate sections by applicability to this profile (internal or external). Sections are NOT filtered — annotated only. |
| template | string | no | Foreground 'report' or 'brief' sections; both lists stay in the payload. |
| include_examples | boolean | no | Include exampleGood/examplePoor in fieldGuidance entries. |
Get Lenny Zeltser's expert criteria for reviewing an existing security assessment report or brief. Surfaces the 17 info-assessment review items across five groups (Key Takeaways, Assessment Scope, Prioritized Findings, Remediation Suggestions, Assessment Methodology), cross-cutting criteria, the risk-adjusted severity model, anti-patterns, and a pointer to rating_score_writing for a numeric score.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sections | array | no | Narrow to specific report sections; 'all' includes every section. |
| focus | array | no | Focus areas: completeness, clarity, tone, structure, severity, remediation, strengths, anti_patterns, or all. |
Get Lenny Zeltser's Security Assessment one-page executive brief template. Standalone variant of assessment_get_template for callers that only want the brief without the long-form report. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's Security Assessment cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of assessment_load_context. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for local analysis.
No parameter schema on file.
Get Lenny Zeltser's Security Assessment frameworks (primary frameworks the brief structurally derives from) plus optional sibling frames (adjacent frameworks that aren't the structural backbone). Pass include_siblings: false to skip sibling blocks. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_siblings | boolean | no | Include the siblingFrames block (adjacent frameworks with whyOmitted notes) and the siblingArtifacts block (related templates) in the response. Default: true. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Website Search or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_zeltser | no tags | |
| get_article | no tags | |
| get_index_info | no tags | |
| get_capabilities | no tags | |
| get_security_writing_guidelines | no tags | |
| ir_get_template | no tags | |
| ir_get_guidelines | no tags | |
| ir_load_context | no tags | |
| ir_review_report | no tags | |
| product_get_template | no tags | |
| product_get_guidelines | no tags | |
| product_load_context | no tags | |
| product_review_plan | no tags | |
| product_compare_context | no tags | |
| rating_get_sheet | no tags | |
| rating_score_writing | no tags | |
| rating_load_context | no tags | |
| aidefense_load_context | no tags | |
| aidefense_get_matrix | no tags | |
| aidefense_get_framework_alignment | no tags | |
| aidefense_evaluate_program | no tags | |
| aidefense_cross_map | no tags | |
| aidefense_locate_concept | no tags | |
| ir_get_brief_template | no tags | |
| ir_get_cross_server_routes | no tags | |
| ir_get_frameworks | no tags | |
| cti_get_template | no tags | |
| cti_get_guidelines | no tags | |
| cti_load_context | no tags | |
| cti_review_report | no tags | |
| cti_get_brief_template | no tags | |
| cti_get_cross_server_routes | no tags | |
| cti_get_frameworks | no tags | |
| malware_get_template | no tags | |
| malware_get_guidelines | no tags | |
| malware_load_context | no tags | |
| malware_review_report | no tags | |
| malware_get_cross_server_routes | no tags | |
| malware_get_frameworks | no tags | |
| vuln_get_template | no tags | |
| vuln_get_guidelines | no tags | |
| vuln_load_context | no tags | |
| vuln_review_brief | no tags | |
| vuln_get_brief_template | no tags | |
| vuln_get_cross_server_routes | no tags | |
| vuln_get_frameworks | no tags | |
| assessment_get_template | no tags | |
| assessment_get_guidelines | no tags | |
| assessment_load_context | no tags | |
| assessment_review_report | no tags | |
| assessment_get_brief_template | no tags | |
| assessment_get_cross_server_routes | no tags | |
| assessment_get_frameworks | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 8.1.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Website Search can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.