Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OSINT Toolbox

PYPI · OSINT-TOOLBOX-MCP · 2 COMPONENTS

Run Sherlock, Maigret, Holehe, GHunt, theHarvester, SpiderFoot and more OSINT tools locally

+6 this week 93 Trust /100

Last scanned (21 hours ago)

Scores higher than 96% of PyPI servers

Category Search and Retrieval

Trust breakdown (7 categories)

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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to renkagod/osint-toolbox-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 22 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 472 tokens (~94/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Changelog

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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +4

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 63. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Oct 26 −11
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.27 ▲ functional
  • 30 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Sept 26 +10
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 16 Oct 2026 · Analysed pypi/osint-toolbox-mcp@1.1.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 renkagod/osint-toolbox-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/renkagod/osint-toolbox-mcp/.github/workflows/release.yml@refs/tags/v1.1.0
Rekor log index 2926965743
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:f520c642ece515fd2d411a2719a8eb11a8e46c90d7435d4afaf38269b7bfe18d

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~419 tokens

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 →

Tool Tokens
crtsh_certificate_search ~71

Host names (often unlisted subdomains) and email addresses found in TLS certificates issued for a domain, from the crt.sh certificate transparency log search.

NameTypeReqDescription
domainstringyesDomain name, e.g. example.com
include_expiredboolean–Include expired certificates (default: true)

No output schema declared.

No examples provided.

dns_lookup ~87

DNS records of a name (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA by default), or the reverse name of an IP address. Asks public DNS-over-HTTPS resolvers.

NameTypeReqDescription
namestringyesDomain name, or an IP address for a reverse (PTR) lookup
typesarray–Record types to fetch

No output schema declared.

No examples provided.

osint_toolbox_status ~42

Which OSINT tools this server can run on this machine, and how to install the missing ones. Call it when a tool you need is not available.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wayback_snapshots ~144

Archived snapshots of a URL, a site or a domain in the Internet Archive's Wayback Machine, newest first, with links to view each one.

NameTypeReqDescription
fromstring–Earliest date, e.g. 2019 or 20190131
limitinteger–Number of snapshots (default: 50)
matchstring–exact URL (default), every URL under it (prefix), the whole host, or the domain with subdomains
tostring–Latest date, e.g. 2021 or 20211231
urlstringyesURL or domain, e.g. example.com/about

No output schema declared.

No examples provided.

whois_lookup ~75

Registration data for a domain, IP address, network or AS number: registrar, dates, name servers, holder and contacts where public. Uses RDAP, or WHOIS for registries without RDAP.

NameTypeReqDescription
querystringyesDomain (example.com), IP address, CIDR network or AS number (AS13335)

No output schema declared.

No examples provided.

Install

How do I install the OSINT Toolbox MCP server?

OSINT Toolbox runs locally as a PyPI package, launched with uvx osint-toolbox-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 · osint-toolbox-mcp

# add to Claude Code
claude mcp add renkagod-osint-toolbox-mcp -- uvx osint-toolbox-mcp
Common questions

What is the OSINT Toolbox MCP server?

OSINT Toolbox is an MCP server listed in the public MCP registry as io.github.renkagod/osint-toolbox-mcp. Run Sherlock, Maigret, Holehe, GHunt, theHarvester, SpiderFoot and more OSINT tools locally. This page covers its PyPI package (osint-toolbox-mcp).

Is the OSINT Toolbox MCP server safe to use?

OSINT Toolbox scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 OSINT Toolbox MCP server expose?

OSINT Toolbox exposes 5 tools: whois_lookup, dns_lookup, crtsh_certificate_search, wayback_snapshots, osint_toolbox_status. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.

Is the OSINT Toolbox MCP server still maintained?

OSINT Toolbox is still listed as active in the MCP registry. We last reached this channel on 16 October 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 OSINT Toolbox MCP server under?

OSINT Toolbox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.