About Recon Knowledge
Recon Knowledge is an MCP server for searching Recon's public documentation, book, and newsletter on fuzzing, invariant testing, and related topics. It offers source-specific and cross-source search, plus tools for retrieving individual articles and concepts.
Key features
- 01Search documentation, book, and newsletter
- 02Look up glossary terms and concepts
- 03Retrieve posts, chapters, and comparisons
- 04List developer tools and book chapters
- 05Refresh cached public content
Use cases
- 01Find Recon material about fuzzing
- 02Look up invariant-testing concepts
- 03Retrieve a specific blog or newsletter post
MCP support
The MCP server exposes search, listing, retrieval, and cache-refresh tools to MCP clients. It fetches public content from Recon's documentation site, book, and Substack newsletter.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
14Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| query | string | Yes | The search query to find glossary terms |
Details
From the project README@recon-fuzz-mcp/knowledge
MCP server that makes Recon documentation searchable by AI tools. Fetches and parses getrecon.xyz/llms-full.txt into structured, queryable content.
Tools
Site tools (getrecon.xyz)
| Tool | Input | Returns |
|---|---|---|
search_glossary | query: string | Top 5 matching glossary terms with definitions |
get_blog_post | slug: string | Full post content + metadata + URL |
get_comparison | slug: string | Both entities, strengths, conclusion, FAQs |
search_site | query: string | Top 10 matches across site content |
list_tools | (none) | Developer tools with descriptions + URLs |
Book tools (book.getrecon.xyz)
| Tool | Input | Returns |
|---|---|---|
get_book_chapter | slug: string | Full chapter content, category, URL |
get_book_concept | slug: string | Technical concept explanation |
search_book | query: string | Top 10 matches across book content |
list_book_chapters | (none) | All chapters grouped by category |
Substack tools (getrecon.substack.com)
| Tool | Input | Returns |
|---|---|---|
get_substack_post | slug: string | Full newsletter post content |
search_substack | query: string | Top 10 matches across Substack posts |
list_substack_posts | (none) | All posts sorted by date |
Cross-source
| Tool | Input | Returns |
|---|---|---|
search_all | query: string | Top 15 matches across all 3 sources |
refresh_cache | (none) | Re-fetch all sources (rate limited to 1/min) |
Installation
Claude Code
claude mcp add recon-knowledge -- npx @recon-fuzz-mcp/knowledge
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"recon-knowledge": {
"command": "npx",
"args": ["@recon-fuzz-mcp/knowledge"]
}
}
}
Cursor
Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"recon-knowledge": {
"command": "npx",
"args": ["@recon-fuzz-mcp/knowledge"]
}
}
}
No API key needed. The server fetches public documentation only.
Local development
git clone https://github.com/Recon-Fuzz/recon-mcp-knowledge.git
cd recon-mcp-knowledge
npm install
npm run build
Test it works
# List tools
echo '{"jsonrpc":"2.0","method":"tools/list","id":1}' | node dist/index.js
# Search for chimera content
echo '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"search_site","arguments":{"query":"chimera"}},"id":2}' | node dist/index.js
Architecture
- Fetches
llms-full.txtonce on startup, caches in memory - Cache refreshes every 24h automatically or on manual
refresh_cache - Parser splits by
---dividers, extracts blog posts, glossary, comparisons, tools - Search uses case-insensitive term matching with word-boundary scoring
- No database, no external search library, no filesystem writes
Privacy
This server is read-only. It fetches from a single hardcoded public URL (getrecon.xyz/llms-full.txt). No user queries, tool arguments, or any data is sent to Recon or any third party.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.