fittok
PYPI · FITTOK
Retrieve only the relevant code for a codebase question, within a token budget.
Available components
Last scanned (9 hours ago)
Scores higher than 53% of PyPI servers
Category Code Search and Documentation
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 Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: our dependency resolver did not run for this package.Unverified
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health could not be checked: our dependency resolver did not run for this package.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 88 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1192 tokens (~59/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (10% 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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
Checks we ran (14)
- Malware scan
- Install scripts
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: our dependency resolver did not run for this package.
- Dependency health in Supply Chain SecurityDependency health could not be checked: our dependency resolver did not run for this package.
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 −5
- Known CVEs: fail → unverified ▼ security
- Dependency health: 0.94 → unverified ▼ functional
- 20 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +40
- Injection markers: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.00 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 10 functional
- First check of Schema quality: pass functional
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/fittok@0.11.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 →
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 →
add_pii_pattern_tool ~34
Add or override a PII detection pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| regex | string | yes | – |
No output schema declared.
No examples provided.
cache_stats_tool ~18
Return cache hit/miss statistics and size.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
clear_cache_tool ~33
Clear the cache. Scope: 'all' | 'graph' | 'query'.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | – |
No output schema declared.
No examples provided.
diff_graph_tool ~36
Compare two knowledge graphs and return structural differences.
| Name | Type | Req | Description |
|---|---|---|---|
| graph_path_a | string | yes | – |
| graph_path_b | string | yes | – |
No output schema declared.
No examples provided.
get_graph_stats_tool ~26
Return metadata and stats for a graph.
| Name | Type | Req | Description |
|---|---|---|---|
| graph_path | string | yes | – |
No output schema declared.
No examples provided.
launch_ui_tool ~33
Launch the web visualization UI for graph exploration.
| Name | Type | Req | Description |
|---|---|---|---|
| open_browser | boolean | – | – |
| port | integer | – | – |
No output schema declared.
No examples provided.
list_pii_patterns_tool ~19
List all registered PII detection patterns.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
optimize_context_batch ~51
One parse, many queries. Builds graph once, runs slurp+select per query.
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | yes | – |
| queries | array | yes | – |
| token_budget | integer | – | – |
No output schema declared.
No examples provided.
optimize_context_stream ~68
Streaming pipeline: yields stage-by-stage progress events. Returns a list of event dicts in order: [{"stage": "parsing", "status": "started"}, ...]
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | yes | – |
| query | string | yes | – |
| token_budget | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
optimize_context_structured ~70
Full pipeline with structured JSON output mode. Args: output_format: "markdown" (default) or "json" for structured output.
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | yes | – |
| output_format | string | – | – |
| query | string | yes | – |
| token_budget | integer | – | – |
No output schema declared.
No examples provided.
optimize_context_tool ~187
Return the most relevant REAL source code for a question — completely. Use this FIRST for any "how does X work / where is Y" question about the codebase, and prefer it over reading files or grepping. Returns ALL relevant functions/classes in full (every line numbered with its real source line), plus a flow trace and referenced dependencies — so answer directly from the output and cite file:line from the numbers shown. Do NOT re-read (Read/grep/`nl`) files that appear in the output: their bodies are already complete here. token_budget defaults to 0 = return everything relevant (recommended). Set a value ONLY to cap output size. (Server-wide cap: FITTOK_MAX_BUDGET env var.)
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | yes | – |
| query | string | yes | – |
| token_budget | integer | – | – |
No output schema declared.
No examples provided.
parse_codebase_stream_tool ~38
Stream parse progress. Parses in batches, returns progress events.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_size | integer | – | – |
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
parse_codebase_tool ~29
Parse all code files in a directory into a knowledge graph.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
query_graph_tool ~94
Query a knowledge graph for the most relevant subgraph within a token budget. Prefer ``codebase_path`` (a directory) — it uses the live, incrementally updated graph. ``graph_path`` (a saved graph.json) is kept as a fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | – | – |
| graph_path | string | – | – |
| query | string | – | – |
| token_budget | integer | – | – |
No output schema declared.
No examples provided.
reset_graph_tool ~30
Force a full re-parse of the codebase, ignoring cache.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
scrub_file_tool ~30
Scrub PII from a file.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | – | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
scrub_text_tool ~40
Scrub PII (secrets, emails, API keys, etc.) from text.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_patterns | – | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
show_graph_tool ~151
Open an INTERACTIVE BROWSER visualization of the codebase knowledge graph. ⚠️ Call this ONLY when the user EXPLICITLY asks to SEE / VISUALIZE / SHOW / DRAW the graph — e.g. "show me the knowledge graph", "visualize this codebase", "draw the call graph". Do NOT call it for ordinary codebase questions; use `optimize_context` for those. This opens a browser tab on the user's machine (the server runs locally) and returns a short confirmation — it does NOT return source code to answer from. Optional `query` highlights the most relevant nodes.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| query | string | – | – |
No output schema declared.
No examples provided.
watch_start_tool ~26
Start watching a codebase for incremental graph updates.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
watch_stop_tool ~22
Stop watching a codebase.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
How do I install the fittok MCP server?
fittok runs locally as a PyPI package, launched with uvx fittok. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · fittok
claude mcp add likhithreddy-fittok -- uvx fittok
What is the fittok MCP server?
fittok is an MCP server listed in the public MCP registry as io.github.likhithreddy/fittok. Retrieve only the relevant code for a codebase question, within a token budget. This page covers its PyPI package (fittok).
Is the fittok MCP server safe to use?
fittok scores 58 out of 100 on VerifyMCP. 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 fittok MCP server expose?
fittok exposes 20 tools: parse_codebase_tool, query_graph_tool, optimize_context_tool, optimize_context_stream, optimize_context_batch, and 15 more. Their descriptions and schemas cost roughly 1,035 tokens of context every time the server is loaded.
Is the fittok MCP server still maintained?
fittok 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 fittok MCP server under?
fittok 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 fittok MCP server?
VerifyMCP ran 14 checks on fittok, covering Malware scan, Install scripts, Source repository, Provenance and 10 more. 2 items could not be completed, a gap on our side rather than a finding about fittok: Known CVEs and Dependency health. 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.