Skip to main content
Glama

Lamdis Exchange

by ai.lamdis
OverviewDiscussionsAdmin

Server Details

Pay people nearby for physical work: find out if something is true, or have it done.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
45.3% over 22 days
Last Tested
Transport
Streamable HTTP
URL
Repository
lamdis-ai/lamdis-protocol
GitHub Stars
0

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation4/5

Tools target mostly distinct actions: feasibility checking, physical-world execution, physical-world observation, information gathering, and job/bid/receipt retrieval. However, do_in_world, observe_world, and find_out share the same paid-job posting mechanics and could be confused without reading the descriptions closely.

Naming Consistency3/5

All names are snake_case and readable, but the set mixes action-oriented names (check_feasible, do_in_world, find_out, observe_world, list_bids) with resource-oriented names (job_evidence, job_receipt, job_status). There is no single predictable verb_noun pattern.

Tool Count5/5

Eight tools is well-scoped for a physical-task exchange, covering feasibility, task creation, information gathering, bids, status, evidence, and receipts. Each tool appears to earn its place without obvious redundancy.

Completeness3/5

The surface covers feasibility, posting, bids, status, evidence, and receipts, but lacks explicit bid acceptance/awarding, cancellation/refund/dispute handling, and account or balance inspection. These are notable gaps for a bidding-based exchange workflow.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changeddo_in_world1 field changed
      • addedInput schema / properties / x402
        Added value: +{
+  "description": "pay inline with a USDC wallet on Base instead of a pay link: the reply is then the x402 payment requirements (HTTP 402); retry the same POST /v1/tasks with a signed X-PAYMENT header and the job lists in that round trip. Only for an agent holding the wallet; never set it otherwise",
+  "type": "boolean"
+}
    • Changedobserve_world1 field changed
      • addedInput schema / properties / x402
        Added value: +{
+  "description": "pay inline with a USDC wallet on Base instead of a pay link: the reply is then the x402 payment requirements (HTTP 402); retry the same POST /v1/tasks with a signed X-PAYMENT header and the job lists in that round trip. Only for an agent holding the wallet; never set it otherwise",
+  "type": "boolean"
+}
  2. 3 tool updates
    • Changedcheck_feasible1 field changed
      • addedInput schema / properties / sandbox
        Added value: +{
+  "description": "ask the fulfilment sandbox instead of the world. Always feasible there, because supply is a simulated operator; it says nothing about whether the work can be done at this address",
+  "type": "boolean"
+}
    • Changeddo_in_world1 field changed
      • addedInput schema / properties / sandbox
        Added value: +{
+  "description": "post this against the fulfilment sandbox instead of the real world. Nobody is dispatched, the evidence is generated by the exchange, nothing is paid and no money moves. The job walks the same states in seconds so you can finish an integration today. Every reply about it carries sandbox true; never tell a person a sandbox job is arranged",
+  "type": "boolean"
+}
    • Changedobserve_world1 field changed
      • addedInput schema / properties / sandbox
        Added value: +{
+  "description": "post this against the fulfilment sandbox instead of the real world. Nobody is dispatched, the evidence is generated by the exchange, nothing is paid and no money moves. The job walks the same states in seconds so you can finish an integration today. Every reply about it carries sandbox true; never tell a person a sandbox job is arranged",
+  "type": "boolean"
+}
  3. 8 tool updates
    • First observedcheck_feasible
    • First observeddo_in_world
    • First observedfind_out
    • First observedjob_evidence
    • First observedjob_receipt
    • First observedjob_status
    • First observedlist_bids
    • First observedobserve_world

Related MCP Connectors

Related MCP Servers

  • 4bl1ty MCP Server

    Brissux-Labs
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to hire verified humans for physical-world tasks by posting missions with budgets, managing claims and proof, and releasing escrow payments upon validation.
    MIT
  • humanforai by humanforai

    humanforaiofficial

    humanforai
    A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to hire verified human operators for tasks requiring physical presence, human perception, or judgment, such as real-world verification, product testing, and data collection.
    6
    MIT
  • humanforai by humanforai

    humanforaiofficial

    humanforai
    A
    license
    A
    quality
    A
    maintenance
    Enables AI agents to hire real human operators for tasks requiring physical presence, human perception, or judgment, such as verification, testing, data collection, and physical-world tasks.
    4
    52 npm
    1
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources