No user-submitted related servers found.
Scored across 2 tools
Each tool targets a clearly distinct evidence source: one resolves an installed dependency call-site, the other reads a repository-local JSON file via RFC 6901 pointer. The descriptions are explicit about the different inputs, so there is no real ambiguity.
Both names follow the evidrift_record_ prefix with snake_case, but one is a bare verb ('evidrift_record') while the other includes a direct object ('evidrift_record_json_pointer'). The pattern is mostly consistent but slightly unbalanced, making the first name less descriptive.
With only two tools, the surface feels thin, though the narrow specialization of recording evidence from just these two sources could justify it. It is borderline but not extreme, so a middling score is appropriate.
The domain appears to be specific types of evidence recording, and the two tools cover the two stated cases well. The descriptions explicitly rule out other methods (URL, command, package code, LLM), suggesting the scope is intentional. Minor gaps in other potential evidence types are acceptable for this narrow purpose.