io.github.bytedance/mcp-server-search
version 1.0.0
- scanned 2026-10-16
- source github.com/bytedance/UI-TARS-desktop
- transport streamable-http
- methodology 0.2.0
the package this server declares (npm:@agent-infra/mcp-server-search@latest) could not be fetched from its registry, so its source could not be read
not assessed
not assessed
not assessed
81measured on 90% 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
transport is streamable-http but the entry declares no endpoint URL to read a scheme from
- 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 7 day(s) before 2026-10-16
- issue_responsiveness
median over 48 issue(s) in the last 6 months: 22.4 day(s) to first maintainer comment
- release_cadence
released 8 day(s) ago (by releases), inside `03` §5's 30-day window
- bus_factor
4 authors with >= 5 commits in 12 months
- 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 package this server declares (npm:@agent-infra/mcp-server-search@latest) could not be fetched from its registry, so its source could not be read
- readme_quality
the package this server declares (npm:@agent-infra/mcp-server-search@latest) could not be fetched from its registry, so its source could not be read
- declared_scopes
the package this server declares (npm:@agent-infra/mcp-server-search@latest) could not be fetched from its registry, so its source could not be read
- changelog
the package this server declares (npm:@agent-infra/mcp-server-search@latest) could not be fetched from its registry, so its source could not be read
- security_contact
the package this server declares (npm:@agent-infra/mcp-server-search@latest) could not be fetched from its registry, so its source could not be read
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.