json-server-https

json-server-https is a variant of json-server that serves a JSON file (or JSON-based data) over HTTPS, enabling REST-like CRUD endpoints for local development/testing.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ DevTools devtools mock-api rest https json-server
⚙ Agent Friendliness
38
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
22
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

HTTPS is the primary security feature; authentication/authorization is generally absent in json-server-like mocks. HTTPS configuration depends on how certificates/keys are supplied; transport security does not replace authz controls.

⚡ Reliability

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

Best When

You need a quick HTTPS mock server that exposes typical json-server routes for development and testing.

Avoid When

You need robust security controls (authz/authn, audit logging, rate limiting), guaranteed uptime/SLA, or strict API contract management.

Use Cases

  • Local development with a mock REST API over HTTPS
  • Testing client apps that require secure origins (e.g., Service Workers, secure cookies)
  • API prototyping and integration testing without a real backend

Not For

  • Production-grade API hosting
  • High-security or compliance-critical deployments
  • Complex business logic, authorization, or data modeling needs

Interface

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

Authentication

OAuth: No Scopes: No

json-server-style mocks typically do not implement authentication; any HTTPS support is transport-level only.

Pricing

Free tier: No
Requires CC: No

Open-source tooling; no direct pricing information provided.

Agent Metadata

Pagination
unknown
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • HTTPS setup may require providing certificates/keys; misconfiguration can block agent access.
  • No standardized API contract (e.g., OpenAPI) is typically available for agent-driven tooling.
  • json-server behavior may differ slightly from real backends (ordering, validation, error formats).

Alternatives

Full Evaluation Report

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

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