TalentLyft Ops Control Plane

Created By
Sam Vangelos15 hours ago
Paid-download MCP for asking TalentLyft recruiting-ops questions inside Claude, Cursor, or another MCP client.
Overview

Ask TalentLyft questions at recruiting-ops granularity: stale candidate applications by stage, candidate activity follow-up, job and requisition status movement, source quality, job-board visibility, disposition hygiene, and bottleneck owners. No dashboard build. No SQL.

Paid one-time download: https://samvangelos.gumroad.com/l/talentlyft-ops-control-plane

The package runs locally. Buyers bring their own TalentLyft API credentials. Not affiliated with, sponsored by, or endorsed by TalentLyft.

Server Config

{
  "mcpServers": {
    "talentlyft-ops-control-plane": {
      "command": "node",
      "args": [
        "<path-to-talentlyft-ops-control-plane-download>/dist/index.js"
      ],
      "env": {
        "TALENTLYFT_API_TOKEN": "<your_talentlyft_api_token>",
        "TALENTLYFT_COMPANY_ID": "<your_talentlyft_company_id>"
      }
    }
  }
}
Project Info
Created At
15 hours ago
Updated At
15 hours ago
Author Name
Sam Vangelos
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago