Servana
REMOTE · SERVANA.AI · SCANNED SEP 24
Search and message local service vendors (cleaning, med spa, yoga, personal training) by city.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_message_to_vendor). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 739 tokens (~147/item across 5 items; 5 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 Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Servana MCP server?
Servana is a hosted endpoint at https://servana.ai/api/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 · servana.ai
claude mcp add --transport http ai-servana-servana 'https://servana.ai/api/mcp'
{
"mcpServers": {
"ai-servana-servana": {
"url": "https://servana.ai/api/mcp"
}
}
} {
"servers": {
"ai-servana-servana": {
"type": "http",
"url": "https://servana.ai/api/mcp"
}
}
} [mcp_servers.ai-servana-servana] url = "https://servana.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-servana-servana": {
"type": "remote",
"url": "https://servana.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-servana-servana --url 'https://servana.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-servana-servana:
url: "https://servana.ai/api/mcp" {
"McpServers": {
"ai-servana-servana": {
"Transport": "http",
"Url": "https://servana.ai/api/mcp"
}
}
} assistant mcp add ai-servana-servana -t streamable-http -u 'https://servana.ai/api/mcp'
{
"mcpServers": {
"ai-servana-servana": {
"type": "http",
"url": "https://servana.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Probed https://servana.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=servana.ai | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 4a915063edf87a9e0e8e341d0aaedb04 |
| SANs: servana.ai, *.servana.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 insecure
Validation of servana.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| servana.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://servana.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://servana.ai/api/mcp | HTTPS enforced | 301 | https://servana.ai/api/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 →
estimate_service_request ~228
Get a rough price estimate for a service in a given city, based on Servana vendors' posted rates. Always a heuristic ESTIMATE, not a quote from any specific vendor: actual pricing is set by each vendor. Response includes a confidence level ('high' = 5+ locally priced vendors, 'medium' = 2-4, 'low' = 0-1, in which case the range falls back to a category-wide median across all metros) and an explanation string naming the sample size and metro used.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, lowercase, hyphenated (e.g. 'tampa') |
| hours | number | – | Optional: estimated hours needed, if known. Overrides job_size for hourly-rate services. |
| job_size | string | – | Rough size of the job. Defaults to 'medium'. |
| service | string | yes | Service slug, use search_services to find it (e.g. 'cleaning-and-organizing') |
| state | string | yes | US state slug, lowercase, hyphenated (e.g. 'florida') |
No output schema declared.
No examples provided.
get_vendor ~58
Get one Servana vendor's public profile: name, description, services + pricing, verification status, rating, and page URL.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor_slug | string | yes | The vendor's slug from search_vendors results or a servana.ai vendor URL |
No output schema declared.
No examples provided.
search_services ~89
Look up Servana's service categories by free-text description (e.g. 'someone to fold my laundry', 'deep clean my apartment'). Use this first when you don't already have an exact service slug: it maps everyday requests to the category slug search_vendors and estimate_service_request expect.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text description of what the user needs (a task, not a category name) |
No output schema declared.
No examples provided.
search_vendors ~159
Search Servana's directory of local service businesses (cleaning, med spa, yoga, personal training, and more) by US state, city, and service. Returns business names, descriptions, verification status, rating, pricing, and page URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug, lowercase, hyphenated (e.g. 'tampa', 'los-angeles') |
| service | string | – | Optional service slug (e.g. 'cleaning-and-organizing', 'med-spa', 'yoga', 'personal-training', 'laundry'), use search_services to find it |
| state | string | yes | US state slug, lowercase, hyphenated (e.g. 'florida', 'new-york') |
No output schema declared.
No examples provided.
send_message_to_vendor ~104
Send a message or booking enquiry to a Servana vendor on the user's behalf. The vendor sees it in their Servana inbox. Include what the user needs, and contact details so the vendor can reply. Requires the user's explicit approval before calling: this contacts a real business.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The enquiry, including the user's name and preferred contact (email or phone) so the vendor can respond |
| vendor_slug | string | yes | The vendor's slug |
No output schema declared.
No examples provided.
What is the Servana MCP server?
Servana is an MCP server listed in the public MCP registry as ai.servana/servana. Search and message local service vendors (cleaning, med spa, yoga, personal training) by city. This page covers its hosted endpoint (https://servana.ai/api/mcp).
Is the Servana MCP server safe to use?
Servana scores 78 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 Servana MCP server expose?
Servana exposes 5 tools: search_services, search_vendors, get_vendor, estimate_service_request, send_message_to_vendor. Their descriptions and schemas cost roughly 638 tokens of context every time the server is loaded.
Does the Servana MCP server require authentication?
No. We connected to Servana without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Servana MCP server still maintained?
Servana is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.