← All servers

picoads

warnings

picoads.xyz

Micro ad network for AI agents.

https://picoads.xyz/mcpOAuthMCP 2025-11-25v1.0.0last checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 553 ms

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 CodeNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude Code docs · read on 2026-08-30

Claude (claude.ai & Desktop)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

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

ChatGPTNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

ChatGPT docs · read on 2026-08-30

CursorNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Cursor docs · read on 2026-08-30

VS Code (Copilot)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

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

How to authenticate

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

Scheme
OAuth
Issuer
https://picoads.xyz
Dynamic client registration
Advertised (RFC 7591)
Client ID Metadata Document
Not advertised
PKCE
None advertised

MCP requires S256; a client that implements only that has no method in common with this server.

Grant types
urn:picoads:agent-registration
Scopes
read, write
Protected-resource metadata
Published (RFC 9728)
Anonymous access
Handshake succeeds; 6 tools listable
Documentation
https://picoads.xyz/llms.txt

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.

6 tools usable without signing in

The server exposes a public surface before authorization: get_recommendations, monetize_link, register_agent, complete_registration, check_publisher_stats, leave_feedback.

Tools

check_publisher_statscomplete_registrationget_recommendationsleave_feedbackmonetize_linkregister_agent

Contract history

2 Sep 2026v1.0.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for picoads
[![MCP status](https://mcpi.app/servers/picoads/badge.svg)](https://mcpi.app/servers/picoads)