2.2.5npm · docfork · latest release
Observed 2026-08-15T19:28:14.285Z using mcpSecurity-inventory. Protocol 2025-06-18.
| Tool | Category | Risk |
|---|---|---|
fetch_docRetrieve full documentation content from a URL and return it as rendered markdown. Use this tool to get complete pages — including code examples, API signatures, and prose — from search_docs result URLs.
- Pass a URL directly from search_docs results to retrieve that section's full content.
- Trim the URL anchor or path to a parent directory to get a broader table of contents with section previews.
- Returns rendered markdown that preserves code blocks, headings, and document structure.
- Only works on Docfork-indexed documentation — use WebFetch for URLs not returned by search_docs.
- If search_docs returns sparse or no results, try fetch_doc on the library's root documentation URL (e.g. https://github.com/owner/repo/tree/main/docs) to browse available content.Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "URL from search_docs results. Keep the anchor for a specific section, or trim it for a broader page view."
}
},
"required": [
"url"
]
}Annotations{
"readOnlyHint": true
} | — | — |
search_docsSearch a library's indexed documentation and return relevant sections with titles, summaries, and URLs. Results are sourced from official, versioned documentation.
Usage:
- Be specific in your query. Include the feature, API, or concept you need. Good: "server-side rendering with App Router". Bad: "rendering".
- The library parameter accepts a simple name (e.g., react, nextjs) or exact owner/repo for precision (e.g., vercel/next.js, TanStack/query).
- When multiple library candidates appear, prefer exact name matches and official organizations over forks.
- After 2 searches without finding the relevant section, switch to fetch_doc on the best result URL or the library's documentation root rather than searching again.
- Use fetch_doc on result URLs to retrieve full documentation content.Input schema{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "The search query. Be specific and include relevant details. Good: 'How to set up server-side rendering in Next.js' or 'Zod schema validation for nested objects'. Bad: 'rendering' or 'validation'."
},
"library": {
"type": "string",
"description": "Library name or keyword (e.g., react, nextjs), or exact owner/repo for higher precision (e.g., vercel/next.js, TanStack/query). Prefer official organizations and upstream repositories when multiple candidates match."
},
"tokens": {
"description": "Result detail level. Omit for automatic sizing.",
"anyOf": [
{
"type": "string",
"const": "dynamic"
},
{
"type": "integer",
"minimum": 100,
"maximum": 10000
},
{
"type": "string"
}
]
}
},
"required": [
"query",
"library"
]
}Annotations{
"readOnlyHint": true
} | — | — |
Compared with initial baseline using full_baseline.
| Risk | Change | Subject |
|---|---|---|
| No material changes recorded. | ||
| Severity | Finding | Advisory |
|---|---|---|
| No confirmed vulnerability is published for this version. | ||
Artifact SHA-256: b41536931330831fcf58634f3b3c57f351e84c1a00c6105e4991b13dbaa7a0d1
Scanner: mcp-proof-engine 0.1.0.