EvalyMe
REMOTE · API.EVALY.ME
Startup valuation tools: value a business from its metrics or check a for-sale listing's price.
Available components
Last scanned (20 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 (67% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 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.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 69
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 4 Nov 2026 · Probed https://api.evaly.me/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=evaly.me | CN=YE2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5e126bcb190361b6baf24bf86bb4d1f7887 |
| SANs: *.evaly.me, evaly.me | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.evaly.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| evaly.me. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.evaly.me/mcp | Verified | 200 | |
| http (plaintext) | http://api.evaly.me/mcp | HTTPS enforced | 301 | https://api.evaly.me/mcp |
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 →
analyze_listing Analyze a business-for-sale listing ~464
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| archetype | string | yes | – |
| assumptions | array | yes | Every value EvalyMe assumed, derived, or capped. Empty when all inputs were supplied. |
| currency | string | yes | – |
| disclaimer | string | yes | – |
| engineVersion | string | yes | 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 | yes | 0-100 operating score from six weighted signals. |
| listing | object | yes | – |
| methodologyUrl | string | yes | – |
| modelInput | object | yes | The exact inputs the engine used. |
| priorities | array | yes | 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 | yes | – |
| valuationHigh | number | yes | – |
| valuationLow | number | yes | – |
| valuationMid | number | yes | – |
No examples provided.
explain_methodology Explain the valuation methodology ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
value_business Value a business ~341
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.
| Name | Type | Req | Description |
|---|---|---|---|
| activeUsers | number | – | Active users or paying customers, when known. |
| cac | number | – | Customer acquisition cost in USD. Used only together with ltv. |
| churnPercent | number | yes | Monthly customer churn as a percent, e.g. 3 means 3% of customers cancel each month. |
| growthRatePercent | number | yes | 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 | yes | 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 | yes | Months the business has been live or earning revenue. |
| mrr | number | yes | Monthly recurring revenue in USD (average monthly revenue for non-subscription models; 0 when pre-revenue). |
| Name | Type | Req | Description |
|---|---|---|---|
| archetype | string | yes | – |
| assumptions | array | yes | Every value EvalyMe assumed, derived, or capped. Empty when all inputs were supplied. |
| currency | string | yes | – |
| disclaimer | string | yes | – |
| engineVersion | string | yes | 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 | yes | 0-100 operating score from six weighted signals. |
| methodologyUrl | string | yes | – |
| modelInput | object | yes | The exact inputs the engine used. |
| priorities | array | yes | 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 | yes | – |
| valuationHigh | number | yes | – |
| valuationLow | number | yes | – |
| valuationMid | number | yes | – |
No examples provided.
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.
remote · api.evaly.me
claude mcp add --transport http me-evaly-evalyme 'https://api.evaly.me/mcp'
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.