TempoRevenue
NPM · @TEMPOREVENUE/MCP · 2 COMPONENTS
Turn a client conversation into a priced proposal draft and track whether clients open or accept it.
Available components
Last scanned (5 hours ago)
Scores higher than 87% of npm servers
Category CRM and Sales
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to TempoRevenue/mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 651 tokens (~93/item across 7 items; 5 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 +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.
- 1 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 +27
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Dependency health: unverified → pass ▲ functional
- 30 Oct 26 +1
- Known CVEs: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: TempoRevenue/mcp security
- Schema quality: 414 → 651 ▼ functional
- Dependency health: pass → unverified ▼ functional
- 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 functional
- 29 Oct 26 55
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 5 Nov 2026 · Analysed npm/@temporevenue/mcp@1.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | TempoRevenue/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/TempoRevenue/mcp/.github/workflows/release.yml@refs/tags/v1.2.0 |
| Rekor log index | 3580389052 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d44cfaae0292eda5ecf554a78f6946289e804bc7c6b7a75b52d7eeb3d77eea45565c05e7e60a04b50d879c48fecbe72212e4bd30cc30cde096ff68578 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
calculate_sow_pricing Calculate SOW pricing ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| buffer_percent | integer | – | Scope risk buffer in percent. Defaults to 20. |
| client_message | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| buffer_hours | number | – | – |
| buffer_percent | integer | yes | – |
| currency | string | yes | – |
| hourly_rate | number | yes | – |
| line_items | array | yes | – |
| preview_url | string | yes | Opens this estimate, editable, in the TempoRevenue web calculator. |
| signals | array | – | – |
| subtotal_hours | number | – | – |
| total_hours | number | yes | – |
| total_price | number | yes | – |
No examples provided.
create_proposal Create proposal ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_name | string | – | The client's name, if known. |
| deal_description | string | yes | 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. |
No output schema declared.
No examples provided.
get_credit_balance Get credit balance ~22
Return how many proposals the user can still create in TempoRevenue.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_proposal_status Get proposal status ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Proposal id returned by create_proposal or list_proposals. |
No output schema declared.
No examples provided.
list_proposals List proposals ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many proposals to return (1 to 20, default 10). |
| status | string | – | Only proposals in this status. |
No output schema declared.
No examples provided.
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.
npm · @temporevenue/mcp
claude mcp add com-temporevenue-proposals -- npx -y @temporevenue/mcp
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.