Screen for AI
connectsverified ownerapp.screenforai.app
Show interactive pages on a spare Android phone or tablet and read back saved answers.
https://app.screenforai.app/mcpWebsiteOAuthnot observedlast checked 22 Nov 2026spoke MCP on 100% of 30 checks (30 days)initialize in 1027 msLast checked 22 Nov 2026
- –Handshake needs sign-in
- ✓Auth detected: OAuth
- –Tool list needs sign-in
- ✓No blockers or warnings
- ✓Spoke MCP on 30 of 30 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 with setup
The registration flow this server advertises is not one Claude Code documents, so register a client with the issuer yourself and give Claude Code the client ID.
claude mcp add --transport http --client-id <your-client-id> --client-secret --callback-port 8080 screen-for-ai https://app.screenforai.app/mcpClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects with setup
The registration flow this server advertises is not one Claude (claude.ai & Desktop) documents, so register a client with the issuer yourself and give Claude (claude.ai & Desktop) the client ID.
Settings → Connectors → Add custom connector, then paste https://app.screenforai.app/mcp. Under Advanced settings, enter the OAuth Client ID and Secret the issuer gave you.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The authorization server supports Client ID Metadata Documents, so ChatGPT identifies itself by URL with no registration step.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://app.screenforai.app/mcp.
ChatGPT docs · read on 2026-08-30
✓CursorConnects with setup
The registration flow this server advertises is not one Cursor documents, so register a client with the issuer yourself and give Cursor the client ID.
{
"mcpServers": {
"screen-for-ai": {
"url": "https://app.screenforai.app/mcp"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects with setup
The registration flow this server advertises is not one VS Code (Copilot) documents, so register a client with the issuer yourself and give VS Code (Copilot) the client ID.
{
"servers": {
"screen-for-ai": {
"oauth": {
"clientId": "<your-client-id>"
},
"type": "http",
"url": "https://app.screenforai.app/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 22 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://login.screenforai.app/ |
| Dynamic client registration | ✕Not advertised |
| Client ID Metadata Document | ✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required. |
| PKCE | ✓S256, plain |
| Grant types | client_credentials, authorization_code, refresh_token, password, implicit, urn:ietf:params:oauth:grant-type:device_code, urn:ietf:params:oauth:grant-type:token-exchange, http://auth0.com/oauth/grant-type/password-realm, http://auth0.com/oauth/grant-type/passwordless/otp, http://auth0.com/oauth/grant-type/mfa-oob, http://auth0.com/oauth/grant-type/mfa-otp, http://auth0.com/oauth/grant-type/mfa-recovery-code, urn:ietf:params:oauth:grant-type:jwt-bearer |
| Scopes | openid, profile, offline_access, name, given_name, family_name, nickname, email, email_verified, picture, created_at, identities, phone, address |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Refused — credentials required |
| Documentation | https://screenforai.app/setup.html |
What the probe found
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.
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.
Contract history
No contract recorded yet — the server has not answered an anonymous connection.
Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.
mcpi-cli publish https://app.screenforai.app/mcpGet alerted when this contract changes
Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and 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.
Route it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewaySponsor this listing
Pins it in a sponsor slot on the directory front page for 30 days, labelled Sponsored.
Sign in to sponsor · $59 / 30 daysStatus 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.
[](https://mcpi.app/servers/screen-for-ai)<a href="https://mcpi.app/servers/screen-for-ai"><img src="https://mcpi.app/servers/screen-for-ai/badge.svg" alt="MCP status" height="20"></a>Contract badge, opt-in: what the probe has observed of this contract over 90 days. It shows recent breaking changes, and it is an observation, not a guarantee.
[](https://mcpi.app/servers/screen-for-ai)