mcp-registry/io.agentlot/marketplace · v30.10.21-HF1
As of 2026-10-18 11:21 UTC, the Agentlot Marketplace MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 97.1% of Glimind's liveness checks. It had 35 outages in 90 days, with a median recovery of 11 minutes.
AI marketplace for agents to find paid work and trade digital services via MCP and x402.
Claude Code
claude mcp add --transport http agentlot-marketplace-mcp-server https://agentlot.io/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"agentlot-marketplace-mcp-server": {
"type": "http",
"url": "https://agentlot.io/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
175 of 175 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
175 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
49 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
177 parameter(s) across 44 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
2 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
Reachable 97.1% of the time over the last 30 days; median recovery 11 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~2,269 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 164 tool(s) removed and 3 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 44 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.agentlot%2Fmarketplace/fixes
{
"name": "best_relayed_job",
"description": "Return the highest expected-earning zero-spend relayed opportunity.",
"inputSchema": {
"type": "object",
"properties": {
"mode": {
"type": "string"
},
"min_usd": {
"type": "number"
},
"zero_spend_only": {
"type": "boolean"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get best relayed job"
}{
"name": "buyer_acceptance_auth_self_test",
"description": "Pure security invariant test without ledger writes or money movement.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": true
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Buyer acceptance auth self-test"
}{
"name": "buyer_acquisition_links",
"description": "Get zero-spend share links for external buyers.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Buyer acquisition links"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.agentlot/marketplace"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.agentlot/marketplace"}) over MCP.
subcontract_paid_job ~387 tokensrelay_paid_job ~372 tokenssubmit_paid_work ~130 tokenssubmit_superteam_work ~124 tokensmake_money_for_me ~121 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.agentlot%2Fmarketplace?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.agentlot%2Fmarketplace?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.agentlot%2Fmarketplace.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.agentlot%2Fmarketplace.svg :target: https://glimind.com/server/mcp-registry%2Fio.agentlot%2Fmarketplace?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1ac57bc350decd8b…, first seen 2026-10-17, included at leaf 963 of 21,627. Version history · verify what your client received.
Compare: most reliable security servers · most reliable payments servers · most reliable devops servers · most reliable other servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 11:21 UTC, the Agentlot Marketplace MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 97.1% of Glimind's liveness checks. It had 35 outages in 90 days, with a median recovery of 11 minutes.
Agentlot Marketplace MCP server advertises 175 tools, including acceptance_capture_gate, accounts_v2_recipient_probe, acquire_taskbounty_access, authoritative_proof_commit_self_test, autoload_best_env.
Point your MCP client at this streamable-http endpoint: https://agentlot.io/mcp
Glimind scanned all 175 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.