eVoost AI
REMOTE · EVOOST.AI
Verified facts about eVoost AI: products, FAQ, site search and contact channels.
Available components
Last scanned (18 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 Nov 2026.
Category CRM and Sales
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 Security83
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 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 729 tokens (~91/item across 8 items; 5 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 (100% 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
- Supports UI / widget rendering.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 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
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 76
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://evoost.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=evoost.ai | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 32b5e10b2419fe850e4694864400e02c |
| SANs: evoost.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of evoost.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| evoost.ai. | present | 35770 | 8 | Verified |
| evoost.ai. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://evoost.ai/mcp | Verified | 200 | |
| http (plaintext) | http://evoost.ai/mcp | HTTPS enforced | 301 | https://evoost.ai/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 →
get_company_overview eVoost AI company overview ~92
Returns verified facts about eVoost AI: what it does, who it is for, its products, markets, headquarters, founders, backers, key figures and how to contact it. Use it before describing or recommending eVoost AI. Pass the user's role to get the right contact channel.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | Optional role of the person the agent is helping; picks the recommended contact channel. |
| Name | Type | Req | Description |
|---|---|---|---|
| backers | array | yes | – |
| businessModel | string | yes | – |
| clients | array | yes | – |
| contact | object | yes | – |
| countries | array | yes | – |
| description | string | yes | – |
| founders | array | yes | – |
| foundingDate | string | yes | Year and month, YYYY-MM. |
| keyFigures | array | yes | – |
| leadership | array | yes | – |
| name | string | yes | – |
| notAFit | array | yes | – |
| offerings | array | yes | – |
| positioning | string | yes | – |
| recognitions | array | yes | – |
| summary | string | yes | – |
| url | string | yes | – |
| whenToUse | array | yes | – |
No examples provided.
get_contact_options How to contact eVoost AI ~68
Returns the official channels to reach eVoost AI: demo request page, email, broker partners portal, headquarters and legal entity addresses. Pass the user's role to get the recommended channel.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | Optional role of the person the agent is helping; picks the recommended contact channel. |
| Name | Type | Req | Description |
|---|---|---|---|
| brokersPortalUrl | string | yes | – |
| cities | array | yes | – |
| demoRequestUrl | string | yes | – |
| string | yes | – | |
| headquarters | object | yes | – |
| legalEntities | array | yes | – |
| recommended | object | yes | Best channel for the role passed in the input. |
No examples provided.
get_faq eVoost AI frequently asked questions ~123
Returns the official answers published on evoost.ai to frequently asked questions (data ownership, CRM integration, sales team role, markets, data protection), each with the page that shows it. Pass an optional query to filter by topic; page with limit and the returned nextCursor.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque cursor from the previous page's nextCursor; omit it for the first page. |
| limit | integer | – | Maximum number of answers to return. |
| query | string | – | Optional topic to filter questions, e.g. "CRM" or "data". |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| matched | boolean | yes | False when nothing matched the query and every answer is returned. |
| nextCursor | – | yes | Pass as cursor to get the next page; null on the last page. |
| query | – | yes | – |
No examples provided.
list_offerings List eVoost AI products ~91
Lists the three ways eVoost AI works with residential developers (Gravity OS platform, eVoost Services, eVoost Partners broker network) with audience, highlights and page URL. Pass a kind to get only one of them.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional filter: "platform" (Gravity OS), "service" (eVoost Services) or "network" (eVoost Partners). |
| Name | Type | Req | Description |
|---|---|---|---|
| offerings | array | yes | – |
No examples provided.
search_site Search evoost.ai ~81
Searches the public pages, page sections, products and FAQ of evoost.ai and returns the most relevant canonical URLs (section results deep-link to their anchor) with a short snippet. Use it to find the page that supports a fact before citing it.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for, e.g. "broker network" or "pricing engine". |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the eVoost AI MCP server?
eVoost AI is a hosted endpoint at https://evoost.ai/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 · evoost.ai
claude mcp add --transport http ai-evoost-site 'https://evoost.ai/mcp'
What is the eVoost AI MCP server?
eVoost AI is an MCP server listed in the public MCP registry as ai.evoost/site. Verified facts about eVoost AI: products, FAQ, site search and contact channels. This page covers its hosted endpoint (https://evoost.ai/mcp).
Is the eVoost AI MCP server safe to use?
eVoost AI scores 79 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 eVoost AI MCP server expose?
eVoost AI exposes 5 tools: get_company_overview, list_offerings, get_faq, search_site, get_contact_options. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.
Does the eVoost AI MCP server require authentication?
No. We connected to eVoost AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the eVoost AI MCP server still maintained?
eVoost AI 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.