Kanibal Tools
PYPI · KANIBAL-TOOLS-MCP
Local read-only tools: French telemarketing consent, GDPR offshore checklist, cost per kept meeting
Available components
Last scanned (1 day ago)
Scores higher than 87% of PyPI servers
Category CRM and Sales
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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to kanibal-studio/kanibal-tools-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 793 tokens (~198/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 Management37
- Stability observed for 11 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
- 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 +3
- Schema quality: 127 → 198 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- Package version: 0.1.0 → 0.1.1 functional
- 24 Oct 26 61
First indexed and scored.
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 4 Nov 2026 · Analysed pypi/kanibal-tools-mcp@0.1.1
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 | kanibal-studio/kanibal-tools-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/kanibal-studio/kanibal-tools-mcp/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3457546440 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:dccb16525994f65a2a2510da23fa828950fdefa5631548e4329d4fc7c06189a9 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| 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 →
check_telemarketing_consent ~221
France only: is a consent to telephone canvassing still valid under décret 2026-662? Returns "valide", "expire" (older than the ceiling), "revoque" (any sign of revocation wins) or "preuve_manquante" (no readable collection date, or one in the future), with the expiry date and proof-retention date. Fail-closed. Use it for French telemarketing consent only; for transfers of customer-service data outside the EU use gdpr_offshore_gap_report. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| collected_at | string | yes | When the consent was collected, ISO 8601; a date without time zone is read as UTC. |
| max_age_days | – | – | Stricter internal ceiling in days; values above 365 or not positive fall back to the legal 365. |
| now | – | – | Reference instant, ISO 8601; defaults to the current UTC time. |
| revoked_at | – | – | Revocation date or any sign of revocation; omit if none. |
Structured output declared, but exposes no named fields.
No examples provided.
gdpr_offshore_gap_report ~182
GDPR gap report for customer-service processing outsourced outside the EU/EEA. Checks the transfer basis (adequacy or Art. 46 safeguards), the transfer impact assessment, the Art. 28 processor contract and its twelve clauses, Art. 32 security controls and breach notification. Only a JSON true satisfies a check; anything else is a gap or "to_verify". Use it for transfers outside the EU; for French telemarketing consent use check_telemarketing_consent. Not legal advice and not a certification: a report without blocking gap is not a finding of compliance.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Your set-up, as a JSON object. Every key is optional and a missing key is reported as to_verify; unknown keys are ignored with a warning. |
| lang | string | – | Language of the report text. |
Structured output declared, but exposes no named fields.
No examples provided.
rank_lead_sources_by_kept_meeting ~214
Rank B2B lead sources on cost per kept qualified meeting instead of cost per lead. Returns, per source and period, total cost, cost per lead, show rate, cost per kept meeting, cost per qualified kept meeting, and cost per deal and margin minus cost when provided. Invalid rows are reported as a tool error naming each row. Use it to compare acquisition channels; it does not check consent or GDPR. A low cost per meeting does not prove profitability.
| Name | Type | Req | Description |
|---|---|---|---|
| csv_text | string | yes | CSV content with a header row. Required: source, meetings_qualified_kept and at least one cost column (cost_media, cost_data, cost_tools, cost_human_time, cost_other). Optional: period, leads, meetin… |
| min_meetings | integer | – | Results under this many qualified kept meetings are flagged as a small sample, never hidden. |
Structured output declared, but exposes no named fields.
No examples provided.
select_least_cost_capable_model ~128
Pick, from a supplied catalogue, the model with the lowest declared cost rank among those that have every required capability and are available and authorised. Returns status "selected" with the comparison basis, "needs_information" naming the missing or non-comparable evidence, or "no_candidate_in_catalogue", plus exclusions. Use it to choose between AI models from facts you supply; it is unrelated to lead sources. Nothing is called, switched or launched; savings are not guaranteed.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogue | object | yes | Required capabilities and candidate models with their declared cost evidence. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Kanibal Tools MCP server?
Kanibal Tools runs locally as a PyPI package, launched with uvx kanibal-tools-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 · kanibal-tools-mcp
claude mcp add kanibal-studio-kanibal-tools-mcp -- uvx kanibal-tools-mcp
What is the Kanibal Tools MCP server?
Kanibal Tools is an MCP server listed in the public MCP registry as io.github.kanibal-studio/kanibal-tools-mcp. Local read-only tools: French telemarketing consent, GDPR offshore checklist, cost per kept meeting. This page covers its PyPI package (kanibal-tools-mcp).
Is the Kanibal Tools MCP server safe to use?
Kanibal Tools scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Kanibal Tools MCP server expose?
Kanibal Tools exposes 4 tools: check_telemarketing_consent, rank_lead_sources_by_kept_meeting, gdpr_offshore_gap_report, select_least_cost_capable_model. Their descriptions and schemas cost roughly 745 tokens of context every time the server is loaded.
Is the Kanibal Tools MCP server still maintained?
Kanibal Tools is still listed as active in the MCP registry. We last reached this channel on 4 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 Kanibal Tools MCP server under?
Kanibal Tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.