io.github.Sandeeprdy1729/timps
NPM · @TIMPS-AI/TIMPS-MCP · SCANNED AUG 23
Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.
Available components
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 →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 46 of 160 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3645 tokens (~52/item across 69 items; 69 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.Sandeeprdy1729/timps MCP server?
io.github.Sandeeprdy1729/timps runs locally as an npm package, launched with npx -y @timps-ai/timps-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @timps-ai/timps-mcp
claude mcp add sandeeprdy1729-timps -- npx -y @timps-ai/timps-mcp
{
"mcpServers": {
"sandeeprdy1729-timps": {
"command": "npx",
"args": [
"-y",
"@timps-ai/timps-mcp"
]
}
}
} {
"servers": {
"sandeeprdy1729-timps": {
"command": "npx",
"args": [
"-y",
"@timps-ai/timps-mcp"
]
}
}
} codex mcp add sandeeprdy1729-timps -- npx -y @timps-ai/timps-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sandeeprdy1729-timps": {
"type": "local",
"command": [
"npx",
"-y",
"@timps-ai/timps-mcp"
],
"enabled": true
}
}
} openclaw mcp add sandeeprdy1729-timps --command npx --arg -y --arg @timps-ai/timps-mcp
mcp_servers:
sandeeprdy1729-timps:
command: "npx"
args: ["-y", "@timps-ai/timps-mcp"] {
"McpServers": {
"sandeeprdy1729-timps": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@timps-ai/timps-mcp"
]
}
}
} assistant mcp add sandeeprdy1729-timps -t stdio -c npx -a -y @timps-ai/timps-mcp
{
"mcpServers": {
"sandeeprdy1729-timps": {
"command": "npx",
"args": [
"-y",
"@timps-ai/timps-mcp"
]
}
}
} 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.
- 20 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Aug 26 53
First indexed and scored.
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 23 Aug 2026 · Analysed npm/@timps-ai/timps-mcp@2.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 160 packages
| Packages resolved | 160 |
|---|---|
| Stale | 46 |
| Tree resolution | Complete |
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.
timps_record_mention ~55
Record that a person was mentioned in some context. Builds the relationship profile that powers drift alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | What was said about them or in what context |
| name | string | yes | Person name |
No output schema declared.
No examples provided.
timps_record_pattern ~54
Store a reusable code pattern or convention for future recall.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | The code pattern or convention to store |
| tags | array | – | Tags like ["typescript", "react", "error-handling"] |
No output schema declared.
No examples provided.
timps_record_review_pattern ~45
Store something you consistently flag or look for during code reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | What you always check or flag in reviews |
| severity | string | – | – |
No output schema declared.
No examples provided.
timps_record_signal ~47
Log a behavioral signal for burnout tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| signal_type | string | yes | focus_hours | energy_level | enthusiasm_score | commits_per_day |
| value | number | yes | Signal value |
No output schema declared.
No examples provided.
timps_register_trigger ~77
Register a prospective trigger: when a specific phrase appears in context, surface a specific memory or action (Tool 23 / L17).
| Name | Type | Req | Description |
|---|---|---|---|
| memoryId | string | yes | Memory ID to associate |
| surface | string | yes | What to surface when trigger fires |
| when | string | yes | Trigger phrase to watch for (substring match) |
No output schema declared.
No examples provided.
timps_relationship_check ~53
Check relationship health and drift alerts. Use when user mentions a person. Returns drift alerts for contacts not mentioned in 90+ days.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_name | string | – | Person name — omit for all drift alerts |
No output schema declared.
No examples provided.
timps_resolve_conflict ~63
Check for conflicts/contradictions between two memories using Jaccard similarity + sentiment analysis (Tool 21 ConflictResolver).
| Name | Type | Req | Description |
|---|---|---|---|
| memoryA | string | yes | First memory content to compare |
| memoryB | string | yes | Second memory content to compare |
No output schema declared.
No examples provided.
timps_reveal_bias ~35
Analyze memory for over/under-representation bias across saved facts (Tool 24 / L18 BiasRevealer).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timps_simulate_decision ~67
Simulate future outcomes for a decision based on actual history. Uses Jaccard similarity to find similar past decisions and votes weighted by regret.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_months | number | – | Months ahead (default 12) |
| scenario | string | yes | Decision or situation to simulate |
No output schema declared.
No examples provided.
timps_skill_shadow ~58
Coach using your own observed workflow patterns. Reframes VelocityTracker advice as "how YOU do this work" rather than generic tips.
| Name | Type | Req | Description |
|---|---|---|---|
| situation | string | yes | The current situation or task (e.g. "writing a hard refactor") |
No output schema declared.
No examples provided.
timps_store_memory ~43
Store an important fact in TIMPs long-term memory.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Memory to store |
| importance | number | – | Importance 1-5 |
No output schema declared.
No examples provided.
timps_synapse_consolidate ~43
Run a metabolic consolidation cycle. Consolidates high-activation nodes, audits low-utility nodes, refreshes stale nodes, and decays inactive ones.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timps_synapse_graph ~48
Get the metabolic graph structure (nodes + edges) for visualization. Returns nodes with activation scores and layer information.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max nodes to return (default 30) |
No output schema declared.
No examples provided.
timps_synapse_ingest ~117
Ingest a signal into SynapseMetabolon spreading activation graph. Classifies into interaction/reasoning/audit layers with automatic entity linking and activation spread.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The signal or event to ingest |
| entity | string | – | Primary entity identifier |
| source_module | string | yes | Source: timps-code, timps-vscode, timps-mcp, reflection, etc. |
| tags | array | – | Entity tags: code, bug, tech-debt, api, burnout, relationship |
No output schema declared.
No examples provided.
timps_synapse_query ~89
Query SynapseMetabolon with spreading activation. Spreads from seed nodes through relational edges, runs metabolic cycle, and returns activated nodes with confidence scores.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max activated nodes to return (default 10) |
| query | string | yes | Metabolic graph query (e.g. "how do my coding sessions relate to burnout?", "show patterns around API decisions") |
No output schema declared.
No examples provided.
timps_synapse_stats ~32
Get SynapseMetabolon statistics: node counts, edge counts, layer breakdown, and average activation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timps_temporal_query ~99
Query memories that were valid at a specific point in time. Use for historical reconstruction ("what did I believe on March 15?"), longitudinal tracking, or context-anchored retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| at_timestamp | number | yes | Unix epoch seconds for the point-in-time query. Use Date.now()/1000 for "now". |
| domain | string | – | Filter by memory domain |
| limit | number | – | Max results (default 10) |
No output schema declared.
No examples provided.
timps_verify_engram_chain ~36
Verify the integrity of the immutable memory audit trail (L10 EngramLog). Returns valid/invalid and block count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timps_warn_bug_pattern ~39
Check if coding context matches personal bug triggers. Use before writing code under pressure.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Current coding context and conditions |
No output schema declared.
No examples provided.
What is the io.github.Sandeeprdy1729/timps MCP server?
io.github.Sandeeprdy1729/timps is an MCP server listed in the public MCP registry as io.github.Sandeeprdy1729/timps. Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools. This page covers its npm package (@timps-ai/timps-mcp).
Is the io.github.Sandeeprdy1729/timps MCP server safe to use?
io.github.Sandeeprdy1729/timps scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 August 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.Sandeeprdy1729/timps MCP server expose?
io.github.Sandeeprdy1729/timps exposes 69 tools: timps_chat, timps_get_memories, timps_store_memory, timps_check_contradiction, timps_get_positions, and 64 more. Their descriptions and schemas cost roughly 3,645 tokens of context every time the server is loaded.
Is the io.github.Sandeeprdy1729/timps MCP server still maintained?
io.github.Sandeeprdy1729/timps is still listed as active in the MCP registry. We last reached this channel on 23 August 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.Sandeeprdy1729/timps MCP server under?
io.github.Sandeeprdy1729/timps declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.