# EvalyMe (remote · api.evaly.me)

Startup valuation tools: value a business from its metrics or check a for-sale listing's price.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `api.evaly.me`: 70/100 (this document), [markdown](https://verifymcp.io/servers/me-evaly-evalyme/api.md), [page](https://verifymcp.io/servers/me-evaly-evalyme/api)

## Channel facts

- Endpoint: `https://api.evaly.me/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 971 tokens (~323/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 (67% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 EvalyMe MCP server?

EvalyMe is a hosted endpoint at https://api.evaly.me/mcp, so there is nothing to install locally. 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 --transport http me-evaly-evalyme 'https://api.evaly.me/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "me-evaly-evalyme": {
      "url": "https://api.evaly.me/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-evaly-evalyme": {
      "type": "http",
      "url": "https://api.evaly.me/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.me-evaly-evalyme]
url = "https://api.evaly.me/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-evaly-evalyme": {
      "type": "remote",
      "url": "https://api.evaly.me/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-evaly-evalyme --url 'https://api.evaly.me/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-evaly-evalyme:
    url: "https://api.evaly.me/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "me-evaly-evalyme": {
      "Transport": "http",
      "Url": "https://api.evaly.me/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-evaly-evalyme -t streamable-http -u 'https://api.evaly.me/mcp'
```

### Other

```json
{
  "mcpServers": {
    "me-evaly-evalyme": {
      "type": "http",
      "url": "https://api.evaly.me/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-01 (score 69)

First indexed and scored.

## MCP tools (3)

### `value_business` (~341 tokens)

Value a business

Estimates a valuation range, 0-100 investor score, archetype, and top three improvement priorities for a business from its operating metrics: revenue model, MRR, monthly churn, month-over-month growth, and months live, plus optional active users, CAC, and LTV. For a business the user owns or operates. Deterministic and versioned (unified-v1): identical inputs return identical results. Out-of-range values return an error naming the field.

Input parameters:

- `activeUsers` (number): Active users or paying customers, when known.
- `cac` (number): Customer acquisition cost in USD. Used only together with ltv.
- `churnPercent` (number, required): Monthly customer churn as a percent, e.g. 3 means 3% of customers cancel each month.
- `growthRatePercent` (number, required): Month-over-month revenue growth as a percent, e.g. 8 means +8% per month. Negative for decline.
- `ltv` (number): Customer lifetime value in USD. Used only together with cac.
- `monetization` (string, required): Primary revenue model. 'SaaS Subscription' for recurring software; 'Marketplace' for commission/take-rate businesses; 'Advertising' for ad-funded content; 'One-time Purchase' for ecommerce, templates…
- `monthsActive` (number, required): Months the business has been live or earning revenue.
- `mrr` (number, required): Monthly recurring revenue in USD (average monthly revenue for non-subscription models; 0 when pre-revenue).

Output parameters:

- `archetype` (string)
- `assumptions` (array): Every value EvalyMe assumed, derived, or capped. Empty when all inputs were supplied.
- `currency` (string)
- `disclaimer` (string)
- `engineVersion` (string): Model version; results with the same version and inputs are identical.
- `impliedMultipleOnArr` (number): Range midpoint divided by ARR. Absent when ARR is 0.
- `investorScore` (number): 0-100 operating score from six weighted signals.
- `methodologyUrl` (string)
- `modelInput` (object): The exact inputs the engine used.
- `priorities` (array): Up to three weakest weighted signals, each with one concrete next step.
- `saveToEvalyMeUrl` (string): Opens this estimate in the EvalyMe app so the user can save, track, and improve it.
- `scoreBreakdown` (array)
- `valuationHigh` (number)
- `valuationLow` (number)
- `valuationMid` (number)

### `analyze_listing` (~464 tokens)

Analyze a business-for-sale listing

Evaluates a business-for-sale listing (Acquire.com, Flippa, broker) against EvalyMe's model: valuation range, whether the asking price is below, within, or above it, and the asking price as a multiple of ARR and of profit. Accepts the figures a listing states; any figure not supplied gets a documented neutral default, reported in `assumptions`. Yearly growth and annual churn are converted to compounded monthly rates. Evaluates one listing per call.

Input parameters:

- `activeCustomers` (number): Active or paying customers, if the listing states them.
- `ageMonths` (number): Business age in months, e.g. 36 for '3 years old'.
- `annualChurnPercent` (number): Annual churn as a percent. Converted to a compounded monthly rate.
- `annualRevenue` (number): Annual revenue in USD (ARR, TTM, or last-12-months). Used only when monthlyRevenue is absent.
- `askingPrice` (number): Asking price in USD; absent for unpriced or 'make an offer' listings.
- `listingUrl` (string): The listing's URL, echoed back in the result for matching. Never fetched.
- `monetization` (string, required): Primary revenue model. 'SaaS Subscription' for recurring software; 'Marketplace' for commission/take-rate businesses; 'Advertising' for ad-funded content; 'One-time Purchase' for ecommerce, templates…
- `monthlyChurnPercent` (number): Monthly churn as a percent. Takes precedence over annualChurnPercent.
- `monthlyGrowthPercent` (number): Month-over-month revenue growth as a percent. Takes precedence over yearlyGrowthPercent.
- `monthlyProfit` (number): Average monthly net profit or SDE in USD. Used only for the asking-price profit multiple; the valuation model is revenue-based.
- `monthlyRevenue` (number): Monthly revenue in USD (MRR or average monthly revenue). Takes precedence over annualRevenue.
- `yearlyGrowthPercent` (number): Year-over-year revenue growth as a percent, e.g. 40 means +40% YoY. Converted to a compounded monthly rate.

Output parameters:

- `archetype` (string)
- `assumptions` (array): Every value EvalyMe assumed, derived, or capped. Empty when all inputs were supplied.
- `currency` (string)
- `disclaimer` (string)
- `engineVersion` (string): Model version; results with the same version and inputs are identical.
- `impliedMultipleOnArr` (number): Range midpoint divided by ARR. Absent when ARR is 0.
- `investorScore` (number): 0-100 operating score from six weighted signals.
- `listing` (object)
- `methodologyUrl` (string)
- `modelInput` (object): The exact inputs the engine used.
- `priorities` (array): Up to three weakest weighted signals, each with one concrete next step.
- `saveToEvalyMeUrl` (string): Opens this estimate in the EvalyMe app so the user can save, track, and improve it.
- `scoreBreakdown` (array)
- `valuationHigh` (number)
- `valuationLow` (number)
- `valuationMid` (number)

### `explain_methodology` (~60 tokens)

Explain the valuation methodology

Returns EvalyMe's published valuation methodology: the formula, base multiples by revenue model, factor adjustments and caps, investor-score weights, archetype rules, limitations, and versioning policy. For explaining or citing how an EvalyMe valuation was produced.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/me-evaly-evalyme/api#diagnostics

## Score history

- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69

## Common questions

### What is the EvalyMe MCP server?

EvalyMe is an MCP server listed in the public MCP registry as me.evaly/evalyme. Startup valuation tools: value a business from its metrics or check a for-sale listing's price. This page covers its hosted endpoint (https://api.evaly.me/mcp).

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

EvalyMe scores 70 out of 100 on VerifyMCP. 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 EvalyMe MCP server expose?

EvalyMe exposes 3 tools: value_business, analyze_listing, explain_methodology. Their descriptions and schemas cost roughly 865 tokens of context every time the server is loaded.

### Does the EvalyMe MCP server require authentication?

No. We connected to EvalyMe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the EvalyMe MCP server still maintained?

EvalyMe is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.evaly.me/mcp
- Website: https://evaly.me/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/me-evaly-evalyme/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-evaly-evalyme/api.json
- HTML version of this page: https://verifymcp.io/servers/me-evaly-evalyme/api