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.

tokencast

PYPI · TOKENCAST

Pre-execution cost estimation for LLM agent workflows with calibration learning

Available components

0 this week 73 Trust /100

Last scanned (17 hours ago)

Scores higher than 66% of PyPI servers

Category AI and Machine Learning

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 Security50
  • Malware scan not yet available for this package.Unverified
  • 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
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency96
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to krulewis/tokencast). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 235 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 297 tokens (~59/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 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
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 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
What we tested

Checks we ran (15)

  • 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

Checks we could not complete (1)

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.

  • Malware scan in Supply Chain SecurityMalware scan not yet available 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 →

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 +1
    • Stability: 0.97 → pass security
  • 15 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 14 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 10 Nov 26 0
    • Security disclosure: unverified → fail ▼ 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 21 Nov 2026 · Analysed pypi/tokencast@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 krulewis/tokencast
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/krulewis/tokencast/.github/workflows/release.yml@refs/tags/v0.1.1
Rekor log index 1189869455
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:4c863ffba25b151d23d744010538901039c75387393f58640528e26dd48414bc

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 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~297 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
estimate_cost ~98

Estimate Anthropic API token costs for a development plan before execution

NameTypeReqDescription
avg_file_linesinteger|null––
complexitystringyes–
file_pathsarray––
filesintegeryes–
languagestring––
parallel_groupsarray––
project_typestring––
review_cyclesinteger––
sizestringyes–
stepsarray––

No output schema declared.

No examples provided.

get_calibration_status ~27

Get calibration health and accuracy metrics for cost estimates

NameTypeReqDescription
windowstring––

No output schema declared.

No examples provided.

get_cost_history ~34

Query historical cost estimation records and actuals

NameTypeReqDescription
include_outliersboolean––
windowstring––

No output schema declared.

No examples provided.

report_session ~51

Report actual session cost to improve future calibration

NameTypeReqDescription
actual_costnumberyes–
review_cycles_actualinteger––
step_actualsobject––
turn_countinteger––

No output schema declared.

No examples provided.

report_step_cost ~87

Record the cost of a completed pipeline step. Costs accumulate per step and are flushed when report_session is called.

NameTypeReqDescription
costnumber––
modelstring––
step_namestringyes–
tokens_cache_readinteger––
tokens_cache_writeinteger––
tokens_ininteger––
tokens_outinteger––

No output schema declared.

No examples provided.

Install

How do I install the tokencast MCP server?

tokencast runs locally as a PyPI package, launched with uvx tokencast. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · tokencast

# add to Claude Code
claude mcp add krulewis-tokencast -- uvx tokencast
Common questions

What is the tokencast MCP server?

tokencast is an MCP server listed in the public MCP registry as io.github.krulewis/tokencast. Pre-execution cost estimation for LLM agent workflows with calibration learning. This page covers its PyPI package (tokencast).

Is the tokencast MCP server safe to use?

tokencast scores 73 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 tokencast MCP server expose?

tokencast exposes 5 tools: estimate_cost, get_calibration_status, get_cost_history, report_session, report_step_cost. Their descriptions and schemas cost roughly 297 tokens of context every time the server is loaded.

Is the tokencast MCP server still maintained?

tokencast 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 tokencast MCP server under?

tokencast 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 tokencast MCP server?

VerifyMCP ran 15 checks on tokencast, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about tokencast: Malware scan. 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.