io.github.tsutera09/tempo
PYPI · TEMPO-MCP · SCANNED SEP 20
Founder-vitals connector joining human capacity to business load for solo operators.
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 41 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 921 tokens (~83/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.tsutera09/tempo MCP server?
io.github.tsutera09/tempo runs locally as a PyPI package, launched with uvx tempo-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 · tempo-mcp
claude mcp add tsutera09-tempo -- uvx tempo-mcp
{
"mcpServers": {
"tsutera09-tempo": {
"command": "uvx",
"args": [
"tempo-mcp"
]
}
}
} {
"servers": {
"tsutera09-tempo": {
"command": "uvx",
"args": [
"tempo-mcp"
]
}
}
} codex mcp add tsutera09-tempo -- uvx tempo-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tsutera09-tempo": {
"type": "local",
"command": [
"uvx",
"tempo-mcp"
],
"enabled": true
}
}
} openclaw mcp add tsutera09-tempo --command uvx --arg tempo-mcp
mcp_servers:
tsutera09-tempo:
command: "uvx"
args: ["tempo-mcp"] {
"McpServers": {
"tsutera09-tempo": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"tempo-mcp"
]
}
}
} assistant mcp add tsutera09-tempo -t stdio -c uvx -a tempo-mcp
{
"mcpServers": {
"tsutera09-tempo": {
"command": "uvx",
"args": [
"tempo-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.
- 18 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 9 Sept 26 −2
- Stability: pass → 0.80 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 20 Sept 2026 · Analysed pypi/tempo-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| 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 →
activate_license ~57
Activate a Tempo Pro or Team Solo licence key. Paste the key from the welcome email. It is verified offline against Tempo's signing key and saved to ~/.tempo/license — nothing is sent anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
apply_action ~165
Record — or on Pro, execute — an action Tempo recommended. Args: kind: auto_decline, reprice, rest_day, block_deep_work, ... payload: the action's parameters (who, when, how much) outcome: applied | dismissed | pending execute: Pro only. Hand the action to the connected executor (Cal.com / Stripe / Gmail) instead of only writing it down. Pro allows 3 executions per day; Team Solo is unlimited. Logging is always free — the decision record is the point of the free tier, and it is what makes the weekly retrospective honest.
| Name | Type | Req | Description |
|---|---|---|---|
| execute | boolean | – | – |
| kind | string | yes | – |
| outcome | string | – | – |
| payload | object | yes | – |
No output schema declared.
No examples provided.
export_data ~78
Export the full local Tempo dataset. Pro and Team Solo only. Args: fmt: "json" for the raw records, "csv" for one CSV block per table. Your data is yours; this is the door out. It reads the local SQLite database and returns it inline — nothing is uploaded.
| Name | Type | Req | Description |
|---|---|---|---|
| fmt | string | – | – |
No output schema declared.
No examples provided.
get_history ~79
Return the full time-series history so Claude can surface trends. Returns daily check-in snapshots, revenue by day, and calendar load over the requested window. Useful for building sparklines, comparing weeks, or asking "am I actually getting better?" Free tier returns the last 7 days; Pro returns everything.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
ingest_calendar_event ~87
Ingest a calendar event. kind ∈ {sales, deep_work, admin, personal}. As with revenue: manual entry is free, connector-sourced ingest is Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| end_iso | string | yes | – |
| external | boolean | – | – |
| kind | string | yes | – |
| source | string | – | – |
| start_iso | string | yes | – |
| title | – | – | – |
No output schema declared.
No examples provided.
ingest_revenue_event ~83
Record a revenue event. Amounts in the user's home currency. Typing one in by hand (source="manual") is free. Automated ingest from an upstream connector — Stripe, QuickBooks, a wearable bridge — is a Pro feature.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| iso_ts | – | – | – |
| meta | – | – | – |
| source | string | – | – |
No output schema declared.
No examples provided.
license_status ~45
Show the active Tempo plan and what it unlocks. Call this whenever the user asks what they're paying for, why a tool refused, or how much history they can see.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_checkin ~112
Log a morning (or moment-in-time) founder check-in. Args: mood: 1..10, subjective mood energy: 1..10, subjective energy stress: 1..10, subjective stress sleep_hours: hours of sleep last night (can be fractional) note: optional free text
| Name | Type | Req | Description |
|---|---|---|---|
| energy | integer | yes | – |
| mood | integer | yes | – |
| note | – | – | – |
| sleep_hours | number | yes | – |
| stress | integer | yes | – |
No output schema declared.
No examples provided.
recommend_actions ~52
Return prescriptive business actions based on current Tempo state. These are the decisions that separate Tempo from a wellness tracker: price raises, meeting declines, rest days, deep-work blocks.
| Name | Type | Req | Description |
|---|---|---|---|
| window_days | integer | – | – |
No output schema declared.
No examples provided.
tempo_score ~75
Compute the current Tempo score and supporting metrics. Returns tempo (0..100), capacity, load, RpRH (revenue per recovery hour) and its 7-day delta, plus human-readable signals and alerts. Free tier scores over the last 7 days; Pro over any window.
| Name | Type | Req | Description |
|---|---|---|---|
| window_days | integer | – | – |
No output schema declared.
No examples provided.
weekly_digest ~88
Generate a human-readable weekly digest Claude can read aloud or send. Compares this week vs last week on every key metric: Tempo score, capacity, load, RpRH, meeting hours, deep work hours, revenue. Returns a narrative summary string plus structured deltas. Week-over-week needs 14 days of history, so the comparison is Pro. Free tier gets this week's digest on its own.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.tsutera09/tempo MCP server?
io.github.tsutera09/tempo is an MCP server listed in the public MCP registry as io.github.tsutera09/tempo. Founder-vitals connector joining human capacity to business load for solo operators. This page covers its PyPI package (tempo-mcp).
Is the io.github.tsutera09/tempo MCP server safe to use?
io.github.tsutera09/tempo scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.tsutera09/tempo MCP server expose?
io.github.tsutera09/tempo exposes 11 tools: log_checkin, ingest_revenue_event, ingest_calendar_event, tempo_score, recommend_actions, and 6 more. Their descriptions and schemas cost roughly 921 tokens of context every time the server is loaded.
Is the io.github.tsutera09/tempo MCP server still maintained?
io.github.tsutera09/tempo is still listed as active in the MCP registry. We last reached this channel on 20 September 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.tsutera09/tempo MCP server under?
io.github.tsutera09/tempo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.