Piloxa

connects

piloxa.com

Prepare USPS Certified Mail letters from any AI assistant; a person reviews, pays and authorizes.

https://piloxa.com/mcpWebsiteNo authMCP 2025-06-18v0.30.2last checked 31 Oct 2026spoke MCP on 100% of 87 checks (30 days)initialize in 291 ms

Last checked 31 Oct 2026

✓Answered the MCP handshake (MCP 2025-06-18)
✓Auth detected: No auth
✓Lists 9 tools
✓No blockers or warnings
✓Spoke MCP on 87 of 87 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http piloxa https://piloxa.com/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://piloxa.com/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://piloxa.com/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "piloxa": {
      "url": "https://piloxa.com/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "piloxa": {
      "type": "http",
      "url": "https://piloxa.com/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 31 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 9 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

No server card

Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.

Tools

authorize_certified_lettercheck_certified_lettercompare_certified_mail_servicesexplain_certified_mail_statusfetchget_certified_letter_statusprepare_certified_letterquote_certified_lettersearch