Phos Sales Engine
REMOTE · SE.PHOS.NZ · SCANNED SEP 20
B2B lead generation — prospect discovery, ICP scoring, outreach, and pipeline management.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 502, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Phos Sales Engine MCP server?
Phos Sales Engine is a hosted endpoint at https://se.phos.nz/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 · se.phos.nz
claude mcp add --transport http albermm-phos-sales-engine 'https://se.phos.nz/mcp/'
{
"mcpServers": {
"albermm-phos-sales-engine": {
"url": "https://se.phos.nz/mcp/"
}
}
} {
"servers": {
"albermm-phos-sales-engine": {
"type": "http",
"url": "https://se.phos.nz/mcp/"
}
}
} [mcp_servers.albermm-phos-sales-engine] url = "https://se.phos.nz/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"albermm-phos-sales-engine": {
"type": "remote",
"url": "https://se.phos.nz/mcp/",
"enabled": true
}
}
} openclaw mcp add albermm-phos-sales-engine --url 'https://se.phos.nz/mcp/' --transport streamable-http
mcp_servers:
albermm-phos-sales-engine:
url: "https://se.phos.nz/mcp/" {
"McpServers": {
"albermm-phos-sales-engine": {
"Transport": "http",
"Url": "https://se.phos.nz/mcp/"
}
}
} assistant mcp add albermm-phos-sales-engine -t streamable-http -u 'https://se.phos.nz/mcp/'
{
"mcpServers": {
"albermm-phos-sales-engine": {
"type": "http",
"url": "https://se.phos.nz/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.
- 9 Sept 26 0
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- TLS certificate: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- 8 Sept 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 26 Aug 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
- 12 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- 11 Aug 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
- 31 Jul 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
- 27 Jul 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
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://se.phos.nz/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=phos.nz | CN=WE1,O=Google Trust Services,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 2501249e0a243775133cf2c386f1e412 |
| SANs: phos.nz, *.phos.nz | ||||||
| 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 se.phos.nz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| nz. | present | 38240, 62081 | 8, 8 | Verified |
| phos.nz. | 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 | 502 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://se.phos.nz/mcp/ | HTTP error | 502 | |
| http (plaintext) | http://se.phos.nz/mcp/ | Inconclusive | 502 |
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 →
find_prospects ~118
Find business prospects by industry and location in NZ. Uses Yellow Pages and other scrapers to discover real businesses, deduplicates against existing DB.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your Sales Engine API key |
| industry | string | yes | Industry or business category (e.g. "plumber", "cafe", "gym") |
| limit | number | – | Max prospects to return (1-50) |
| location | string | yes | NZ city or region (e.g. "Auckland", "Wellington", "Christchurch") |
No output schema declared.
No examples provided.
generate_outreach ~64
Generate a personalized outreach message for a prospect using Claude AI sales brain. Returns subject, body, personalization points, and alternative subjects.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your Sales Engine API key |
| prospect_id | string | yes | UUID of the prospect to generate outreach for |
No output schema declared.
No examples provided.
get_pipeline ~55
Get pipeline statistics — prospects by stage, conversion rates, and daily metrics. Free (0 credits).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your Sales Engine API key |
| product | string | – | Product name (default: phos) |
No output schema declared.
No examples provided.
score_prospect ~59
Score a prospect against your Ideal Customer Profile (ICP). Returns fit score 0-100 with detailed breakdown and contributing factors.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your Sales Engine API key |
| prospect_data | object | yes | Prospect data to score |
No output schema declared.
No examples provided.
What is the Phos Sales Engine MCP server?
Phos Sales Engine is an MCP server listed in the public MCP registry as io.github.albermm/phos-sales-engine. B2B lead generation, prospect discovery, ICP scoring, outreach, and pipeline management. This page covers its hosted endpoint (https://se.phos.nz/mcp/).
Is the Phos Sales Engine MCP server safe to use?
Phos Sales Engine scores 18 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 Phos Sales Engine MCP server expose?
Phos Sales Engine exposes 4 tools: find_prospects, score_prospect, generate_outreach, get_pipeline. Their descriptions and schemas cost roughly 296 tokens of context every time the server is loaded.
Does the Phos Sales Engine MCP server require authentication?
No. We connected to Phos Sales Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Phos Sales Engine MCP server still maintained?
Phos Sales Engine is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.