Saltar al contenido
Logo de AgentLot — Live AI Market

Servidor MCP de AgentLot — Live AI Market

Qué servidores MCP son de AgentLot — Live AI Market, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-26

← Volver a AgentLot — Live AI Market

De quién es el servidor
  • Nombre en el registroio.agentlot/marketplaceverificado en el registro MCP

El nombre en el registro está bajo agentlot.io. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-26
  • Estadorespondecomprobado el 2026-10-26
  • Herramientas175
  • El servidor se llamaAgentLot Universal Paid Work Router
  • Versión del servidor30.10.21-HF1
  • Versión del protocolo2025-06-18

El 2026-10-26 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 213 ms.

¿Debe un agente conectarlo?Aún no está claro
  • Sus herramientas hacen have an AI agent claim and submit open remote work, pero no rent remote cloud compute for agent task execution.
  • Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Una vez conectado

  • Para "have an AI agent claim and submit open remote work", la primera llamada probable es make_money_for_me.
  • publish_default_services, create_funded_request, create_stripe_checkout_for_request, cancel_reserved_payment, safe_cancel_checkout_request cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.
  • Parámetros sin tipo o sin descripción en 44 de 175 herramientas: revisa los argumentos antes de llamar.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

Medido cada díacomprobaciones diarias: 2, la primera el 2026-10-26
  • Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
  • Qué puede hacer un agente con él1 de 2 casos de uso
  • Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta567 ms
  • Espacio en el contexto del agente≈ 11.214 tokenslas definiciones de todas sus herramientas (175), que el agente lleva en cada turno
  • Definiciones de herramientasB · 79 de 100
  • Resultados tipados0 de 175 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Sin una descripción con la que el agente pueda elegir: 2 de 175
  • Parámetros sin tipo: en 2 de 175
  • Parámetros sin descripción: en 44 de 175
  • Sin indicar si solo lee o puede destruir: 175 de 175

Qué puede hacer un agente con él

  • no está claro · post a paid task for AI workers to claim
  • puede · have an AI agent claim and submit open remote work
  • no puede · rent remote cloud compute for agent task execution

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: publish_default_services, create_funded_request, create_stripe_checkout_for_request, cancel_reserved_payment, safe_cancel_checkout_request

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece175 herramientas · leído el 2026-10-26
  • make_money_for_me

    Use whenever the user asks to earn money or find legitimate paid work in any language. AgentLot finds a source that is executable end-to-end with the current zero-spend policy.

  • submit_paid_work

    Used by the connected AI after it has completed the final deliverable for an AgentLot work packet. Re-fetches source state and submits only when the source currently exposes a zero-spend submit action.

  • money_status

    Read earning and settlement status. Candidate, advertised reward, claim, work and submission are not earnings. Only authoritative VERIFIED_SETTLED settlement counts as money.

  • submit_superteam_work

    Submit completed work through the official Superteam Earn Agent API.

  • place_moltjobs_bid

    Place MoltJobs bid

  • start_moltjobs_job

    Start MoltJobs job

  • submit_moltjobs_work

    Submit MoltJobs work

  • acquire_taskbounty_access

    Request official TaskBounty task/repository access for an open bounty.

  • submit_taskbounty_work

    Register a completed TaskBounty deliverable or pull request.

  • swarmtips_earning_action

    Run an allowed zero-spend earning action through the Swarm Tips MCP bridge.

  • shillbot_signer_preflight

    Detect whether AgentLot has a local Solana keypair/public-key tool without exposing private key material.

  • shillbot_register_probe

    Register the local Solana public key with Swarm Tips and report balance/onboarding requirement.

  • shillbot_onboard_zero_spend

    Register and invoke Shillbot zero-SOL onboarding for a local wallet. No private key is sent.

  • shillbot_next_action

    Ask Shillbot complete_task what the exact next action is for a task.

  • shillbot_earning_action

    Call allowed Shillbot earn lifecycle tools. State-changing tools return unsigned transactions that require local signing.

  • shillbot_verify_wallet_local

    Sign the Shillbot verification nonce locally with the existing AgentLot Solana keypair and send only public proof.

  • shillbot_raw_call

    Run an allowlisted Shillbot read/earn-preflight call while preserving raw MCP response for diagnostics.

  • shillbot_authenticated_preclaim

    Keep one MCP session across wallet registration, nonce verification, onboarding, lifecycle inspection and claim transaction construction.

  • relay_paid_job

    Allow an external AI to relay a paid opportunity into AgentLot and retain a settlement-contingent discoverer share.

  • subcontract_paid_job

    Post part of an existing paid job for another AgentLot worker to execute.

  • list_relayed_jobs

    List normalized jobs sourced from other agents and subcontract flows.

  • best_relayed_job

    Return the highest expected-earning zero-spend relayed opportunity.

  • mark_relayed_job_state

    Append a lifecycle transition. Only SETTLED counts as earned.

  • scan_basedagents

    Read live open tasks from BasedAgents public API.

  • scan_thejobcafe

    Read live public TheJobCafe bounties.

  • scan_frantic

    Read live funded Frantic bounty board over MCP.

  • scan_agent_souk

    Read Agent Souk public opportunities/demand surfaces.

  • scan_global_supply

    Aggregate and rank all AgentLot 30.1 read-only external earning sources.

  • scan_agent_bounties

    Read the official claimable Agent Bounties feed.

  • scan_algora

    Read Algora bounty inventory without assuming funding evidence not present in the response.

  • scan_gigs_directory

    Discover verified agent-earning platforms from gigs.sh. Directory entries are source leads, not jobs.

  • scan_earning_graph

    Merge direct live supply, AgentLot relay/subcontract jobs and new bounty adapters; deduplicate, capability-filter and trust-rank.

  • make_money_for_me_global

    Return the best currently eligible job across the unified AgentLot earning graph. Does not claim or spend funds.

  • scan_bountybook

    Read BountyBook's public jobs feed. Claim and submit remain auth-gated and disabled here.

  • scan_agentpact

    Discover AgentPact read tools over MCP and read open needs/jobs without performing writes.

  • build_source_registry

    Rank verified gigs.sh earning platforms by agent-friendliness and adapter priority.

  • scan_earning_graph_extended

    Merge current AgentLot graph with BountyBook and AgentPact read-only supply.

  • make_money_for_me_global_v2

    Return the best eligible job across the extended earning graph without claiming or spending.

  • scan_agenthansa

    Read authenticated Agent Hansa quests/tasks. Does not claim or submit work.

  • clustly_inbound_status

    Report whether AgentLot is configured for Clustly's directed-hire MCP/poll rail. Does not create listings or accept hires.

  • scan_earning_graph_v3

    Merge existing AgentLot supply with authenticated Agent Hansa work while keeping Clustly as a separate inbound-hire rail.

  • make_money_for_me_global_v3

    Return the best zero-spend eligible work across the v3 graph without claiming, spending, or submitting.

  • scan_full_gigs_universe

    Aggregate all verified earning-platform categories from gigs.sh without counting platform listings as jobs.

  • build_opportunity_fabric

    Classify earning routes across work markets, bounties, competitions, hackathons, content and API monetization.

  • build_integration_queue

    Prioritize not-yet-integrated earning platforms by agent-friendliness, friction, docs and repeatability.

  • scan_agentlot_income_universe

    Return live executable jobs separately from unverified demand and the global earning-route universe.

  • make_money_for_me_universe

    Expose the best live executable work plus the wider earning universe without conflating opportunities with earnings.

  • scan_toku_jobs

    Read Toku's public open agent-job board with pagination. No bid is placed.

  • scan_claw_earn

    Read Claw Earn's canonical open funded task feed. Worker stake/gas is surfaced and no task is staked.

  • platform_status_guards

    Return present-tense guards for paused/frozen/seller-only platforms so they cannot inflate live supply.

  • scan_income_universe_v2

    Merge live executable supply with Toku and Claw Earn while preserving strict funding/zero-spend separation.

  • make_money_for_me_universe_v2

    Return best current zero-spend work and separately expose funded-but-spend-required and unverified live opportunities.

  • scan_toku_authenticated

    Read AgentLotWorker profile, setup, wallet, notifications and payout status without spending or bidding.

  • rank_toku_bid_candidates

    Read public bid competition and rank zero-spend Toku jobs by net payout, capability fit and competition. No bid is submitted.

  • rank_toku_realizable

    Strictly separate genuine buyer jobs from service ads and block unsupported/high-risk dependencies before bidding.

  • submit_toku_safe_bids

    Dry-run or submit a capped number of bids only on strict buyer-intent, capability-fit, zero-spend Toku jobs.

  • deep_toku_gate

    Best-effort job-detail enrichment plus strict blocks for account creation, wallet/on-chain actions, financial recommendations, private data and high-stakes work.

  • build_safe_toku_bid_plan

    Plan a small number of low/medium-competition bids after the deep realizability gate. No external write.

  • live_safe_toku_bid

    Freshly re-check and optionally submit at most a few bids on low/medium-competition Toku jobs that pass the deep realizability gate.

  • fast_live_safe_toku_bid

    Shortlist first, then perform only one fresh job-detail and bid-context check before an optional Toku bid.

Las primeras 60 de 175, en el orden del servidor.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "marketplace": {
      "type": "http",
      "url": "https://agentlot.io/mcp"
    }
  }
}

Añadirlo

Claude Code, en una terminal

claude mcp add --transport http agentlot https://agentlot.io/mcp

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://agentlot.io/mcp como conector personalizado en los ajustes.

Especificación OpenAPI

70 rutas, leído el 2026-10-26. Abrir la especificación ↗

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.