1. Conduid
  2. Developer Tools
  3. Openhands List MCP
MCP server · Developer Tools

Openhands List MCP

Openhands list MCP server

Unclaimed last commit 10 months ago devtools
46Fair

Scored 3 days ago · breakdown

About Openhands List MCP

Openhands List MCP is an MCP server published by rjboer in the Developer Tools category: openhands list MCP server. It has been installed 0 times through Conduid.

Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx openhands-list-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Openhands List MCP

Powered by Claude · Grounded in docs

I know everything about Openhands List MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.2v0.2
v0.1.0v0.1.0

README

OpenHands MCP List Tool

or coloqually Review-Board HTTP Service

A tiny Go micro-service that stores review items in memory and exposes a handful of REST-style endpoints.
It is designed to be called directly by humans (curl/Postman) or plugged into OpenHands as an SSE-tool backend.


Features

Verb Path Purpose
GET /open/{list} Return one open item (first with status="open").
GET /close/{list} ?index=n Close item n (or the first open one) and return it.
GET /add/{list} Create an empty list.
POST /add/{list} Create list and seed it with the JSON array in the body.
GET /delete/{list} Delete the list.
GET /list/{list} Return the full list as JSON.

On any unknown route or wrong HTTP verb the service replies 400 plus a concise usage cheat-sheet.


Quick start

# clone & build
git clone https://github.com/your-org/review-board.git
cd review-board
go run .

How to use

Clone the git repository

#Step 1 (dont forget the .)
docker build -t openhands-list-mcp:dev .
#Step 2, (launch it as a deamon -d or without)
docker compose up -d

Then Step 3, couple it to openhands,

Register it in openhands; I use port 3002 in my docker-compose and I use multiple dockers.. by itself the application hosts on port 3002 default (modify via docker file). The port is modified by the PORT environment variable.
bridge via host.internal like below (yes it shows an old port, 3001).

image

Step 4: Debugging...

Assuming you run two seperate containers (comes in handy and you dont have to reboot the entire stack every time).

  • First curl from inside your openhands container: openhands-list-mcp is the hostname of my service.. Try this from inside the openhands docker (depending on your port)
curl http://openhands-list-mcp:3002
curl http://openhands-list-mcp:8080
curl http://openhands-list-mcp:3002/mcp/health

Failure looks like this:

curl: (6) Could not resolve host: openhands-list-mcp

Succes on the /mcp/health handle looks like this:

Valid endpoints (all JSON):

GET  /open/{list}              → first open item with its index
GET  /close/{list}?index=n     → close item (index optional)
GET  /add/{list}               → create empty list
POST /add/{list}               → create list, seed JSON array
GET  /delete/{list}            → delete list
GET  /list/{list}              → full list JSON
GET  /timeout/{seconds}        → set throttle delay (0-600 s)
GET  /meta                     → summary for index page
/ or /index.html               → web UI
# 

The MCP server will tell you in the logs where it is hosted: Like this:

[+] Running 1/1
 ✔ Container openhands-list-mcp  Created                                                                                                                      0.0s
Attaching to openhands-list-mcp
openhands-list-mcp  | 🔗  Listening at http://localhost:3002  – UI on /

Alternatively, if openhands give an error because it cannot stream.... You should check the routing.....

2025-06-08 20:56:30.703 | - openhands:ERROR: utils.py:100 - Failed to connect to url='http://host.docker.internal:3001' api_key='******': 
2025-06-08 20:56:30.703 | Traceback (most recent call last):
2025-06-08 20:56:30.703 |   File "/usr/local/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
2025-06-08 20:56:30.703 |     return await fut
2025-06-08 20:56:30.703 |            ^^^^^^^^^
2025-06-08 20:56:30.703 |   File "/app/openhands/mcp/client.py", line 71, in connect_with_timeout
2025-06-08 20:56:30.703 |     streams = await self.exit_stack.enter_async_context(streams_context)
2025-06-08 20:56:30.703 |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

On linux one might create a specific network (in Windows you can use host.docker.internal, but it might not work in Linux).

docker network create openhands-net

Impression on port 8080 or 3001

image

README mirrored from the source repository 3 days ago. The original is authoritative.

Questions

About Openhands List MCP

How do I install Openhands List MCP?

Run npx openhands-list-mcp, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Openhands List MCP safe to use with an AI agent?

Its trust score is 46 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Openhands List MCP still maintained?

The last commit was 10 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.