mcpField
Y
yutori-api-monitor

yutori-api-monitor

github.com/yutori-aiDevelopment25105 installsUpdated 4w ago
Repository

About yutori-api-monitor

A skill for setting up recurring monitoring of API or service changes with a scout. It structures checks for breaking changes, new features, limits, deprecations, and security updates, with an optional webhook for notifications.

Key features

  1. 01Structured API change queries
  2. 02Monitoring for breaking changes
  3. 03Tracking new features and limits
  4. 04Deprecation and security checks
  5. 0512-hour monitoring interval
  6. 06Optional webhook notifications

Use cases

  1. 01Watching an API for breaking changes
  2. 02Tracking service documentation updates
  3. 03Receiving notifications about monitored changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/yutori-ai/yutori-mcp --skill yutori-api-monitor

After installing, type/yutori-api-monitorin Claude Code to confirm it loaded.

Details

From the project README

API & Changelog Monitoring

Set up monitoring for API or service changes.

Create a scout with this query structure:

**Context:** Monitoring API stability and changes for $ARGUMENTS to ensure our integration stays up-to-date.

## What to Monitor
- **Breaking Changes:** API version changes, deprecated endpoints, removed features
- **New Features:** New endpoints, parameters, capabilities
- **Rate Limits & Quotas:** Changes to limits, pricing tier updates
- **Deprecation Notices:** Sunset timelines, migration guides
- **Security Updates:** Authentication changes, security advisories

**Sources to check:** Official changelog, documentation, developer blog, GitHub releases, status page, developer Twitter/X account

**Exclusions:** Minor bug fixes, internal refactoring, documentation typos

## Deliverables
**Frequency:** Every 12 hours

**Output format:**
1. **URGENT** section for breaking changes (if any)
2. Table of changes: Date, Type (breaking/feature/deprecation), Description, Migration Required (yes/no), Source Link
3. Recommended actions for each change

Use create_scout with:

  • query: The above structured query with $ARGUMENTS replaced
  • output_interval: 43200 (every 12 hours)

After creation, explain:

  • Scout will check twice daily for changes
  • Critical for staying ahead of breaking changes
  • Can set up webhook for immediate notifications

Fetching API documentation or changelogs: If you use a web fetch tool to look up the service's changelog, API reference, or developer docs while preparing the query, include the Accept: text/markdown header. Many developer documentation sites (Cloudflare-hosted) will return clean Markdown instead of HTML — fewer tokens, easier to parse.

Comments

Markdown supported