agentView
warningsagentview.de
Display delivery platform for AI agents. Push HTML, dashboards and live data to screens.
https://agentview.de/mcpWebsiteOAuthMCP 2025-11-25v2.1.119last checked 24 Aug 2026spoke MCP on 4 of 4 checks (30 days)initialize in 324 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://agentview.de |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required. |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Scopes | mcp:content, offline_access, openid, profile, email |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 57 tools listable |
| Credentials demanded in prose | ✕list_data_slots, create_api_key, get_data_slot, get_storage_usage, get_public_status, list_store_categories, delete_data_slot, get_license_info, upload_asset, search_public_apis, clear_display, get_account, delete_asset, get_store_template_content, search_store_templates, get_store_template_details, list_api_keys, list_organizations, revoke_api_key, list_display_categories, update_asset, create_organization, get_asset, fetch, test_display_content These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
| Documentation | https://agentview.de/developers.html |
What the probe found
25 of the 57 tools listed anonymously say in their own descriptions that they need an account or a key (list_data_slots, create_api_key, get_data_slot, get_storage_usage, get_public_status, list_store_categories, delete_data_slot, get_license_info, upload_asset, search_public_apis, clear_display, get_account, delete_asset, get_store_template_content, search_store_templates, get_store_template_details, list_api_keys, list_organizations, revoke_api_key, list_display_categories, update_asset, create_organization, get_asset, fetch, test_display_content), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
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.
The server exposes a public surface before authorization: assign_display_categories, list_data_slots, set_display_grant, authenticate, create_api_key, get_data_slot, get_storage_usage, broadcast_content, manage_licenses, get_public_status, get_display, create_auth_session, list_store_categories, send_store_template_to_display, create_display, delete_data_slot, get_license_info, get_organization, remove_display_from_org, set_data_slot, submit_feedback, upload_asset, configure_display, search_public_apis, claim_display, send_url, clear_display, get_account, delete_asset, get_store_template_content, get_auth_session, send_html, delete_display, logout, search_store_templates, search, pair_by_code, get_store_template_details, list_displays, list_assets, get_agent_artifact, configure_organization, list_api_keys, read_display_html, list_organizations, revoke_api_key, get_display_preview_url, delete_organization, list_display_categories, update_asset, create_organization, get_asset, fetch, manage_display_category, test_display_content, get_store_template_install_options, manage_org_member.
Tools
Contract history
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.
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.
[](https://mcpi.app/servers/agentview)Own this server?
Sign in to claim this listing by proving control of the endpoint.