projscan
projscan is an MCP server published by abhiyoheswaran1; its MCP spec-revision support has not been verified yet. Last verified 2026-08-07.
Does projscan support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision projscan supports (as of 2026-08-07).
Is projscan a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for projscan (as of 2026-08-07).
How do I connect to projscan?
projscan is available via the package npm:projscan, the official MCP Registry under io.github.abhiyoheswaran1/projscan, the source repository at https://github.com/abhiyoheswaran1/projscan. Authentication: unknown. Transports: stdio.
When were projscan's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
Agent-first MCP. 11 AST adapters, 12 named languages, 51 tools, mission outcomes. Local.
How widely adopted is projscan?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for projscan
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 4
- Forks
- 0
- Last pushed
- (74 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Package (npm) as of
- Latest version
5.0.3- Last published
- First published
- Releases
- 99
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 7
- Unpacked size
- 29.0 MB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).