Siftdog
PYPI · SIFTDOG
Self-hosted, Tavily-compatible web search, extract, crawl and map tools for AI agents.
Available components
Last scanned (14 hours ago)
Scores higher than 96% of PyPI servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 3 of 53 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to khsarvar/siftdog). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 53 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 637 tokens (~159/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 20 Nov 26 0
- Stability: pass → 0.97 functional
- 17 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/siftdog@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | khsarvar/siftdog |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/khsarvar/siftdog/.github/workflows/release.yml@refs/tags/v0.3.0 |
| Rekor log index | 2982850865 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:09638ea8d8bdc9281df9e1c53be0345d8b7ce505d9b644ea0029262954599f1f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 53 packages
| Packages resolved | 53 |
|---|---|
| Stale | 2 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
siftdog_crawl ~169
Crawl a website from a starting URL and return the content of the pages found. Use this to read many pages of one site. For large sites, call siftdog_map first and narrow the crawl with select_paths.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_external | boolean | – | Follow links to other domains. |
| exclude_paths | – | – | Regexes matched against URL paths, e.g. ['/docs/.*']. |
| limit | integer | – | Maximum pages to return. |
| max_chars | integer | – | Maximum characters of content to return per page. |
| max_depth | integer | – | How many links deep to follow from the start. |
| select_paths | – | – | Regexes matched against URL paths, e.g. ['/docs/.*']. |
| url | string | yes | The page to start crawling from. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
siftdog_extract ~84
Fetch web pages and return their main content as clean markdown or text. Use this when you already have the URLs, for example from siftdog_search results.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format of page content. |
| max_chars | integer | – | Maximum characters of content to return per page. |
| urls | array | yes | 1 to 20 page URLs. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
siftdog_map ~121
List the URLs of a website without fetching their content. Use this to see how a site is organised before extracting or crawling specific pages.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_paths | – | – | Regexes matched against URL paths, e.g. ['/docs/.*']. |
| limit | integer | – | Maximum URLs to return. |
| max_depth | integer | – | How many links deep to follow from the start. |
| select_paths | – | – | Regexes matched against URL paths, e.g. ['/docs/.*']. |
| url | string | yes | The site or page to map from. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
siftdog_search ~177
Search the web and return ranked results with titles, URLs and relevant content. Use this to find sources for a question or to discover pages about a topic. If you already know the URLs, use siftdog_extract instead.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_domains | – | – | Never return results from these domains. |
| include_domains | – | – | Only return results from these domains. |
| max_chars | integer | – | Maximum characters of content to return per page. |
| max_results | integer | – | Number of results. |
| query | string | yes | The search query. |
| search_depth | string | – | 'basic' returns search snippets; 'advanced' reads each page and returns its most relevant passages (slower, better content). |
| time_range | – | – | Only return results from this recent period. |
| topic | string | – | Use 'news' for current events. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Siftdog MCP server?
Siftdog runs locally as a PyPI package, launched with uvx siftdog mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · siftdog
claude mcp add khsarvar-siftdog -- uvx siftdog mcp
What is the Siftdog MCP server?
Siftdog is an MCP server listed in the public MCP registry as io.github.khsarvar/siftdog. Self-hosted, Tavily-compatible web search, extract, crawl and map tools for AI agents. This page covers its PyPI package (siftdog).
Is the Siftdog MCP server safe to use?
Siftdog scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Siftdog MCP server expose?
Siftdog exposes 4 tools: siftdog_search, siftdog_extract, siftdog_crawl, siftdog_map. Their descriptions and schemas cost roughly 551 tokens of context every time the server is loaded.
Is the Siftdog MCP server still maintained?
Siftdog is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Siftdog MCP server under?
Siftdog declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Siftdog MCP server?
VerifyMCP ran 16 checks on Siftdog, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.