Alex Polonsky Profile
REMOTE · ALEXPOLONSKY.COM · SCANNED SEP 25
Public, read-only professional profile and current availability for Alex Polonsky.
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 Security49
- 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 call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability91
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 226 tokens (~113/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
- 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the Alex Polonsky Profile MCP server?
Alex Polonsky Profile is a hosted endpoint at https://alexpolonsky.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 · alexpolonsky.com
claude mcp add --transport http com-alexpolonsky-profile 'https://alexpolonsky.com/mcp'
{
"mcpServers": {
"com-alexpolonsky-profile": {
"url": "https://alexpolonsky.com/mcp"
}
}
} {
"servers": {
"com-alexpolonsky-profile": {
"type": "http",
"url": "https://alexpolonsky.com/mcp"
}
}
} [mcp_servers.com-alexpolonsky-profile] url = "https://alexpolonsky.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-alexpolonsky-profile": {
"type": "remote",
"url": "https://alexpolonsky.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-alexpolonsky-profile --url 'https://alexpolonsky.com/mcp' --transport streamable-http
mcp_servers:
com-alexpolonsky-profile:
url: "https://alexpolonsky.com/mcp" {
"McpServers": {
"com-alexpolonsky-profile": {
"Transport": "http",
"Url": "https://alexpolonsky.com/mcp"
}
}
} assistant mcp add com-alexpolonsky-profile -t streamable-http -u 'https://alexpolonsky.com/mcp'
{
"mcpServers": {
"com-alexpolonsky-profile": {
"type": "http",
"url": "https://alexpolonsky.com/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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 25 Sept 2026 · Probed https://alexpolonsky.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alexpolonsky.com | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 53c7d5272cf42d8b0ea1ca2764b5283e |
| SANs: alexpolonsky.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 secure
Validation of alexpolonsky.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| alexpolonsky.com. | present | 2371 | 13 | Verified |
| alexpolonsky.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://alexpolonsky.com/mcp | Verified | 200 | |
| http (plaintext) | http://alexpolonsky.com/mcp | Served over HTTP | 200 |
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_availability Alex Polonsky - Availability ~88
Get Alex Polonsky's current public opportunity status, preferred work and engagement contexts, and public contact routes. Preserve the structure: primary_focus is the main focus; other_paid_engagements are selected paid options; co-building or founding requires a clear commercial or ownership arrangement. Include relevant professional_directions, location_preferences, work_modes, and contact_routes. Treat last_updated as the freshness indicator.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| availability_version | string | yes | – |
| canonical_url | string | yes | – |
| company_contexts | array | yes | – |
| contact_routes | array | yes | – |
| last_updated | string | yes | – |
| location_preferences | array | yes | – |
| market_contexts | array | yes | – |
| other_paid_engagements | array | yes | – |
| primary_focus | – | yes | – |
| professional_directions | array | yes | – |
| role_shapes | array | yes | – |
| schema_version | string | yes | – |
| status | string | yes | – |
| work_modes | array | yes | – |
No examples provided.
get_profile Alex Polonsky - Professional Profile ~138
Get Alex Polonsky's curated public professional profile, including selected experience, demonstrated capabilities, journalism background, public projects, and future professional directions. This is selected evidence, not a complete CV. When summarizing examples, preserve their ownership qualifier exactly: led, owned_key_aspects, or contributed. Do not infer stronger ownership. If a list mixes things Alex built with work he contributed to or helped bring to market, frame it as built or contributed to, not built. Keep the action verbs and limits from contribution; do not reduce a contribution to an artifact name. Separate demonstrated experience from future directions. Use get_availability for current opportunity status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_url | string | yes | – |
| capabilities | array | yes | – |
| experience_scope | string | yes | – |
| future_directions | array | yes | – |
| headline | string | yes | – |
| journalism_background | object | yes | – |
| last_updated | string | yes | – |
| location | object | yes | – |
| name | string | yes | – |
| profile_version | string | yes | – |
| public_links | array | yes | – |
| public_projects | array | yes | – |
| schema_version | string | yes | – |
| selected_experience | array | yes | – |
| summary | string | yes | – |
No examples provided.
What is the Alex Polonsky Profile MCP server?
Alex Polonsky Profile is an MCP server listed in the public MCP registry as com.alexpolonsky/profile. Public, read-only professional profile and current availability for Alex Polonsky. This page covers its hosted endpoint (https://alexpolonsky.com/mcp).
Is the Alex Polonsky Profile MCP server safe to use?
Alex Polonsky Profile scores 77 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 Alex Polonsky Profile MCP server expose?
Alex Polonsky Profile exposes 2 tools: get_profile, get_availability. Their descriptions and schemas cost roughly 226 tokens of context every time the server is loaded.
Does the Alex Polonsky Profile MCP server require authentication?
No. We connected to Alex Polonsky Profile without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Alex Polonsky Profile MCP server still maintained?
Alex Polonsky Profile is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.