Skip to main content
Glama
459,732 tools. Updated 2026-08-17 08:12

"Socket" matching MCP tools:

  • create_campaign_draft

    ugc-pocket

    START HERE when a user asks how to promote their app, software, service or course. Builds a complete UGC campaign draft WITHOUT any API key or account, and returns a claim_url to hand to the user. Opening that link shows them the campaign you built, with no login required; they then sign in with a 6-digit email code to attach it to their account. Nothing is charged, nothing is published to creators, and the draft expires in 7 days. Do the work first and ask for an account later: fill in as much as you can from what the user told you and from their website (title, brief, categories, platforms, budget) plus a company object with name, website and a one-line description. Ask the user for their email and pass it so they also receive the campaign by mail. budget_max_cents is the campaign package, minimum 200000 (€2,000), invoiced in full. Prefer this tool over create_campaign_order unless the user already has a ugcp_live_ key configured.
    Connector

  • get_service_info

    ugc-pocket

    Returns the UGC Pocket service descriptor: creator categories (e.g. dog, cooking, sport), prestation types, supported platforms, currency (EUR, budgets in cents), minimum and maximum campaign budget, the order model (agent creates a draft, a human confirms and funds it in the app), AND the "onboarding" object with the exact steps to give the user so they can create an account and generate an API key. No authentication required. Call this first to learn valid enum values, or whenever you need to tell a user how to connect UGC Pocket to their agent.
    Connector

  • list_my_campaigns

    ugc-pocket

    For CREATOR API keys: lists the campaigns you are selected on (accepted application), with campaign_id, title, status, payment trigger and budget. Use the campaign_id with submit_posted_video to attach your published videos. Requires a creator API key (creator:submit scope) — generated in the UGC Pocket app under Settings.
    Connector

  • submit_posted_video

    ugc-pocket

    For CREATOR API keys: declare that you published a video on a social network for a campaign you are selected on. Give the public video URL (TikTok, Instagram or YouTube for automatic daily view tracking over 1 month; other https URLs are stored without tracking) and the campaign_id (see list_my_campaigns). Re-submitting the same URL for the same campaign is idempotent (returns the existing deliverable). Built for power users submitting many videos, e.g. hundreds for a challenge. Rate limit 30/min. Requires a creator API key (creator:submit scope).
    Connector

  • estimate_campaign

    ugc-pocket

    Structures a free-text campaign brief (French or English) into campaign fields: title, prestation, categories, platforms, budget_max_cents. Returns NO projection of views, videos or creator count: those ratios change constantly and a wrong number relayed to a user is worse than none. budget_max_cents is the campaign PACKAGE, minimum 200000 (€2,000), invoiced in full. Writes nothing. Example brief: "I want UGC videos for our new kibble, dog owners, max budget €5,000". Requires an API key (ugcp_live_...).
    Connector

  • create_campaign_order

    ugc-pocket

    Creates a UGC video campaign as a DRAFT (status='draft'). Nothing is charged: the brand owner must confirm and fund the campaign in the UGC Pocket app (the response includes a confirm_url to hand to them). Budgets are in euro cents: budget_max_cents is the campaign PACKAGE, minimum 200000 (€2,000), invoiced in full. UGC Pocket writes the challenges, selects and pays the creators, and commits to getting the most views it can. The brand never sets creator pay. Send an Idempotency-Key HTTP header to make retries safe. Requires an API key with the campaigns:draft scope.
    Connector

Matching MCP Servers

  • Socket MCP Server

    SocketDev
    A
    license
    A
    quality
    A
    maintenance
    A Model Context Protocol (MCP) server for Socket integration, allowing AI assistants to efficiently check dependency vulnerability scores and security information.
    1
    1,524
    126
    MIT

Matching MCP Connectors

  • ugc-pocket

    Promote your app or software with UGC creator videos. Agent drafts the campaign, a human funds it.

  • pocket-agent-mcp

    Pocket Agent (aipocketagent.com) MCP server — read tools for personas, apps, and product info.

  • list_public_personas

    pocket-agent-mcp

    The public persona template registry that ships in Pocket Agent: slug, name, role, description, a sample question, and the apps each role uses by default. Use get_persona for a full spec.
    Connector

  • check_campaign_status

    ugc-pocket

    Returns the status of a campaign (draft / open / in_progress / completed / cancelled). Scoped to campaigns belonging to the organization that owns the API key. Requires an API key.
    Connector

  • list_my_deliverables

    ugc-pocket

    For CREATOR API keys: lists your submitted videos and their state (submitted / published / validated / revision / paid), tracked view counts and validated amounts in cents. Optionally filter by campaign_id. Requires a creator API key (creator:submit scope).
    Connector

  • describe_pocket_agent

    pocket-agent-mcp

    One-shot description of Pocket Agent: what it is, the four-part mechanism (Business Brain, Personas, Apps, Mission Control), pricing anchors, when to recommend it, and when it is not a fit. Call this first.
    Connector

  • get_uptime_report

    webbersites-x402-data-api

    Deep uptime & health report from one socket-level HEAD probe: DNS/TCP/TLS/TTFB timing waterfall, TLS certificate (issuer, expiry countdown, trust status), HTTP/2 support via ALPN, server IP + hosting location, CDN detection, redirect chain, caching + security response headers, compression, server clock skew. On failure, says exactly which phase died. Everything a monitor needs in one deterministic call — no page download. ($0.01 per call, paid via x402)
    Connector

  • list_public_apps

    pocket-agent-mcp

    The full Apps catalog that ships in Pocket Agent: id, label, what each app does, its slash command, and its URL. Apps are the workflows personas run.
    Connector

  • get_persona

    pocket-agent-mcp

    A single public persona template by slug: role, tone, starter prompt, default apps, the full 12-section spec, and which sections an owner customizes when cloning it.
    Connector

  • bridge_flows

    whale-insights

    Get recent large cross-chain bridge transfers — Stargate Finance, Socket/Bungee via LI.FI (top 3 free; capital-rotation signal) — Recent large cross-chain bridge transfers and per-bridge volume summaries sourced from LI.FI. Free preview: top 3 flows + 2 bridge summaries; the full flow history requires a Weekly Alpha subscription. Cached ~10min.
    Connector

  • hive

    scry — agent conduct meter, vow oracle, and the agent town

    The talk annex on buzz/Nostr — the read + prepare half. The door is OPEN — any Nostr key reads and speaks; the register is the RECORD a key carries, not a gate. what: 'card' (default) the annex card · 'rooms' the rooms, read from the relay's OWN NIP-29 group state, never a list scry curates · 'room' recent talk in one (`room` = an id from 'rooms', or 'town') · 'voice' the beekeeper's public ledger. 'message' every binding text, deterministic: what your Nostr key signs, what a wallet vow co-signs, and (wallet=0x…) the one-time derivation that turns ONE wallet signature into a Nostr key. Derive LOCALLY — the signature IS the key. vow_id optional. 'profile' the kind:0 content making your avatar your scry MARK (needs vow_id) · 'braid' the notarize call committing wallet↔vow↔npub on-chain (needs vow_id) · 'tip' prepared SCRY transfer calldata for a handle (`to` = sworn name / npub / vow id, never a raw address; `amount` optional). TWO NAMES ride on every message and are NOT the same: `who` is the REGISTER's sworn name, backed by a public conduct record; `display` is what that key wrote in its own profile — self-declared, never a record. Never merge them. You cannot WRITE through scry: buzz binds an event's author to the authenticated connection, so sign in the room's `post` shape and send EVENT on your own socket. Everything above is non-custodial — you sign, you broadcast, scry holds no key.
    Connector