ai.orggen/orggen
version 1.0.0
- scanned 2026-10-16
- source github.com/ms-spown/orgschema-ai
- transport streamable-http
- methodology 0.2.0
the repository this server declares (https://github.com/ms-spown/orgschema-ai) 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 65% of this axis
not assessed
not assessed
this server's declared repository could not be read through the GitHub API, so `03` §5's maintenance signals were not retrieved — note that a private repository and an absent one are indistinguishable from outside
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
registry declares required credential header(s): Authorization; scored 80, not 100: `03` §4's top band also requires that the server REFUSE an uncredentialed request, which cannot be established without connecting (`04` §9). The requirement is declared; its enforcement is unverified.
- transport_security
declared endpoint(s) are HTTPS: https://www.orggen.ai/api/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
no last-commit date was retrieved for this repository
- issue_responsiveness
no issue-response median was retrieved. An unanswered issue scores 0 under `03` §5, but an absent measurement is not an unanswered issue.
- release_cadence
no release history was retrieved for this repository
- bus_factor
no contributor history was retrieved for this repository
- 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/ms-spown/orgschema-ai) 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/ms-spown/orgschema-ai) 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/ms-spown/orgschema-ai) 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/ms-spown/orgschema-ai) 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/ms-spown/orgschema-ai) 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.