framefetch
https://server.smithery.ai/@reyd8777/framefetch ↗
Description
# FrameFetch **One API/MCP call gives an agent clean video data across 6 platforms** — metadata + insights, a Whisper transcript, and parametric frames (pick fps or exact timestamps → pushed to S3). YouTube (incl. Shorts), TikTok, Reddit, Instagram, Pinterest. Agent-first: typed errors, refund-on-fail, result caching. Pay per call via x402 (USDC on Base) or Stripe. ## Endpoints - POST /v1/extract — any combination of metadata/insights/transcript/frames in one call - POST /v1/metadata · /v1/transcript · /v1/frames — shortcuts - GET /v1/platforms — capability matrix · POST /v1/keys — free key + credit ## Example curl -X POST https://framefetch.net/v1/extract -H "Authorization: Bearer <key>" -H "Content-Type: application/json" -d '{"url":"https://youtu.be/...","fields":["metadata","transcript"]}' https://framefetch.net
What our measurements say
framefetch is a remote MCP server published at server.smithery.ai. Its tool list could not be read; the server is closed to direct calls.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Agent readability score
Event narrative
Sign up free to generateRaw observations
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list not measurable
- inputSchema not measurable
- Smoke test not run this round
- Cold-start not measurable (no handshake)
Availability history
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Era history
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
No era measurements yet.
Response time history
The two probe legs separately: modern server/discover and legacy initialize.
No response-time measurements yet.
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/reyd8777-framefetch)<a href="https://mcpmetrics.io/servers/reyd8777-framefetch"><img src="https://mcpmetrics.io/badge/reyd8777/framefetch/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeSimilar MCP servers
The catalog entries whose name and description are closest to this one, found with the same index the search box uses.
- Content-Type token shapeagent-observatory-sensor.nolimit-observatory.workers.dev
Content-Type token shape
- application/json markeragent-observatory-sensor.nolimit-observatory.workers.dev
application/json marker
- Agent Reserve Protocol Authorization Firewallagent-reserve-protocol.super-myna-7255.chatgpt.site
Advisory policy preflight for AI-agent spend requests; never executes payments or accesses wallets.
- IntentFence Agent Action Firewallagentpass-protocol.rmalka06.chatgpt.site
Fail-closed action authorization, MCP risk scanning, x402 checks, and signed receipts.
- Rostro Image, Video, 3D, Voice, SFX, Musicmcp.rostro.dev
Turn any language model into a multimodal powerhouse that can generate images, music, videos and more on the fly. Rostro's tools are designed to be used by language models from the ground up, expanding capabilities with minimal context bloat. ## Quick Setup You will need a [Rostro account](https://rostro.dev/login/sign_up) for OAuth discovery and authentication in your client of choice. **MCP Server URL:** `https://proto.rostro.dev/mcp` ## Quick Install Links - **Cursor**: [Install in Cursor](https://cursor.com/en/install-mcp?name=Rostro&config=eyJ1cmwiOiJodHRwczovL3Byb3RvLnJvc3Ryby5kZXYvbWNwIiwiaGVhZGVycyI6e319) - **LM Studio**: [Install in LM Studio](https://lmstudio.ai/install-mcp?name=rostro&config=eyJ1cmwiOiJodHRwczovL3Byb3RvLnJvc3Ryby5kZXYvbWNwIn0%3D) ## API Key Setup (Optional) For fixed API authentication instead of OAuth, add this to your settings: ```json "rostro": { "url": "https://proto.rostro.dev/mcp", "headers": { "Authorization": "Bearer <YOUR_API
- Meteomaticsmcp.meteomatics.com
The Meteomatics MCP (Model Context Protocol) server allows AI agents to securely access Meteomatics weather data tools. MCP is an open standard that lets AI applications connect to external tools and data sources. With the Meteomatics MCP, agents can request weather data directly from the Meteomatics API through a secure /mcp endpoint. The MCP server manages authentication using OAuth (client registration, authorization code + PKCE, and refresh tokens). Once connected, the AI agent can access data, models, parameters, time ranges that are available to your Meteomatics API account.
Comments
Sign in to write a comment
No comments yet. Be the first.