fcm-http2-mock-server

An HTTP/2-based mock server intended to emulate Firebase Cloud Messaging (FCM) HTTP/2 behaviors for testing clients and integration flows without calling the real FCM service.

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

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

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

As a mock server, strong auth/TLS enforcement is not guaranteed by the information provided. Treat it as non-production infrastructure and ensure it is not exposed publicly; do not rely on it for real security behavior. No evidence was provided about secure secret handling or dependency posture.

⚡ Reliability

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

Best When

You need a controllable, offline substitute for FCM HTTP/2 during development or automated tests.

Avoid When

You require real FCM semantics, quotas, authentication enforcement, or response timing fidelity beyond basic mock behaviors.

Use Cases

  • Local/integration testing of FCM client request/response handling
  • E2E tests for notification sending workflows without external dependencies
  • Development of retry/error-handling logic around FCM interactions
  • CI tests that need deterministic FCM-like responses

Not For

  • Production notification delivery
  • Security-sensitive environments where request spoofing could be confused with real service behavior
  • Load/stress testing that relies on realistic FCM performance characteristics

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

As an open-source-style mock server, pricing is typically not applicable; no monetization details were provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Mock servers may not reproduce real FCM edge cases (auth failures, quota errors, per-request headers) so agent-driven integration testing can pass while production still fails.
  • If the mock only approximates endpoints, agents may need to adapt request paths/headers to match the mock’s expected contract rather than FCM’s exact one.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for fcm-http2-mock-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