README tagline: "One MCP for reverse engineering across binaries, applications, and runtime behavior." The agent calls REA through MCP to inspect a local target and trace relevant code; REA returns findings with their evidence, and the agent uses them to explain the behavior or write and test an implementation.
Score v2 uses only observed signals. The displayed contribution is weight × value × 100. Missing factors are insufficient evidence.
Score factor
GitHub health
18% weight. insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
Score factor
Agent use
16% weight. insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
Score factor
Human notes
14% weight. insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
Score factor
Composability
16% weight. insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
Score factor
Checklist
10% weight. An MCP surface is declared. No API is declared. Cost is unknown. 1 of 3 checklist fields are complete.
Value 0.33 · 3.3 points
10% weight × 0.33 value
3.3 points
An MCP surface is declared. No API is declared. Cost is unknown. 1 of 3 checklist fields are complete.
Score factor
Evidence quality
14% weight. 3 sources cover 1 evidence types. The latest dated evidence is 2026-10-10. Freshness is omitted unless observed as a signal.
Value 0.26 · 3.7 points
14% weight × 0.26 value
3.7 points
3 sources cover 1 evidence types. The latest dated evidence is 2026-10-10. Freshness is omitted unless observed as a signal.
Score factor
Benchmarks
12% weight. insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
insufficient evidence
Total7.00 → 7 after rounding
GitHub health: insufficient evidence
Agent use: insufficient evidence
Human notes: insufficient evidence
Composability: insufficient evidence
Benchmarks: insufficient evidence
[ Claims ]
Publisher-asserted record
Claims are what the publisher declares. Score uses observed signals, not these assertions, except for checklist fields derived from interfaces. MCP, API, cost, and license claims are marked verified, unverified, or contradicted from intake evidence.
README tagline: "One MCP for reverse engineering across binaries, applications, and runtime behavior." The agent calls REA through MCP to inspect a local target and trace relevant code; REA returns findings with their evidence, and the agent uses them to explain the behavior or write and test an implementation.
README tagline: "One MCP for reverse engineering across binaries, applications, and runtime behavior." The agent calls REA through MCP to inspect a local target and trace relevant code; REA returns findings with their evidence, and the agent uses them to explain the behavior or write and test an implementation.
README tagline: "One MCP for reverse engineering across binaries, applications, and runtime behavior." The agent calls REA through MCP to inspect a local target and trace relevant code; REA returns findings with their evidence, and the agent uses them to explain the behavior or write and test an implementation.