# TempoRevenue (npm · @temporevenue/mcp)

Turn a client conversation into a priced proposal draft and track whether clients open or accept it.

- Trust score: 85/100 (high trust)
- Change this week: +30
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `app.temporevenue.com`: 38/100, [markdown](https://verifymcp.io/servers/com-temporevenue-proposals/api-mcp.md), [page](https://verifymcp.io/servers/com-temporevenue-proposals/api-mcp)
- npm · `@temporevenue/mcp`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-temporevenue-proposals/temporevenue-mcp.md), [page](https://verifymcp.io/servers/com-temporevenue-proposals/temporevenue-mcp)

## Channel facts

- Registry: `npm`
- Package: `@temporevenue/mcp`
- Version: `1.2.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-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to TempoRevenue/mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 651 tokens (~93/item across 7 items; 5 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (20% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 TempoRevenue MCP server?

TempoRevenue runs locally as an npm package, launched with npx -y @temporevenue/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 com-temporevenue-proposals -- npx -y @temporevenue/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-temporevenue-proposals": {
      "command": "npx",
      "args": [
        "-y",
        "@temporevenue/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-temporevenue-proposals": {
      "command": "npx",
      "args": [
        "-y",
        "@temporevenue/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-temporevenue-proposals -- npx -y @temporevenue/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-temporevenue-proposals --command npx --arg -y --arg @temporevenue/mcp
```

### Hermes

```yaml
mcp_servers:
  com-temporevenue-proposals:
    command: "npx"
    args: ["-y", "@temporevenue/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-temporevenue-proposals": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@temporevenue/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-temporevenue-proposals -t stdio -c npx -a -y @temporevenue/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-temporevenue-proposals": {
      "command": "npx",
      "args": [
        "-y",
        "@temporevenue/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-03 (score 85, +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-01 (score 84, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 83, +27)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Dependency health: unverified → pass

### 2026-10-30 (score 56, +1)

- [security regression] Known CVEs: pass → unverified
- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: TempoRevenue/mcp
- [functional regression] Schema quality: 414 → 651
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: 100
- [functional] First check of Tool coverage: 20
- [functional] Package version: 1.0.0 → 1.2.0

### 2026-10-29 (score 55)

First indexed and scored.

## MCP tools (5)

### `calculate_sow_pricing` (~181 tokens)

Calculate SOW pricing

Estimate a freelance project from a client message: deliverables found by keyword rules, hours per deliverable, a scope risk buffer and a fixed price (hours times the hourly rate, calculated in integer cents). Runs locally, needs no account and creates nothing. Returns a link to open the same estimate in the TempoRevenue web calculator.

Input parameters:

- `buffer_percent` (integer): Scope risk buffer in percent. Defaults to 20.
- `client_message` (string, required): The client's request, call notes or a feature list.
- `client_name` (string): The client's name, if known.
- `hourly_rate` (number): Hourly rate. Defaults to 100 (or the language's default).
- `language` (string): Language of the labels and currency: en (USD), pt (BRL), es or de (EUR). Defaults to en.

Output parameters:

- `buffer_hours` (number)
- `buffer_percent` (integer)
- `currency` (string)
- `hourly_rate` (number)
- `line_items` (array)
- `preview_url` (string): Opens this estimate, editable, in the TempoRevenue web calculator.
- `signals` (array)
- `subtotal_hours` (number)
- `total_hours` (number)
- `total_price` (number)

### `create_proposal` (~136 tokens)

Create proposal

Create a draft proposal in the user's TempoRevenue account from a short description of the client's request: client name, scope, timeline and budget. If the request states a price, it is used as the total; otherwise the price is calculated from the user's own rates. Returns a link to review and send. Uses one proposal from the user's allowance.

Input parameters:

- `client_name` (string): The client's name, if known.
- `deal_description` (string, required): Brief description of the client's request. Do not send the full chat history.
- `language` (string): Language of the proposal. If omitted, it follows the language of the description.

### `get_proposal_status` (~77 tokens)

Get proposal status

Check the status of a proposal in the user's TempoRevenue account: draft, viewed or accepted, with the date the client first opened it and the date they accepted it. Use the `id` returned by create_proposal or list_proposals.

Input parameters:

- `id` (string, required): Proposal id returned by create_proposal or list_proposals.

### `list_proposals` (~87 tokens)

List proposals

List the user's most recent proposals in TempoRevenue, newest first: id, title, status (draft, viewed or accepted) and a link to open each one. Optionally filter by status. Returns at most 20.

Input parameters:

- `limit` (integer): How many proposals to return (1 to 20, default 10).
- `status` (string): Only proposals in this status.

### `get_credit_balance` (~22 tokens)

Get credit balance

Return how many proposals the user can still create in TempoRevenue.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-temporevenue-proposals/temporevenue-mcp#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 56
- 2026-10-29: 55

## Common questions

### What is the TempoRevenue MCP server?

TempoRevenue is an MCP server listed in the public MCP registry as com.temporevenue/proposals. Turn a client conversation into a priced proposal draft and track whether clients open or accept it. This page covers its npm package (@temporevenue/mcp).

### Is the TempoRevenue MCP server safe to use?

TempoRevenue scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 TempoRevenue MCP server expose?

TempoRevenue exposes 5 tools: calculate_sow_pricing, create_proposal, get_proposal_status, list_proposals, get_credit_balance. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.

### Is the TempoRevenue MCP server still maintained?

TempoRevenue is still listed as active in the MCP registry. We last reached this channel on 5 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 TempoRevenue MCP server under?

TempoRevenue 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 TempoRevenue MCP server?

VerifyMCP ran 16 checks on TempoRevenue, 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/@temporevenue/mcp
- Socket report: https://socket.dev/npm/package/@temporevenue/mcp
- Repository: https://github.com/TempoRevenue/mcp
- Website: https://temporevenue.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-temporevenue-proposals/temporevenue-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-temporevenue-proposals/temporevenue-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-temporevenue-proposals/temporevenue-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-temporevenue-proposals/temporevenue-mcp