@timps-ai/timps-mcp

MCPcommunity
v2.0.3io.github.Sandeeprdy1729UnknownUpdated 1mo agonpmGitHub

Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.Sandeeprdy1729
LicenseUnknown
Version2.0.3
Sourcenpm+mcp-registry
npm@timps-ai/timps-mcp
GitHubTIMPSs/timps
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface—
Security scan✓ Cleanv2.0.3 · 1mo agoHow well does this scan work?
MODERATEqs@6.15.3qs: Denial of Service via Attacker Controlled isBuffer · transitiveMODERATEqs@6.15.3qs array-limit bypass via bracket-key comma parsing · transitive
EvalsNone
IndexedAug 20, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable1mo ago

The published package tarball could not be read at scan time (tarball exceeds 15MB cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-05 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · 1 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

114 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+102 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.