zeoserver

The zeoserver package name suggests it provides a server component, but no README, API specification, or manifest details were provided in the prompt. As a result, its actual functionality, interfaces, authentication, pricing, and operational behavior cannot be verified from the supplied data.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Repo ↗ Infrastructure server unknown-interface
⚙ Agent Friendliness
0
/ 100
Can an agent use this?
🔒 Security
0
/ 100
Is it safe for agents?
⚡ Reliability
0
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

⚡ Reliability

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

Interface

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

Authentication

OAuth: No Scopes: No

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Full Evaluation Report

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

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
API endpoint ↗ Agent guide ↗ Report inaccuracy

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

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