Google Discover MCP Server and API by Cotlet
REMOTE · COTLET.DEV · 2 COMPONENTS
Google Discover personalized news feed MCP server: read Discover feed, check domain in feed.
Available components
Last scanned (13 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category News and Social
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cotlet_browser_click). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability59
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 6196 tokens (~193/item across 32 items; 30 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 32 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 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.
- 20 Nov 26 −3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cotlet_browser_type” rewrote its description, which is the text the model reads security
- Schema quality: 100% → 50% ▼ functional
- New resource “cotlet-refresh-button” functional
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 0
- Tool “cotlet_upload_file” rewrote its description, which is the text the model reads security
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 164 → 194 ▼ functional
- “cotlet_browser_hover” added an optional parameter “tab” cosmetic
- “cotlet_browser_navigate” added an optional parameter “tab” cosmetic
- “cotlet_browser_press” added an optional parameter “tab” cosmetic
- “cotlet_browser_screenshot” added an optional parameter “tab” cosmetic
- “cotlet_browser_scroll” added an optional parameter “tab” cosmetic
- “cotlet_browser_select” added an optional parameter “tab” cosmetic
- “cotlet_browser_type” added an optional parameter “tab” cosmetic
- “cotlet_browser_upload” added an optional parameter “tab” cosmetic
- “cotlet_browser_wait” added an optional parameter “tab” cosmetic
- “cotlet_browser_read” added an optional parameter “tab” cosmetic
- “cotlet_browser_click” added an optional parameter “tab” cosmetic
- “cotlet_browser_download” added an optional parameter “tab” cosmetic
- “cotlet_browser_drag” added an optional parameter “tab” cosmetic
- “cotlet_browser_evaluate” added an optional parameter “tab” cosmetic
- “cotlet_browser_fill_form” added an optional parameter “tab” cosmetic
- “cotlet_browser_find” added an optional parameter “tab” cosmetic
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cotlet_whoami” rewrote its description, which is the text the model reads security
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 21 Nov 2026 · Probed https://cotlet.dev/mcp/v1/google-discover
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cotlet.dev | CN=YE1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6afd7585ee8e24a40f5683c10835ec990a8 |
| SANs: *.cotlet.dev, cotlet.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of cotlet.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| cotlet.dev. | DS published | 2371 | 13 | Verified |
| cotlet.dev. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cotlet.dev/mcp/v1/google-discover | Verified | 200 | |
| http (plaintext) | http://cotlet.dev/mcp/v1/google-discover | HTTPS enforced | 301 | https://cotlet.dev/mcp/v1/google-discover |
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 →
check_domain_in_feed Check if a domain is in the Discover feed ~213
Whether cards from a domain are in a country's Discover feed now, and at which positions. Reads the same feed as get_discover_feed (signed out, from a home IP in the country) and keeps the cards whose link is on the domain or one of its subdomains. in_feed is false when none is there right now; feed_size says how many cards the feed held. Run it on a schedule to see when a story enters and leaves.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country of the feed, ISO 3166-1 alpha-2 (US, GB, DE, PL ...). The feed is read from a home IP there, so its stories are the ones Discover shows in that country. Default: US. |
| domain | string | yes | The site's domain, e.g. example-news.com. Its subdomains count too. |
| language | string | – | Language of the feed, BCP 47 (en-US, de-DE, pt-BR). Default: the country's main language. |
No output schema declared.
No examples provided.
collect_discover_cards Collect Discover cards ~294
Up to 300 different cards Discover shows in a country, from many reads, with how often each appeared. One read of the Discover feed holds about 31 cards, and each read draws them from a larger pool. This tool reads the feed of the country many times in parallel, each time from another home IP there, until it has the number of different cards asked for or the pool runs dry, and returns them at once. seen_in says in how many reads a card appeared (a card in most reads is the core of the feed, one seen once is rare) and best_position its highest place. Cards come most often seen first. complete is false when the feed held fewer different cards than asked for in the time of one call. A call takes up to about 70 seconds and costs more credits than one read, because it makes many.
| Name | Type | Req | Description |
|---|---|---|---|
| cards | integer | – | How many different cards to collect, at most 300. Default: 300. |
| country | string | – | Country of the feed, ISO 3166-1 alpha-2 (US, GB, DE, PL ...). The feed is read from a home IP there, so its stories are the ones Discover shows in that country. Default: US. |
| language | string | – | Language of the feed, BCP 47 (en-US, de-DE, pt-BR). Default: the country's main language. |
No output schema declared.
No examples provided.
cotlet_app_guide Cotlet: how to work in an app ~163
How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Google Discover it covers these actions: Read Discover feed, Check domain in feed.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | The app's name or Cotlet slug. Default: Google Discover. |
| task | string | – | What the user wants done in the app, in their words. |
No output schema declared.
No examples provided.
cotlet_apps Cotlet: apps I can use ~85
The apps of the user's workspace and whether each works now: the app account in the user's Cloud Browser (connected, signed out, signed in but not connected), and the one step the user has to take, with the console link. Free. Needs the user's Cotlet API key or sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Only this app, e.g. skool. |
No output schema declared.
No examples provided.
cotlet_browser_click Click on the page ~300
Clicks element `element`, or point `x`, `y` of the screenshot; `double` double-clicks, `button: right` right-clicks. Answers the page after it: the elements and text in view, with the same numbers. Says when nothing changed. A link that would open a new tab opens in this one. Buttons that pay or buy, and sign-in and account pages, are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| button | string | – | right opens the page's own context menu. Default: left. |
| dialog | string | – | How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog. |
| dialog_text | string | – | Text for a prompt dialog this step opens; implies accept. |
| double | boolean | – | Double-click. |
| element | integer | – | The element's number from the last read or step answer. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
| x | number | – | Instead of `element`: pixels from the left of the screenshot. |
| y | number | – | With `x`: pixels from the top of the screenshot. |
No output schema declared.
No examples provided.
cotlet_browser_close Close the browser ~43
Ends the browser session when the task is done: the browser keeps its cookies and sleeps, and the per-minute charge stops. Answers the session's minutes and credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cotlet_browser_download Download a file ~160
Gets the file that clicking `element` (a download link or button) or opening `url` starts, also an image or PDF it only opens: answers its name, type, size and a link valid 15 minutes; CSV, JSON and other text files also as text.
| Name | Type | Req | Description |
|---|---|---|---|
| element | integer | – | The element's number from the last read or step answer. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
| url | string | – | A public http or https address, e.g. https://example.com. |
No output schema declared.
No examples provided.
cotlet_browser_drag Drag on the page ~211
Drags from one element or point to another: a card between columns, a piece on a board, a slider's handle. Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| dialog | string | – | How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog. |
| dialog_text | string | – | Text for a prompt dialog this step opens; implies accept. |
| from | object | yes | An element number, or x and y of the screenshot. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
| to | object | yes | An element number, or x and y of the screenshot. |
No output schema declared.
No examples provided.
cotlet_browser_evaluate Run a script on the page ~165
Runs a JavaScript function body on the page and answers what it returns, as JSON. Use it to extract data the page holds (a table, a list, attributes); act with the other tools. It cannot send requests, click, submit, or read cookies or storage; a filled field's value reads [hidden by Cotlet]. Example: return [...document.querySelectorAll('h2')].map(h => h.innerText)
| Name | Type | Req | Description |
|---|---|---|---|
| script | string | yes | A function body that returns. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
No output schema declared.
No examples provided.
cotlet_browser_fill_form Fill in a form ~220
Fills several fields in one step: text fields take text, drop-downs an option's label, checkboxes, radios and switches true or false. Stops at the first field that fails and names those filled. Does not send the form: click its button after. Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| dialog | string | – | How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog. |
| dialog_text | string | – | Text for a prompt dialog this step opens; implies accept. |
| fields | array | yes | The fields in the order a person fills them. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
No output schema declared.
No examples provided.
cotlet_browser_find Find on the page ~141
Finds `text` on the whole current page, frames included: the elements whose label holds it, with their numbers, and each line of text that holds it. Use it instead of reading or scrolling a long page for one thing.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only elements of this kind. Default: any. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
| text | string | yes | Words to look for, any case. |
No output schema declared.
No examples provided.
cotlet_browser_hover Point at the page ~160
Rests the pointer on an element or a point, to open a hover menu, a tooltip or a preview. Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| element | integer | – | The element's number from the last read or step answer. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
| x | number | – | Instead of `element`: pixels from the left of the screenshot. |
| y | number | – | With `x`: pixels from the top of the screenshot. |
No output schema declared.
No examples provided.
cotlet_browser_navigate Go to a page ~200
Opens `url` in the current tab, or goes `history` back or forward. Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| dialog | string | – | How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog. |
| dialog_text | string | – | Text for a prompt dialog this step opens; implies accept. |
| history | string | – | Instead of `url`. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
| url | string | – | A public http or https address, e.g. https://example.com. |
No output schema declared.
No examples provided.
cotlet_browser_open Open the browser ~117
Starts the user's Google Discover Cloud Browser (a real Chrome on Cotlet, signed in to Google Discover as the user; use it for what the Google Discover tools do not cover) and opens `url`. Call it first. Only Google Discover pages open. Answers the page after it: the elements and text in view, with the same numbers. In Google Discover it serves these actions: Read Discover feed, Check domain in feed.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | – | A public http or https address, e.g. https://example.com. |
No output schema declared.
No examples provided.
cotlet_browser_press Press a key ~262
Presses a key on the focused element: Enter to send, Tab to the next field, Escape to close a pop-up, arrows in a list or slider, or one character (a site's shortcut). Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| dialog | string | – | How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog. |
| dialog_text | string | – | Text for a prompt dialog this step opens; implies accept. |
| key | string | yes | One of Enter, Tab, Shift+Tab, Escape, Backspace, Delete, Space, ArrowDown, ArrowUp, ArrowLeft, ArrowRight, PageDown, PageUp, Home, End, or one character such as a or 5. |
| repeat | integer | – | Times to press it. Default 1. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
No output schema declared.
No examples provided.
cotlet_browser_read Read the page ~154
The whole current page: its text (up to 20,000 characters) and a numbered list of its links, buttons, fields and other controls, open dialogs first. Use it on a new page or when a step's answer is not enough; `element` reads only inside one element (a dialog, a form, a list). Never returns field values, cookies or storage.
| Name | Type | Req | Description |
|---|---|---|---|
| element | integer | – | Read only inside this element. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
No output schema declared.
No examples provided.
cotlet_browser_screenshot See the page ~110
A JPEG of the visible part of the page. Use it for boards, canvases, maps, charts and layout that the text does not show, then click or drag by `x`, `y` of the image.
| Name | Type | Req | Description |
|---|---|---|---|
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
No output schema declared.
No examples provided.
cotlet_browser_scroll Scroll the page ~193
Scrolls with the mouse wheel: `down` or `up` by `screens`, to `top` or `bottom`, until `element` is in view, or inside a panel or list (`inside`). Content that loads on scroll appears. Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Default: down. |
| element | integer | – | Scroll until this element is in view. |
| inside | integer | – | Scroll inside this element, not the page. |
| screens | number | – | Viewport heights, for down and up. Default: 0.8. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
No output schema declared.
No examples provided.
cotlet_browser_select Choose from a list ~212
Chooses `option` (its label as listed, or its value) in drop-down `element`. For a home-made drop-down, click it, then click the option. Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| dialog | string | – | How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog. |
| dialog_text | string | – | Text for a prompt dialog this step opens; implies accept. |
| element | integer | yes | The element's number from the last read or step answer. |
| option | string | yes | The option. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
No output schema declared.
No examples provided.
cotlet_browser_type Type on the page ~334
Types `text` into field `element`, replacing what it held; `submit` presses Enter after it. For several fields use fill_form. Without `element` the text goes where the focus is, as a person types after clicking: for spreadsheet cells and editors that read does not number (Google Sheets, Docs), click the place first; there a tab in `text` presses Tab and a line break Enter, so one call fills a table. Answers the page after it: the elements and text in view, with the same numbers. A password or code the user gave you goes in like any text; card fields are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| dialog | string | – | How to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog. |
| dialog_text | string | – | Text for a prompt dialog this step opens; implies accept. |
| element | integer | – | The field's number from the last read. Leave it out to type where the focus is. |
| slowly | boolean | – | Key by key, for a search or address field whose suggestions do not appear. |
| submit | boolean | – | Press Enter after typing, e.g. to search. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
| text | string | yes | The text to type. |
No output schema declared.
No examples provided.
cotlet_browser_upload Upload a file ~158
Puts files into file field or upload button `element`: each file is {"url": "https://..."} or {"file_id": "..."} of a file uploaded to Cotlet; up to 10 files, 20 MB each. Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| element | integer | yes | The element's number from the last read or step answer. |
| files | array | yes | The files. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
No output schema declared.
No examples provided.
cotlet_browser_wait Wait for the page ~144
Waits until `text` shows on the page (at most `seconds`, default 5, up to 20), or just `seconds`: for results that load slowly. Says whether the text appeared. Answers the page after it: the elements and text in view, with the same numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| seconds | number | – | At most. |
| tab | string | – | The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on th… |
| text | string | – | Text to wait for. |
No output schema declared.
No examples provided.
cotlet_get_call Cotlet: check a call ~76
Status of an earlier Cotlet call, by its call_id: pending (waits for the owner's approval in the Cotlet console), approved, running, success, rejected, expired, blocked or failed. For a call that answered with status pending or running.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | call_id from the earlier call |
No output schema declared.
No examples provided.
cotlet_report_issue Cotlet: report a bug or a missing feature ~364
Sends a report to the Cotlet team: a tool that failed or returned wrong data, an error you could not get past, or a step the browser could not do, with the page, the step and what you saw. A missing dedicated tool is not a problem to report: do the task in the browser. A feature the user asks for goes as feature_request. A report promises nothing: tell the user it was sent, never that something will be built or fixed, or when. The report carries the error text and call_id when there is one, never passwords or tokens. Needs the user's Cotlet API key or sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| app | – | – | App slug the report is about, e.g. 'skool', or for a site in the web browser its host, e.g. 'app.example.com'. |
| call_id | – | – | call_id of the call that went wrong, if any. |
| client | – | – | Agent or tool sending this, e.g. 'Claude Code'. |
| description | string | yes | What the user asked for, what you tried, what you expected and what happened, with the error text if there was one. No passwords, tokens or other secrets. |
| kind | string | yes | bug: a tool did the wrong thing or returned wrong data. error: a call failed or returned an error you could not get past. feature_request: something new the user asked for. missing_feature: a step th… |
| title | string | yes | One line, e.g. 'skool_list_members stops after 50 members'. |
| tool | – | – | Tool or endpoint name, e.g. 'skool_list_members'. |
No output schema declared.
No examples provided.
cotlet_request_apps Cotlet: request access to apps ~170
Requests access to apps for the user's workspace, as Request access in the console: every app is granted at once. Not needed to work in an app: the user's AI works in any web app in their Web browser with cotlet_app_guide. An app with dedicated tools gets them after the user signs in to it in their Cloud Browser. Access says nothing about whether a task works there: check that in the browser. Takes app slugs as listed at https://cotlet.dev/api/v1/apps. Free. Needs the user's Cotlet API key or sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| apps | array | yes | App slugs, e.g. ["skool", "substack"]. |
| use_case | string | – | What the user wants the agent to do in these apps, in their words. |
No output schema declared.
No examples provided.
cotlet_upload_file Cotlet: upload a file for a tool ~125
Returns a one-time upload_url and a file_id for a local file (an image for a post, an attachment). The file is sent to upload_url with an HTTP PUT; an argument that takes a file accepts {"file_id": "..."}. Up to 25 MB, the URL takes one stored file (a failed PUT can be sent again). Free. Needs the user's Cotlet API key or sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | MIME type, e.g. image/jpeg. |
| name | string | – | File name, e.g. photo.jpg. |
No output schema declared.
No examples provided.
cotlet_whoami Cotlet: who am I ~80
The Cotlet account this connection acts as: email, workspace, access status, the API key or OAuth client in use with its scope, the apps the workspace may call, its credit balance, and the app the user signed up for with its first task and sign-in link. Free. Needs the user's Cotlet API key or sign-in.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_discover_feed Read the Discover feed ~263
The cards Google Discover shows right now in a country, in feed order, with no Google account. Returns the Discover feed Chrome for Android shows on its New Tab page to someone who is not signed in to Google, read from a home IP in the country asked for: position, title, publisher, URL, domain, article or video, age as the card shows it, and the card image. It is the default feed of that country and language, not anyone's personal feed and not data from a panel of users. One read holds about 30 cards; the feed changes over the day, and a read is reused for up to 15 minutes per country and language.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country of the feed, ISO 3166-1 alpha-2 (US, GB, DE, PL ...). The feed is read from a home IP there, so its stories are the ones Discover shows in that country. Default: US. |
| language | string | – | Language of the feed, BCP 47 (en-US, de-DE, pt-BR). Default: the country's main language. |
| limit | integer | – | How many cards to return, counted from the top of the feed. Default: all (about 30). |
No output schema declared.
No examples provided.
google_discover_check_domain_in_feed Check domain in feed in Google Discover ~99
Check domain in feed in the user's own Google Discover account from ChatGPT, Claude or any AI agent. Returns how to do it in Google Discover step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Google Discover Cloud Browser. Google Discover's official API: Google Discover has no API for the feed (checked 25 Oct 2026).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
google_discover_read_discover_feed Read Discover feed in Google Discover ~98
Read Discover feed in the user's own Google Discover account from ChatGPT, Claude or any AI agent. Returns how to do it in Google Discover step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Google Discover Cloud Browser. Google Discover's official API: Google Discover has no API for the feed (checked 25 Oct 2026).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Google Discover MCP Server and API by Cotlet server?
Google Discover MCP Server and API by Cotlet is a hosted endpoint at https://cotlet.dev/mcp/v1/google-discover, 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 · cotlet.dev
claude mcp add --transport http dev-cotlet-google-discover 'https://cotlet.dev/mcp/v1/google-discover'
What is the Google Discover MCP Server and API by Cotlet server?
Google Discover MCP Server and API by Cotlet is listed in the public MCP registry as dev.cotlet/google-discover. Google Discover personalized news feed MCP server: read Discover feed, check domain in feed. This page covers its hosted endpoint (https://cotlet.dev/mcp/v1/google-discover).
Is the Google Discover MCP Server and API by Cotlet server safe to use?
Google Discover MCP Server and API by Cotlet scores 71 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 Google Discover MCP Server and API by Cotlet server expose?
Google Discover MCP Server and API by Cotlet exposes 30 tools: cotlet_whoami, cotlet_apps, cotlet_request_apps, cotlet_get_call, cotlet_upload_file, and 25 more. Their descriptions and schemas cost roughly 5,314 tokens of context every time the server is loaded.
Does the Google Discover MCP Server and API by Cotlet server require authentication?
No. We connected to Google Discover MCP Server and API by Cotlet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Google Discover MCP Server and API by Cotlet server still maintained?
Google Discover MCP Server and API by Cotlet is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Google Discover MCP Server and API by Cotlet server?
VerifyMCP ran 13 checks on Google Discover MCP Server and API by Cotlet, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.