Lamdis Exchange MCP server
not respondingPay people nearby for physical work: find out if something is true, or have it done.
D52/100grade D
Adoption
Growing
0 stars
Reviews
Write oneNobody has reviewed Lamdis Exchange yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Lamdis Exchange tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
1 high
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote unreachable: TypeError: fetch failed0/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 1 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableTypeError: fetch failed
Overall 52/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install Lamdis Exchange in Claude Code, Cursor or VS Code
claude mcp add --transport http exchange https://exchange.lamdis.ai/mcp
Lamdis Exchange: common questions
- Is Lamdis Exchange MCP server safe?
- Not recommended: it is graded D (52/100). Read the Lamdis Exchange safety report
- How do I install Lamdis Exchange?
- It runs remotely at exchange.lamdis.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Lamdis Exchange need an API key?
- Yes. The registry entry asks for
Authorization. - Is Lamdis Exchange maintained?
- The last commit was 8 days ago (2026-09-19). The latest release is v0.1.0.
- Is Lamdis Exchange up?
- 0% of our last 28 checks got an answer. We check remote servers about four times a day.