MCP.Market

TempoRevenue MCP server

online · 100% uptime
by temporevenue.com·com.temporevenue/proposals·v1.2.0
No reviews yet

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

B77/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed TempoRevenue yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

TempoRevenue tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How TempoRevenue compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
186 ms
faster than 66% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-06, latest 2026-10-30, typically one every 23 days.

Install TempoRevenue in Claude Code, Cursor or VS Code

claude mcp add --transport http proposals https://app.temporevenue.com/api/mcp
Add to Cursor

TempoRevenue: common questions

Is TempoRevenue MCP server safe?
Mostly: it is graded B (77/100). Read the TempoRevenue safety report
How do I install TempoRevenue?
It runs remotely at app.temporevenue.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does TempoRevenue need an API key?
Yes. The registry entry asks for TEMPOREVENUE_API_KEY.
Is TempoRevenue maintained?
The latest release is v1.2.0.
Is TempoRevenue up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does TempoRevenue compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 186 ms (faster than 66% of 30,031 servers). Full comparison.