io.github.RyanKramer/summitflow-mcp
PYPI · SUMMITFLOW-MCP
Grant management for AI agents: deadlines, business-day math, budgets, in-kind value. No API key.
Available components
Last scanned (3 hours ago)
Scores higher than 61% of PyPI servers
Category Finance and Payments
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
- 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
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 94 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 672 tokens (~74/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 (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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 (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 →
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.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ 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 5 Nov 2026 · Analysed pypi/summitflow-mcp@0.1.0
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 →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 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 →
add_business_days Add Business Days ~48
Add (or subtract, with a negative number) business days to a date, skipping weekends and US federal holidays.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | yes | – |
| start_date | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
business_days_between Business Days Between ~50
Count business days between two dates, skipping weekends and US federal holidays. Dates are ISO format (YYYY-MM-DD).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | – |
| start_date | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
federal_holidays Federal Holidays ~50
List US federal holidays for a year, with observed dates. Observed dates matter more than actual ones for deadlines: a holiday on a Saturday closes offices the Friday before.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
grant_budget Grant Budget ~176
Build a grant budget with fringe and indirect calculated on the correct base. indirect_base: 'mtdc' (Modified Total Direct Cost) or 'tdc' (Total Direct Cost). MTDC is the common federal base and it EXCLUDES equipment and the portion of each subaward/contract above the first $25,000. Applying your rate to total direct costs instead is the single most common budget error, and it inflates the ask in a way reviewers notice.
| Name | Type | Req | Description |
|---|---|---|---|
| contractual | number | – | – |
| equipment | number | – | – |
| fringe_rate_pct | number | – | – |
| indirect_base | string | – | – |
| indirect_rate_pct | number | – | – |
| other_direct | number | – | – |
| personnel | number | – | – |
| supplies | number | – | – |
| travel | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
grant_deadline_plan Grant Deadline Plan ~100
Work backward from a funder deadline to the dates that actually matter. A deadline is not a plan. This returns when to start drafting, when the internal review copy is due, and when the packet must be complete, using realistic lead times with weekends and federal holidays handled. application_type: loi | proposal_new | proposal_renewal | federal | report
| Name | Type | Req | Description |
|---|---|---|---|
| application_type | string | – | – |
| deadline | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
grant_lead_times Grant Lead Times ~25
The lead times behind grant_deadline_plan, with the reasoning for each.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
in_kind_value In Kind Value ~44
Total donated goods and services. Each item needs 'description' and 'fair_market_value'; optional 'quantity' (default 1).
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
summitflow_resources Summitflow Resources ~20
Free grant templates, guides and calculators on the web.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
volunteer_time_value Volunteer Time Value ~84
Value volunteer time for match requirements or an annual report. Defaults to the published national rate. Skilled volunteers doing professional work (legal, accounting, medical) should be valued at the rate for that work instead, which most funders accept if you document it.
| Name | Type | Req | Description |
|---|---|---|---|
| hourly_rate | number | – | – |
| hours | number | yes | – |
| volunteers | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.RyanKramer/summitflow-mcp server?
io.github.RyanKramer/summitflow-mcp runs locally as a PyPI package, launched with uvx summitflow-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 · summitflow-mcp
claude mcp add ryankramer-summitflow-mcp -- uvx summitflow-mcp
What is the io.github.RyanKramer/summitflow-mcp server?
io.github.RyanKramer/summitflow-mcp is listed in the public MCP registry as io.github.RyanKramer/summitflow-mcp. Grant management for AI agents: deadlines, business-day math, budgets, in-kind value. No API key. This page covers its PyPI package (summitflow-mcp).
Is the io.github.RyanKramer/summitflow-mcp server safe to use?
io.github.RyanKramer/summitflow-mcp scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 io.github.RyanKramer/summitflow-mcp server expose?
io.github.RyanKramer/summitflow-mcp exposes 9 tools: federal_holidays, business_days_between, add_business_days, grant_deadline_plan, grant_budget, and 4 more. Their descriptions and schemas cost roughly 597 tokens of context every time the server is loaded.
Is the io.github.RyanKramer/summitflow-mcp server still maintained?
io.github.RyanKramer/summitflow-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.RyanKramer/summitflow-mcp server under?
io.github.RyanKramer/summitflow-mcp 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 io.github.RyanKramer/summitflow-mcp server?
VerifyMCP ran 15 checks on io.github.RyanKramer/summitflow-mcp, 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 io.github.RyanKramer/summitflow-mcp: 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.