Sasha, Neural Partners Chief of Staff
REMOTE · WWW.NEURALPARTNERS.AI
Ask Neural Partners' Chief of Staff about services, published pricing and booking a conversation.
Available components
Last scanned (10 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 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 Security71
- 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 enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 504 tokens (~168/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 Management47
- Stability observed for 14 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 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.
- 24 Oct 26 +3
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 68
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 5 Nov 2026 · Probed https://www.neuralpartners.ai/api/sasha/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=neuralpartners.ai | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ebfb1181f1e128f00ef5b3b1b10f3e02 |
| SANs: neuralpartners.ai, *.neuralpartners.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 www.neuralpartners.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| neuralpartners.ai. | present | 2371 | 13 | Verified |
| www.neuralpartners.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 |
| x-frame-options | SAMEORIGIN |
| 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://www.neuralpartners.ai/api/sasha/mcp | Verified | 200 | |
| http (plaintext) | http://www.neuralpartners.ai/api/sasha/mcp | Inconclusive | 403 |
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 →
ask_sasha Ask Sasha about Neural Partners ~169
Sasha, Neural Partners' Chief of Staff, answers questions about what Neural Partners sells: the Neural Core products and platform, the Neural Labs agency and advisory services, whether they fit a business, and how to get a price. structuredContent.links carries the Neural Partners pages her reply points to. One message per call; a conversation continues by conversation_id. Sasha is an AI agent built on Claude and can be wrong. Prices are starting points only. Chats are kept up to 90 days. She never books or submits anything.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | – | The conversation_id an earlier call returned. Omitted, a new conversation starts. Earlier turns are kept server-side, so only the new message is sent. |
| message | string | yes | What to ask or tell Sasha, in plain text. |
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | Continues this conversation on a later call. |
| degraded | boolean | – | True when the reply is a stand-in because Sasha ran out of time; the same message can be sent again. |
| disclosure | string | – | Present on the first reply of a conversation: what the person should know about Sasha. Also sent as its own first content block. |
| error | object | – | Present only on a result with isError: true. |
| links | array | – | The Neural Partners pages Sasha's reply pointed at, as absolute URLs. Only pages on the Neural Partners site are ever listed. Empty when she pointed at none. |
| offer_handoff | boolean | – | True on the reply where Sasha offers to pass the conversation to the Neural Partners team. |
| reply | string | – | Sasha's reply, on its own. The disclosure is never part of it. |
No examples provided.
book_discovery Book a Neural Labs discovery call ~174
Returns a link to the Neural Partners contact page, pre-filled with a summary of the conversation. Nothing is submitted or booked by this tool: the message is sent only if a person opens the link, reviews it and presses send. Email addresses and phone numbers are removed from the summary. An optional message is answered by Sasha before the summary is written. Sasha is an AI agent built on Claude and can be wrong. Prices are starting points only. Chats are kept up to 90 days. She never books or submits anything.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | – | The conversation_id an earlier call returned. Omitted, a new conversation starts. Earlier turns are kept server-side, so only the new message is sent. |
| message | string | – | Optional. A last message for Sasha before the handoff, in plain text. |
| Name | Type | Req | Description |
|---|---|---|---|
| contact_url | string | – | The /contact-us/ link a person opens and sends. Carries only a summary parameter. |
| conversation_id | string | yes | Continues this conversation on a later call. |
| degraded | boolean | – | True when the reply is a stand-in because Sasha ran out of time; the same message can be sent again. |
| disclosure | string | – | Present on the first reply of a conversation: what the person should know about Sasha. Also sent as its own first content block. |
| error | object | – | Present only on a result with isError: true. |
| links | array | – | The Neural Partners pages Sasha's reply pointed at, as absolute URLs. Only pages on the Neural Partners site are ever listed. Empty when she pointed at none. |
| offer_handoff | boolean | – | True on the reply where Sasha offers to pass the conversation to the Neural Partners team. |
| reply | string | – | Sasha's reply, on its own. The disclosure is never part of it. |
| summary_included | boolean | – | False when the link carries no summary. |
No examples provided.
pricing_discovery Neural Labs pricing discovery ~161
Sasha discusses what a Neural Labs agency or advisory engagement would cost. She asks about scope before naming a figure and quotes only Neural Partners' approved starting points, each of which depends on the work. structuredContent.prices carries exactly the approved figures her reply quoted, from configuration, with their conditions. Sasha is an AI agent built on Claude and can be wrong. Prices are starting points only. Chats are kept up to 90 days. She never books or submits anything.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | – | The conversation_id an earlier call returned. Omitted, a new conversation starts. Earlier turns are kept server-side, so only the new message is sent. |
| message | string | yes | The pricing question, or what the work is, in plain text. |
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | Continues this conversation on a later call. |
| degraded | boolean | – | True when the reply is a stand-in because Sasha ran out of time; the same message can be sent again. |
| disclosure | string | – | Present on the first reply of a conversation: what the person should know about Sasha. Also sent as its own first content block. |
| error | object | – | Present only on a result with isError: true. |
| links | array | – | The Neural Partners pages Sasha's reply pointed at, as absolute URLs. Only pages on the Neural Partners site are ever listed. Empty when she pointed at none. |
| offer_handoff | boolean | – | True on the reply where Sasha offers to pass the conversation to the Neural Partners team. |
| prices | array | – | The approved Neural Partners starting prices Sasha's reply quoted, read from Neural Partners' configuration rather than from the reply text. Empty when she quoted none. |
| reply | string | – | Sasha's reply, on its own. The disclosure is never part of it. |
No examples provided.
How do I install the Sasha, Neural Partners Chief of Staff MCP server?
Sasha, Neural Partners Chief of Staff is a hosted endpoint at https://www.neuralpartners.ai/api/sasha/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 · www.neuralpartners.ai
claude mcp add --transport http ai-neuralpartners-sasha 'https://www.neuralpartners.ai/api/sasha/mcp'
What is the Sasha, Neural Partners Chief of Staff MCP server?
Sasha, Neural Partners Chief of Staff is an MCP server listed in the public MCP registry as ai.neuralpartners/sasha. Ask Neural Partners' Chief of Staff about services, published pricing and booking a conversation. This page covers its hosted endpoint (https://www.neuralpartners.ai/api/sasha/mcp).
Is the Sasha, Neural Partners Chief of Staff MCP server safe to use?
Sasha, Neural Partners Chief of Staff scores 76 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 Sasha, Neural Partners Chief of Staff MCP server expose?
Sasha, Neural Partners Chief of Staff exposes 3 tools: ask_sasha, pricing_discovery, book_discovery. Their descriptions and schemas cost roughly 504 tokens of context every time the server is loaded.
Does the Sasha, Neural Partners Chief of Staff MCP server require authentication?
No. We connected to Sasha, Neural Partners Chief of Staff without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sasha, Neural Partners Chief of Staff MCP server still maintained?
Sasha, Neural Partners Chief of Staff is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.