Timps runs on your own machine — the client starts it, so there is no endpoint to ping. 10 installs a week from npm. Last commit 14 Sep 2026.
Persistent memory with contradiction detection, burnout monitoring, and 69 intelligence tools.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const fullPath = path.join(cwd, file);
async eval(script: string, keys: string[], args: unknown[]): Promise<unknown> {
exec(command: string, options?: ExecOptions): Promise<ExecResult> {
contentEl.innerHTML = content;
private apiBase = 'https://api.telegram.org';
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add timps -- npx -y @timps-ai/timps-mcp
{
"mcpServers": {
"timps": {
"command": "npx",
"args": [
"-y",
"@timps-ai/timps-mcp"
]
}
}
}
[mcp_servers.timps]
command = "npx"
args = ["-y", "@timps-ai/timps-mcp"]
{
"mcpServers": {
"timps": {
"command": "npx",
"args": [
"-y",
"@timps-ai/timps-mcp"
]
}
}
}
{
"servers": {
"timps": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@timps-ai/timps-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
TIMPS_URL (URL of the TIMPS MemoryServer (e.g. http://localhost:4100). If not set, uses local file-based memory), TIMPS_MEMORY_URL (URL of the TIMPS MemoryServer for memory operations. Set to same as TIMPS_URL when using the full stack), TIMPS_API_KEY (API key for authenticating with TIMPS MemoryServer. Generate via POST /auth/key on the server), TIMPS_PROJECT_PATH (Project path for local memory storage. Defaults to current working directory).
AI-powered news intelligence — 21 tools for personalized monitoring, briefings, and semantic search
DataFinder analytics with 52 tools, metric dictionaries, persistent jobs and confirmed changes.
9 MCP tools: extract, analyze, research, compare, monitor, brief. Pay-per-call x402 or subscribe.
Real-time global intelligence across conflict, markets, energy, trade, shipping and cyber. 95 tools.
28 pay-per-event tools for regulatory, sanctions, procurement, and corporate-registry monitoring.
Build, inspect, flash, and monitor PlatformIO firmware projects with policy-controlled tools.
Typed access to monitored competitive changes, evidence, dossiers, research, and collection health.
Peppol market intelligence and network monitoring: migrations, provider churn, leads, and uptime.
Answers built from our own checks of this server.