MCP.Market

Agentdrop MCP server

by qFlav·io.github.qFlav/agentdrop-mcp-server·v0.2.27·1 stars

MCP server for AgentDrop - encrypted file transfer between AI agents across any host or network.

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

full report

Adoption
New

1 stars56 downloads/wk

Reviews

Write one

Nobody has reviewed Agentdrop yet.

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

Agentdrop tools

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

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan37 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 143 days ago8/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Agentdrop compares

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

Safety score
78/100
higher than 57% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
56
more than 46% of 12,191 servers with a package

Install Agentdrop in Claude Code, Cursor or VS Code

Runs npx -y agentdrop-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add agentdrop-mcp-server -- npx -y agentdrop-mcp-server
Add to Cursor

What the publisher says

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

MCP Registry

The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.

📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation

Development Status

2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!

2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).

Current key maintainers:

  • Adam Jones (Anthropic) @domdomegg
  • Tadas Antanavicius (PulseMCP) @tadasant
  • Toby Padilla (GitHub) @toby
  • Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov

Contributing

We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.

Often (but not always) ideas flow through this pipeline:

  • Discord - Real-time community discussions
  • Discussions - Propose and discuss product/technical requirements
  • Issues - Track well-scoped technical work
  • Pull Requests - Contribute work towards issues

Quick start:

Pre-requisites

  • Docker
  • Go 1.24.x
  • ko - Container image builder for Go (installation instructions)
  • golangci-lint v2.4.0

Running the server

# Start full development environment
make dev-compose

This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.

Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.

By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCPREGISTRYSEEDFROM=data/seed.json MCPREGISTRYENABLEREGISTRY_VALIDATION=false make dev-compose.

The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.

Alternative: Running a pre-built Docker image

Shortened. The full README is on GitHub.

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

Agentdrop: common questions

Is Agentdrop MCP server safe?
Mostly: it is graded B (78/100). Read the Agentdrop safety report
How do I install Agentdrop?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Agentdrop need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Agentdrop maintained?
The last commit was 180 days ago (2026-05-07). The latest release is v0.2.27.
How does Agentdrop compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers); downloads a week 56 (more than 46% of 12,191 servers with a package). Full comparison.