Yutori MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_api_usageA | Get API usage statistics including active scout counts, rate limits, and activity metrics. |
| list_scoutsA | List all scouts for the authenticated user. Returns basic metadata; use get_scout_detail for full fields. |
| get_scout_detailA | Get detailed information about a specific scout. |
| get_scout_updatesA | Get paginated updates/reports for a scout. Each update contains findings from a run. |
| create_scoutB | Create a monitoring scout for continuous web monitoring. Scouts track changes relevant to a query and alert you. Examples: 'news about Yutori', 'H100 pricing below $1.50'. |
| edit_scoutA | Update an existing scout's query, schedule, webhook configuration, or status. Use status='paused' to pause, 'active' to resume, or 'done' to archive. |
| delete_scoutA | Permanently delete a scout and all its data. This action cannot be undone. |
| run_browsing_taskC | Execute a one-time web browsing task. The navigator agent runs a browser and operates it like a person. Returns a task_id for polling. Example: 'list employees'. Set browser='local' to use the desktop app with the user's logged-in sessions. |
| list_browsing_tasksA | List one-time browsing tasks for the authenticated user. Supports cursor pagination and status filtering. List status is approximate (running also covers queued and not-yet-reconciled tasks); call get_browsing_task_result for a task's authoritative status. |
| get_browsing_task_resultA | Poll for browsing task status and result. Call until status is 'succeeded' or 'failed'. |
| run_research_taskB | Execute a one-time deep web research task. The research agent searches, reads, and synthesizes information from across the web. Returns a task_id for polling. Example: 'latest AI startup funding announcements'. |
| list_research_tasksA | List one-time research tasks for the authenticated user. Supports cursor pagination and status filtering. List status is approximate (running also covers queued and not-yet-reconciled tasks); call get_research_task_result for a task's authoritative status. |
| get_research_task_resultA | Poll for research task status and result. Call until status is 'succeeded' or 'failed'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Tools are clearly separated into scout and task domains, each with distinct operations. No overlapping functionality between tools.
All tools follow a consistent verb_noun pattern in snake_case, e.g., create_scout, get_scout_detail, list_browsing_tasks.
13 tools cover two main areas (scouts and tasks) plus API usage, which is well-scoped for the server's purpose.
Scouts have full CRUD plus updates. Tasks lack delete/cancel operations, which is a minor gap for one-time tasks.