# io.github.CloudCorpRecords/filingclock (npm · @reneturcios/filingclock)

US filing-deadline radar: small-biz and foreign-LLC obligations, details and checklists.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/filingclock`: 72/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-filingclock/reneturcios-filingclock.md), [page](https://verifymcp.io/servers/cloudcorprecords-filingclock/reneturcios-filingclock)
- oci · `ghcr.io/cloudcorprecords/filingclock`: 43/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-filingclock/ghcr-io-cloudcorprecords-filingclock.md), [page](https://verifymcp.io/servers/cloudcorprecords-filingclock/ghcr-io-cloudcorprecords-filingclock)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/filingclock`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 441 tokens (~147/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/filingclock MCP server?

io.github.CloudCorpRecords/filingclock runs locally as an npm package, launched with npx -y @reneturcios/filingclock mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-filingclock -- npx -y @reneturcios/filingclock mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-filingclock": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/filingclock",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-filingclock": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/filingclock",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-filingclock -- npx -y @reneturcios/filingclock mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-filingclock": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/filingclock",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-filingclock --command npx --arg -y --arg @reneturcios/filingclock --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-filingclock:
    command: "npx"
    args: ["-y", "@reneturcios/filingclock", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-filingclock": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/filingclock",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-filingclock -t stdio -c npx -a -y @reneturcios/filingclock mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-filingclock": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/filingclock",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 72, +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.

### 2026-11-18 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 70)

First indexed and scored.

## MCP tools (3)

### `list_obligations` (~175 tokens)

List recurring US compliance / tax-filing obligations that commonly blindside small businesses and foreign-owned US LLCs (FinCEN BOI, IRS Form 5472, Delaware/WY/NV/CA franchise tax & annual reports, 1099 deadlines, etc.). Each item cites its official IRS/FinCEN/state source with the date it was last verified. INFORMATIONAL ONLY — not legal or tax advice. Optionally filter by entity type and/or 2-letter state.

Input parameters:

- `entityType` (string): Filter to obligations that can apply to this entity type.
- `foreignOwned` (boolean): Include foreign-owned-only obligations (e.g. Form 5472).
- `state` (string): 2-letter US state (e.g. 'DE'). Filters state-specific obligations + always-included federal ones.

### `get_obligation` (~97 tokens)

Return full detail for a single obligation by id: what it is, who must file, the deadline, the penalty for missing it, and a link to the OFFICIAL government source with a dated 'verified as of'. INFORMATIONAL ONLY — not legal or tax advice.

Input parameters:

- `id` (string, required): Obligation id, e.g. 'fincen-boi', 'irs-5472', 'de-franchise-llc'.

### `build_checklist` (~169 tokens)

Build a personalized list of likely recurring compliance obligations and their NEXT deadline dates from an entity profile (entity type + state + formation date + a few flags). Pure date arithmetic over officially-cited rules — NOT individualized legal or tax advice. Always verify against the cited sources and a licensed professional.

Input parameters:

- `entityType` (string, required)
- `foreignOwned` (boolean): True if owned (>=25% or wholly) by a non-US person.
- `formationDate` (string): Entity formation date YYYY-MM-DD (drives anniversary-based deadlines).
- `hasEmployees` (boolean)
- `paysContractors` (boolean): True if you pay $600+ to US contractors (1099 obligations).
- `state` (string, required): 2-letter formation/registration state, e.g. 'DE'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-filingclock/reneturcios-filingclock#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 70

## Common questions

### What is the io.github.CloudCorpRecords/filingclock MCP server?

io.github.CloudCorpRecords/filingclock is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/filingclock. US filing-deadline radar: small-biz and foreign-LLC obligations, details and checklists. This page covers its npm package (@reneturcios/filingclock).

### Is the io.github.CloudCorpRecords/filingclock MCP server safe to use?

io.github.CloudCorpRecords/filingclock scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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.CloudCorpRecords/filingclock MCP server expose?

io.github.CloudCorpRecords/filingclock exposes 3 tools: list_obligations, get_obligation, build_checklist. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/filingclock MCP server still maintained?

io.github.CloudCorpRecords/filingclock 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 io.github.CloudCorpRecords/filingclock MCP server under?

io.github.CloudCorpRecords/filingclock 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.CloudCorpRecords/filingclock MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/filingclock, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/filingclock
- Socket report: https://socket.dev/npm/package/@reneturcios/filingclock
- Repository: https://github.com/CloudCorpRecords/filingclock
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-filingclock/reneturcios-filingclock.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-filingclock/reneturcios-filingclock/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-filingclock/reneturcios-filingclock.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-filingclock/reneturcios-filingclock
