io.github.pcaiano/toolscout
version 1.0.0
- scanned 2026-10-16
- source github.com/pcaiano/toolscout
- transport streamable-http
- methodology 0.2.0
the repository this server declares (https://github.com/pcaiano/toolscout) is not publicly reachable, so its documentation could not be read — note that a private repository and an absent one are indistinguishable from outside
not assessed
80measured on 25% of this axis
not assessed
100measured on 30% of this axis
not assessed
The evidence
Every deduction below names the artefact that produced it. Nothing on this page was executed: the source was read, never run, and no running server was contacted.
Auth Posture
- authentication_model
no source was fetched, and no credential header is declared. An undeclared header is not an absent one — measured 2026-09-15, only 10 of 100 remotes declare one at all — so `03` §4's "no authentication" band is not established.
- transport_security
declared endpoint(s) are HTTPS: https://trytoolscout.org/mcp; scored 80, not 100: `03` §4 reserves 100 for HTTPS *with HSTS*, and an HSTS header can only be seen by connecting, which `04` §9 does not do. This is an unverifiable band, not an observed absence.
- secret_handling
no source was fetched, so there is nothing to scan for committed credentials
- authorization_granularity
no source was fetched, so neither the tool count nor any access-control logic can be read
Maintenance
- recency
last commit 2 day(s) before 2026-10-16
- issue_responsiveness
only 0 issue(s) from outside the project fall inside `03` §5's 6-month window, which is under §5's floor of 3, and §5's lifetime-median fallback needs this repository's whole issue history — more of it than `04` §7's bounded fetch reads. A limit of ours, not a finding about the server.
- release_cadence
this repository publishes neither releases nor version tags
- bus_factor
this repository's 12-month history is longer than the bounded walk `04` §7 performs, and the authors found so far span more than one of `03` §5's bands. A limit of ours, not a finding about the server.
- repository_signals
`03` §5 scores this by quartile WITHIN the server's category, which needs a distribution across every scanned server and so cannot be computed while scanning one. It is a post-pass over the crawl and that pass does not exist yet.
Transparency
- license
the repository this server declares (https://github.com/pcaiano/toolscout) is not publicly reachable, so its documentation could not be read — note that a private repository and an absent one are indistinguishable from outside
- readme_quality
the repository this server declares (https://github.com/pcaiano/toolscout) is not publicly reachable, so its documentation could not be read — note that a private repository and an absent one are indistinguishable from outside
- declared_scopes
the repository this server declares (https://github.com/pcaiano/toolscout) is not publicly reachable, so its documentation could not be read — note that a private repository and an absent one are indistinguishable from outside
- changelog
the repository this server declares (https://github.com/pcaiano/toolscout) is not publicly reachable, so its documentation could not be read — note that a private repository and an absent one are indistinguishable from outside
- security_contact
the repository this server declares (https://github.com/pcaiano/toolscout) is not publicly reachable, so its documentation could not be read — note that a private repository and an absent one are indistinguishable from outside
Contest a finding
Every number here comes from a rule reading published source, and rules get things wrong. If something on this page is incorrect — or correct but mitigated by a check the rule cannot see — open an issue and we answer it in writing. A finding we got wrong is removed and the rule is fixed; one that stands is answered on the record.
Anyone can file: the maintainer, a researcher who disagrees with the classification, or a user who tested the server and could not reproduce it. Name this server and the rule or advisory ID shown beside the finding above. We aim to reply within five business days and to resolve within ten.