Quiet File Team MCP
PYPI · QUIET-FILE-TEAM-MCP
Six offline guidance tools for a local file-first agent team.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of PyPI servers
Category Developer Tools
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pandadad0214/quiet-file-team-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 931 tokens (~155/item across 6 items; 6 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 Management33
- Stability observed for 10 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 (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.
- 21 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 18 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 −15
- Malware scan: pass → unverified ▼ security
- 16 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.
- 14 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.2 → 0.1.3 functional
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.1 → 0.1.2 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/quiet-file-team-mcp@0.1.3
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 | pandadad0214/quiet-file-team-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pandadad0214/quiet-file-team-mcp/.github/workflows/release.yml@refs/tags/v0.1.3 |
| Rekor log index | 3862133895 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8dcfac55a574fc1552fcd1fee58842706f2f0efc7d2782b65be3da61efe5c51c |
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 →
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 →
draft_owner_batch ~161
Structure supplied owner-decision questions into a bounded review batch; unlike draft_workflow, organize decisions rather than simulate job execution. Use before an authorized owner review. This tool only drafts and deduplicates questions for local review; it does not contact anyone, infer approval, or invent answers. Free offline text processing, no network or paid API and unbenchmarked short latency. Identical explicit questions merge task ids; missing questions or cap overflow preserve unresolved references. Returns questions, unresolved ids and warnings; summaries alone do not establish a decision.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Generic unresolved task summaries with original ids and optional explicit questions. |
| max_questions | integer | – | Maximum deduplicated questions to return; overflow ids are marked unresolved. |
| Name | Type | Req | Description |
|---|---|---|---|
| questions | array | yes | – |
| unresolved_task_ids | array | yes | – |
| warnings | array | yes | – |
No examples provided.
draft_workflow ~132
Draft a fictional lead/builder/helper task, board and pair exercise; unlike explain_method, return practice steps and acceptance checks. Use only in an empty disposable default-roster folder, not as production history or an executable fixture. Free offline template computation with no network or paid API, bounded work and unbenchmarked latency. Objective is treated as quoted prose, never executed; sensitive-shaped text is rejected heuristically. Returns scenario, ordered steps, acceptance checks and warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| objective | string | – | Short fictional, non-sensitive practice objective; no account data, credentials or real history. |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptance | array | yes | – |
| scenario | string | yes | – |
| steps | array | yes | – |
| warnings | array | yes | – |
No examples provided.
explain_method ~121
Explain the file-first quiet-bus method and trust limits; unlike draft_workflow, return concepts rather than a practice sequence. Use before adoption or to clarify idle/durable behavior, not to install software or create schedules. Free offline text computation; no paid APIs or network calls, small bounded work with unbenchmarked latency. Topic selects emphasis, not an integration. Returns principles, prerequisites, limits and the free-core link.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Choose conceptual focus: overview, trust boundaries, quiet idle behavior, or durable tasks. |
| Name | Type | Req | Description |
|---|---|---|---|
| free_core | string | – | – |
| limits | array | yes | – |
| prerequisites | array | yes | – |
| principles | array | yes | – |
No examples provided.
generate_early_exit ~171
Draft a quiet early-exit shell block for an existing routine; unlike generate_team_config, leave roster settings unchanged. Use while manually wiring a routine, not to schedule it, inspect files or prove the enclosing agent stops. Free offline text computation, no paid API or network calls; short bounded work, latency unbenchmarked. Role must belong to roster; team_dir is quoted as literal text and is never read. Match exactly NO WORK, not exit status. Returns block and enclosing-routine warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | yes | Participant id present in roster for this routine. |
| roster | array | yes | Configured roster including lead and the chosen role. |
| team_dir | string | yes | Absolute POSIX directory of the reviewed local core, not a file to inspect. |
| Name | Type | Req | Description |
|---|---|---|---|
| block | string | yes | – |
| warnings | array | yes | – |
No examples provided.
generate_team_config ~171
Draft reviewed team.conf defaults for a fresh local core; unlike generate_early_exit, produce roster settings rather than routine instructions. Use before manual installation, not for secrets, arbitrary shell fragments or modifying existing logs. Free offline text computation with no paid API and unbenchmarked short latency. Coordinator must be lead and occur in roster; environment overrides still win, and target zone support must be checked locally. Returns config text, normalized roster and warnings; writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| coordinator | string | – | Keep lead: the free core authorizes decided only for this label. |
| roster | array | yes | Unique simple lowercase participant ids; include lead. Each id is at most 24 characters. |
| zone | string | – | IANA time zone supported by the target machine; defaults to UTC. |
| Name | Type | Req | Description |
|---|---|---|---|
| config_text | string | yes | – |
| coordinator | string | yes | – |
| roster | array | yes | – |
| warnings | array | yes | – |
| zone | string | yes | – |
No examples provided.
validate_layout_manifest ~139
Compare a supplied file manifest with required free-core paths; unlike generate_team_config, report omissions rather than draft settings. Use to review a known path list, not to read a filesystem, validate contents or prove runtime safety. Free offline computation, no network or paid API; bounded list processing with unbenchmarked latency. Absolute paths, traversal and oversized lists fail rather than being silently normalized. Returns completeness, missing paths and limitations; extras do not prove installation.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | Caller-supplied relative file paths; no absolute paths, traversal, controls or backslashes. Each path at most 240 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | – |
| limitations | array | yes | – |
| missing | array | yes | – |
| present_required | array | yes | – |
No examples provided.
How do I install the Quiet File Team MCP server?
Quiet File Team MCP runs locally as a PyPI package, launched with uvx quiet-file-team-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 · quiet-file-team-mcp
claude mcp add pandadad0214-quiet-file-team-mcp -- uvx quiet-file-team-mcp
What is the Quiet File Team MCP server?
Quiet File Team MCP is listed in the public MCP registry as io.github.pandadad0214/quiet-file-team-mcp. Six offline guidance tools for a local file-first agent team. This page covers its PyPI package (quiet-file-team-mcp).
Is the Quiet File Team MCP server safe to use?
Quiet File Team MCP scores 69 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 Quiet File Team MCP server expose?
Quiet File Team MCP exposes 6 tools: explain_method, generate_team_config, generate_early_exit, validate_layout_manifest, draft_workflow, draft_owner_batch. Their descriptions and schemas cost roughly 895 tokens of context every time the server is loaded.
Is the Quiet File Team MCP server still maintained?
Quiet File Team MCP 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 Quiet File Team MCP server under?
Quiet File Team 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 Quiet File Team MCP server?
VerifyMCP ran 15 checks on Quiet File Team 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 Quiet File Team 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.