Reliability
Whether the server starts consistently, completes the MCP handshake, and behaves as its tool declarations claim.
FOLLOWMCP REVIEW SCORE
FMRS scoring and verification
FollowMCP evaluates servers across five explainable dimensions and clearly separates source review from real runtime verification. Scores total 100 and cannot be raised through payment.
Security and permissions
Whether permissions, credentials, data boundaries, and side effects are clear and follow least privilege.
Maintenance
Whether releases, commits, issue responses, and dependency updates remain active.
Documentation
Whether setup, auth, tool parameters, limits, and troubleshooting are documented with verifiable detail.
Setup experience
The number and complexity of steps from obtaining dependencies to a working connection in major clients.
Verification is not a vague badge
Source and config reviewed
An editor checked names, tools, setup, permissions, and bilingual content against source material, without claiming a successful runtime test.
Runtime connection verified
An operator started the server at the recorded revision and completed MCP initialization and tool-list negotiation.
Upstream changed; retest due
The upstream revision changed. Historical evidence remains visible, but the current version needs a new test.
Scoring rules
- Each dimension is scored independently from 0–20 with a written rationale.
- Missing evidence lowers a score; brand recognition never fills the gap.
- Material security findings and failed verification must remain visible.
- A material upstream revision moves the server into the retest workflow.