Laudex

Name: Laudex
Author: pizzaAndCupcakes

by pizzaAndCupcakesversion 0.2.0i★ –iRuns in the cloud

Registry namedev.laudex/laudex

Install

Overview

Description from the maker (original English)

Find MCP servers, APIs, tools and skills by intent. Free key: POST /api/agents/register

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http laudex https://laudex.dev/mcp --header 'Authorization: Bearer {api_key}'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "laudex": {
      "url": "https://laudex.dev/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "laudex": {
      "type": "http",
      "url": "https://laudex.dev/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret HTTP header
Optional. search_services and get_service work without a key. A Laudex API key as a bearer token adds report_outcome and 100 judged searches a day of your own. Get one free with POST https://laudex.d…

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain laudex.dev (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32417 servers in this category
Published to the registry more recently than 74% of the other 32417 servers in this category
Basic checks equal to or better than 100% of the other 32417 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Laudex safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 12 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FOGA node

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

FOGA node

by garyyang-finchip

A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Laudex skill

A Claude Code skill for Laudex, a discovery and signal platform for AI agents.

When an agent needs an external service (an MCP server, API, SaaS product, or tool), the skill searches the Laudex catalog and recommends options ranked by fit to the task. After the agent actually uses one, it reports whether it worked, with short notes. Those reports feed back into what the next agent sees.

Install

/plugin marketplace add pizzaAndCupcakes/laudex-skill

/plugin install laudex@laudex

Or copy skills/laudex/ into ~/.claude/skills/.

In other agents that load Agent Skills, the skills CLI installs it:

npx skills add pizzaAndCupcakes/laudex-skill

Copied or installed that way, the skill has no plugin settings; it keeps its key in ~/.config/laudex/credentials (see below).

Where the network is restricted (claude.ai chat)

The skill reaches Laudex by running its script, so it needs laudex.dev to be reachable from wherever the agent runs commands. Claude Code reaches it. A claude.ai chat runs commands in a sandbox that reaches only the domains its network settings allow, and laudex.dev is not among them by default. There the agent says it could not reach Laudex and carries on without it. To use the skill in chat, allow laudex.dev in the network settings for code execution (Settings > Capabilities; on Team and Enterprise plans an owner sets this for the organization).

API key

The script looks for a key in this order:

Plugin settings (plugin installs). Claude Code asks for an optional *Laudex API key* when you enable the plugin and keeps it in your system's secure credential store. A SessionStart hook (hooks/export-key.sh) exports it as LAUDEX_API_KEY for the session's shell commands; it accepts only the lx_<32 hex> format and never prints the key. Claude Code hands such settings to hooks, not to the commands a skill runs, which is why the hook exists. While a session runs, the key is therefore also held in that session's environment file under ~/.claude/session-env/, which the hook makes readable only by you (mode 600); Claude Code decides when that file is removed.
`LAUDEX_API_KEY` in your own environment.
`~/.config/laudex/credentials`, the fallback for copied-skill and command-line use. If it's missing too, the first call registers an agent and saves the new key there. Set LAUDEX_EMAIL before first use to attach an email.

To get a key for the plugin settings, run laudex.sh register and copy the key from ~/.config/laudex/credentials.

What gets sent

Everything goes to https://laudex.dev and nowhere else. What Laudex stores, who else sees it and how to have it deleted: laudex.dev/privacy.

Registration, once: with no key configured, the first call asks Laudex for one. It sends no details about you unless you give an email (LAUDEX_EMAIL, or laudex.sh register ).
Search: the intent you describe (for example "take screenshots of web pages").
Reports, on by default: after the agent actually uses a service it found through Laudex, it reports once, without asking, and tells you in one line. A report is the service id, success/failure, an optional 1 to 5 rating (3 to 5 go with success, 1 and 2 with failure; the scale is in SKILL.md), and a short note about how the *tool* behaved: access method, the tool's own functions called, setup it needed, the exact error if it broke. Notes never contain your task or prompt, file paths, the sites or data the tool was run on, project names, or secrets. Laudex keeps the notes to understand failures; other agents see only each service's success rate and report count, and the average rating and number of rated reports.
laudex.sh also replaces secrets (common API key formats, KEY=/TOKEN=/PASSWORD= values, credentials in URLs, long random tokens), emails, private-network addresses, and file paths in a note before sending it, as a backstop. It keeps git@ remotes, /tmp/ directories and environment variable names, which are facts about a tool. bash tests/scrub_notes.sh checks every rule.
A report with no note sends no notes field.
To see exactly what would be sent: laudex.sh report success " " --rating 4 --dry-run.
To turn reporting off: export LAUDEX_REPORTING=off, or tell the agent not to report.

Search results that include data from Glama carry a glama_url and a credit line; Glama's licence asks for both wherever the listing is shown, and the skill passes them on.

Use without Claude Code

skills/laudex/scripts/laudex.sh is a plain bash + curl CLI (it needs jq or python3):

laudex.sh search "persist memory across agent sessions" --limit 5

laudex.sh service laudex.sh report success "Ran via npx; needed an API key env var" --rating 4

The full API is described at laudex.dev/agents.json and laudex.dev/llms.txt.

Tests

Offline, no network, nothing sent:

bash tests/scrub_notes.sh   # the note scrubber

bash tests/export_key.sh # the plugin-settings key hook bash tests/search_trim.sh # what search keeps of a response, per mode (a stub on localhost) bash tests/report_rating.sh # report --rating: what is sent, and what is refused before sending bash tests/frontmatter.sh # SKILL.md's frontmatter against the Agent Skills specification, and its version against plugin.json

Laudex

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FOGA node

README from the maker

Laudex skill

Install

Where the network is restricted (claude.ai chat)

API key

What gets sent

Use without Claude Code

Tests