MCPE_Server

MCPE_Server is a Java-based Minecraft: Pocket Edition server implementation, intended to accept Minecraft PE client connections and run a multiplayer game server.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Infrastructure minecraft bedrock mcpe server java multiplayer self-hosted
⚙ Agent Friendliness
16
/ 100
Can an agent use this?
🔒 Security
30
/ 100
Is it safe for agents?
⚡ Reliability
19
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
20
Error Messages
0
Auth Simplicity
50
Rate Limits
0

🔒 Security

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

Based only on repository metadata (no code/docs provided), TLS/auth/secret handling, dependency status, and security controls cannot be verified. As a network-facing game server, it will require careful hardening (firewalling, protocol-level validation, patching dependencies, and safe configuration management) before exposing to untrusted clients.

⚡ Reliability

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

Best When

You want a self-hosted Java Minecraft PE server and can manage the operational/security risks yourself.

Avoid When

You need a well-documented, authenticated REST/SDK/API integration, or enterprise-grade support/SLA.

Use Cases

  • Run a self-hosted Minecraft Pocket Edition server for small communities
  • Learn/experiment with Minecraft PE server protocol and server-side mechanics in Java
  • Prototype multiplayer worlds and server extensions (where supported by the project)

Not For

  • Production-grade internet-wide hosting without thorough security hardening and protocol validation
  • Use as a hosted SaaS API (no documented network/API interface for automation is provided here)
  • Compliance-heavy deployments without an audit of dependencies and runtime security controls

Interface

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

Authentication

OAuth: No Scopes: No

No authentication mechanism (API keys/OAuth) is described in the provided repository metadata. For a game server, client authentication/authorization would typically be handled at the game protocol layer, but this is not assessable from the given information.

Pricing

Free tier: No
Requires CC: No

As a repository/package, pricing is not applicable based on the provided metadata.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No documented programmatic API surface (REST/SDK/MCP) is indicated by the provided data, so agent integration is limited to running/building software rather than calling endpoints.
  • Server software typically requires environment-specific configuration; without README/instructions, operational details can’t be validated.
  • Game-server actions are stateful; automated retries may not be safe without idempotent endpoints (not documented here).

Alternatives

Full Evaluation Report

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

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