mcp-servers

Provides multiple Model Context Protocol (MCP) server implementations (Python, Go, Rust) that expose MCP functionality over HTTP/SSE for use with MCP-capable clients (e.g., VS Code). Includes a Docker Compose setup to run the servers.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Ai Ml mcp model-context-protocol ai-tools api sse json-rpc fastapi golang rust vscode-integration docker
⚙ Agent Friendliness
47
/ 100
Can an agent use this?
🔒 Security
18
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
75
Documentation
55
Error Messages
0
Auth Simplicity
30
Rate Limits
0

🔒 Security

TLS Enforcement
20
Auth Strength
10
Scope Granularity
0
Dep. Hygiene
40
Secret Handling
30

No authentication/authorization is described in the provided README. Transport security (HTTPS/TLS) and secret-handling practices are also not described. Python server claims comprehensive error handling and logging, but details (e.g., whether logs include sensitive data) are not provided.

⚡ Reliability

Uptime/SLA
0
Version Stability
30
Breaking Changes
20
Error Recovery
50
AF Security Reliability

Best When

You want a self-hosted MCP server interface locally or in your own infrastructure, especially the Python server that is labeled production-ready.

Avoid When

You need guaranteed security controls (TLS/auth/scoped authorization) based solely on the provided documentation, or you require production readiness from the Go/Rust servers.

Use Cases

  • Connect an AI agent/tooling workflow to MCP tools via standardized JSON-RPC/SSE endpoints
  • Use the Python MCP server as a ready-to-run local MCP gateway for developer tooling
  • Experiment with alternative MCP server implementations in Go and Rust for customization

Not For

  • Production deployments without verifying security/auth configuration (not described in the provided README)
  • Use as a managed hosted service (appears self-hosted via Docker)
  • Use of the Go/Rust servers for production use cases without further validation (marked in progress)

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

The README does not describe authentication/authorization for the MCP endpoints.

Pricing

Free tier: No
Requires CC: No

Open-source repository (MIT per metadata); costs depend on your hosting/infrastructure.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Go and Rust servers are marked in progress; protocol coverage/HTTP interface may be incomplete vs the Python server
  • Auth, rate limiting, and error semantics are not documented in the provided README, so agents may need to handle generic HTTP/JSON-RPC failures conservatively
  • SSE endpoints may require correct client connection behavior/timeouts not specified here

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-servers.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered