Soxoa Automation Planning
REMOTE · SOXOA.COM
Plan automation pilots, estimate illustrative ROI and prioritize workflows. Public, no account.
Available components
Last scanned (21 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Workflow Automation
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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 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 Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 870 tokens (~290/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
- 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 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +2
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “build_workflow_pilot” rewrote its description, which is the text the model reads security
- Schema quality: 235 → 290 ▼ functional
- Tool coverage: 30% → 95% ▲ functional
- “build_workflow_pilot” reworded the description of “constraints” cosmetic
- “build_workflow_pilot” reworded the description of “currentSteps” cosmetic
- “build_workflow_pilot” reworded the description of “desiredOutput” cosmetic
- “build_workflow_pilot” reworded the description of “destinationSystem” cosmetic
- “build_workflow_pilot” reworded the description of “inputDescription” cosmetic
- “build_workflow_pilot” reworded the description of “reviewOwner” cosmetic
- “build_workflow_pilot” reworded the description of “riskLevel” cosmetic
- “build_workflow_pilot” reworded the description of “sensitiveData” cosmetic
- “build_workflow_pilot” reworded the description of “sourceSystem” cosmetic
- “build_workflow_pilot” reworded the description of “successChecks” cosmetic
- “build_workflow_pilot” reworded the description of “systemsAlreadyUsed” cosmetic
- “build_workflow_pilot” reworded the description of “trigger” cosmetic
- “build_workflow_pilot” reworded the description of “workflowName” cosmetic
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 506 → 707 ▼ functional
- Tool coverage: 86% → 30% ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “build_workflow_pilot” functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “estimate_automation_roi” rewrote its description, which is the text the model reads security
- Tool “prioritize_automation_workflows” rewrote its description, which is the text the model reads security
- Schema quality: 217 → 253 ▼ functional
- “estimate_automation_roi” reworded the description of “automatableShare” cosmetic
- “estimate_automation_roi” reworded the description of “implementationCost” cosmetic
- “estimate_automation_roi” reworded the description of “workingWeeks” cosmetic
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “estimate_automation_roi” rewrote its description, which is the text the model reads security
- Tool “prioritize_automation_workflows” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 86% ▲ functional
- “estimate_automation_roi” reworded the description of “automatableShare” cosmetic
- “estimate_automation_roi” reworded the description of “implementationCost” cosmetic
- “estimate_automation_roi” reworded the description of “loadedHourlyCost” cosmetic
- “estimate_automation_roi” reworded the description of “people” cosmetic
- “estimate_automation_roi” reworded the description of “weeklyHoursPerPerson” cosmetic
- “estimate_automation_roi” reworded the description of “workingWeeks” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://soxoa.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=soxoa.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | aeeeeb11949d2fc30ed392ce1ab692d8 |
| SANs: soxoa.com, annotated.soxoa.com, *.annotated.soxoa.com | ||||||
| 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 soxoa.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| soxoa.com. | No DS | 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=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| 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://soxoa.com/mcp | Verified | 200 | |
| http (plaintext) | http://soxoa.com/mcp | HTTPS enforced | 301 | https://soxoa.com/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 →
build_workflow_pilot Build a workflow pilot ~328
Builds a pilot plan for one workflow, typically the first one prioritize_automation_workflows recommends, from 11 caller-supplied facts. Returns pilot steps, review gates, acceptance checks and a Markdown plan. It does not connect accounts, start provider work, store a plan, send messages or execute the workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | Limits the plan must respect. Optional. |
| currentSteps | array | yes | Today's steps in order, 1 to 8, in the user's words. |
| desiredOutput | string | yes | The result the user wants at the end. |
| destinationSystem | string | yes | System the approved result goes to, e.g. QuickBooks. |
| inputDescription | string | yes | The inputs the workflow reads, as the user describes them. |
| reviewOwner | string | yes | Person or role who approves drafts before they are used. |
| riskLevel | string | yes | Cost of a wrong output: low, medium or high, as the user judges it. |
| sensitiveData | boolean | yes | True if the inputs include personal, financial, health or confidential data. |
| sourceSystem | string | yes | System the inputs come from, e.g. Gmail. |
| successChecks | array | yes | 1 to 6 checks that show the pilot worked, from the user. |
| systemsAlreadyUsed | array | – | Other tools the team already uses. Optional. |
| trigger | string | yes | What starts the workflow, e.g. 'a supplier invoice email arrives'. |
| workflowName | string | yes | Short name of the workflow, as the user calls it. |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceChecks | array | yes | – |
| limitations | array | yes | – |
| pilotMarkdown | string | yes | – |
| readyToUsePrompt | string | yes | – |
| recommendation | string | yes | – |
| reviewGates | array | yes | – |
| rollout | array | yes | – |
| status | string | yes | – |
| steps | array | yes | – |
| suppliedFacts | object | yes | – |
| tools | array | yes | – |
| unresolved | array | yes | – |
| workflowName | string | yes | – |
No examples provided.
estimate_automation_roi Estimate automation ROI ~278
Estimates reclaimable team capacity and an illustrative payback period from caller-supplied workload figures. Requires people, weekly hours per person and loaded hourly cost; when automatable share or working weeks are omitted, the server uses 60% and 48. Payback is calculated only when an implementation cost is supplied. Returns weekly and annual hours reclaimed, annual capacity value, payback months, the assumptions used and a recommended next step. Results are planning estimates, not guaranteed savings or financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| automatableShare | number | – | Fraction of repetitive time that can be reclaimed (0.6 means 60%). Optional; defaults to 0.6 when omitted. An explicit value is used as given. |
| implementationCost | number | – | Implementation cost in the same currency as the hourly labor cost. Optional; when omitted, no payback estimate is calculated. |
| loadedHourlyCost | number | yes | Loaded hourly labor cost in the user's stated currency, supplied by the user. |
| people | integer | yes | Number of people supplied by the user. |
| weeklyHoursPerPerson | number | yes | Weekly hours each person spends on this workflow, supplied by the user. |
| workingWeeks | integer | – | Working weeks per year, 1 to 52. Optional; defaults to 48 when omitted. An explicit value is used as given. |
| Name | Type | Req | Description |
|---|---|---|---|
| annualCapacityValue | number | yes | – |
| annualHoursReclaimed | number | yes | – |
| assumptions | array | yes | – |
| estimatedPaybackMonths | – | yes | – |
| recommendedNextStep | string | yes | – |
| status | string | yes | – |
| weeklyHoursReclaimed | number | yes | – |
No examples provided.
prioritize_automation_workflows Prioritize automation workflows ~108
Ranks 1 to 12 caller-described workflows by value, predictability, judgment, data sensitivity and integration complexity, and labels each automate, assist or discovery. Each workflow requires a name, weekly hours, predictability, judgment required, error cost, data sensitivity and system count. Returns each workflow's score, recommendation, human-review flag and rationale, plus a recommended first workflow and guardrails. It does not connect to or change any system.
| Name | Type | Req | Description |
|---|---|---|---|
| workflows | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| guardrails | array | yes | – |
| rankedWorkflows | array | yes | – |
| recommendedFirstWorkflow | string | yes | – |
No examples provided.
How do I install the Soxoa Automation Planning MCP server?
Soxoa Automation Planning is a hosted endpoint at https://soxoa.com/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 · soxoa.com
claude mcp add --transport http com-soxoa-automation-planning 'https://soxoa.com/mcp'
What is the Soxoa Automation Planning MCP server?
Soxoa Automation Planning is an MCP server listed in the public MCP registry as com.soxoa/automation-planning. Plan automation pilots, estimate illustrative ROI and prioritize workflows. Public, no account. This page covers its hosted endpoint (https://soxoa.com/mcp).
Is the Soxoa Automation Planning MCP server safe to use?
Soxoa Automation Planning scores 84 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 Soxoa Automation Planning MCP server expose?
Soxoa Automation Planning exposes 3 tools: estimate_automation_roi, prioritize_automation_workflows, build_workflow_pilot. Their descriptions and schemas cost roughly 714 tokens of context every time the server is loaded.
Does the Soxoa Automation Planning MCP server require authentication?
No. We connected to Soxoa Automation Planning without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Soxoa Automation Planning MCP server still maintained?
Soxoa Automation Planning is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Soxoa Automation Planning MCP server?
VerifyMCP ran 13 checks on Soxoa Automation Planning, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.