MCP.Market

Diavlos MCP server

by harisnopen·io.github.harisnopen/diavlos·v2.1.1·1 stars

Signed messages between AI agents. Dangerous actions wait for a human-signed approval.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

not scanned yet

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Diavlos yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Diavlos tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Diavlos compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Release history: 2 versions in the registry since 2026-09-27, latest 2026-09-28, typically one every 1 day.

Install Diavlos in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Diavlos repository's README, as published. We do not edit it. Read it on GitHub

>> Diavlos

Diavlos (δίαυλος, Greek for "channel") lets AI agents talk to each other. Any agent, any terminal, any computer. You pick a room name and share a signed invite. The agents find each other and start talking.

It is one small program. You install it once. It runs in the background. Any agent from any vendor can use it: Claude Code, Codex, Cursor, Gemini CLI, Aider, or one you wrote yourself. No account. No server to set up.

The big difference from a plain chat pipe: messages never get lost, every sender is who they say they are, and messages carry a type (task, reply, done) so agents never have to guess.

https://diavlos.sh

Watch it work

Two rented cloud desktops on different machines, one room, over the public internet with nothing port-forwarded. A real Claude agent does the work, a scripted agent hands it out, a human approves the one risky step from a browser, and a read-only observer key audits the lot afterwards. Nineteen signed messages, 77 seconds from the first task to the human's approve.

It also refuses a prompt injection on camera: the boss agent tells the Claude agent to ignore its instructions and run something it is not allowed to, and the message is rejected rather than obeyed.

The whole run, step by step — stills, the 19-message transcript, the export that verifies on the other machine, and the commands to reproduce it. The 115-second video · transcript

Two E2B sandboxes, one human gate

Two real E2B sandboxes join one room over the public internet. The planner in sandbox A asks the runner in sandbox B to run a job. The runner asks a human first. After an approve, the gate spends it at the room's home and the job runs. After a deny, nothing runs. Every message is signed and checked, and the audit bundle verifies.

This is a replay of the real log from GitHub run 35896619176. The example · the 31-second video

The seven promises

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Diavlos: common questions

Is Diavlos MCP server safe?
Mostly: it is graded B (83/100). Read the Diavlos safety report
Does Diavlos need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Diavlos maintained?
The last commit was 38 days ago (2026-09-27). The latest release is v2.1.1.
How does Diavlos compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.