NEAT
NEAT is an MCP server published by neat-technologies, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does NEAT support the current MCP specification (2026-07-28)?
Not yet confirmed. NEAT is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is NEAT a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for NEAT (as of 2026-08-20).
How do I connect to NEAT?
NEAT is available via the package npm:@neat.is/mcp, the official MCP Registry under io.github.neat-technologies/neat, the source repository at https://github.com/neat-technologies/neat. Authentication: unknown. Transports: stdio.
Does NEAT support MCP revision 2025-11-25?
Yes. NEAT supports MCP revision 2025-11-25 (checked 2026-08-20).
Does NEAT support MCP revision 2026-07-28?
No. NEAT was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were NEAT's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Fused graph of your codebase - static code + runtime OTel - for AI agents, over MCP.
Which MCP spec revisions does NEAT support?
NEAT has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is NEAT?
Ranked #276 in The MCP 500 with Adoption Index 49.05 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 1,113 | API · |
| GitHub stars | 18 | API · |
| GitHub forks | 1 | API · |
| Last push | 2026-09-15T00:19:25Z | API · |
| Repository archived | no | API · |
Repository and package signals for NEAT
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
- Created
- Open issues
- 74
- Primary language
- TypeScript
- License (repository)
- Apache-2.0
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: architecture, graph-theory, platform-engineering, software-engineering — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.9.5- Last published
- First published
- Releases
- 122
- License (package)
- BUSL-1.1
- Maintainers
- 1
- Direct dependencies
- 3
- Unpacked size
- 389 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.neat-technologies/neat at version 0.7.5 - lists package npm:@neat.is/mcp and repository https://github.com/neat-technologies/neat - accessed
- npm registry metadata for @neat.is/mcp at published version 0.9.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed