io.github.Udhay-Adithya/neopat-mcp
PYPI · NEOPAT-MCP
Browse campus placement drives and apply, with confirmation.
Available components
Last scanned (12 days ago)
Scores higher than 0% of PyPI servers
Category Education and Research
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: the registry has no such package, so there's no artefact to verify. See how to fix → View diagnostics → Fail
- License check failed: the registry has no such package, so no license can be read. See how to fix → Fail
- Maintenance check failed: the registry has no such package, so there's no release history to read. See how to fix → Fail
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 −16
- Tool safety: pass → unverified ▼ security
- Stability: 0.23 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 22 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 +49
- Malware scan: unverified → pass ▲ security
- 16 Oct 26 −34
- Known CVEs: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Provenance: pass → fail ▼ security
- Source repository: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- The code this package runs automatically changed: its declared build backend security
- The attested source repository moved: Udhay-Adithya/neopat-mcp security
- Security disclosure: fail → unverified ▼ functional
- Dependency health: 0.99 → unverified ▼ functional
- License: pass → fail ▼ functional
- Maintenance: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Licence: MIT functional
- Package version: 0.1.3 → 0.1.4 functional
- 15 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 59 functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 95 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Analysed pypi/neopat-mcp@0.1.4
Provenance Package not found
The registry answered that no such package exists, so no provenance could be looked up.
| Result | Package not found |
|---|---|
| Ecosystem | pypi |
| Reason | Metadata unavailable |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
How do I install the io.github.Udhay-Adithya/neopat-mcp server?
io.github.Udhay-Adithya/neopat-mcp runs locally as a PyPI package, launched with uvx neopat-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · neopat-mcp
claude mcp add udhay-adithya-neopat-mcp -- uvx neopat-mcp
What is the io.github.Udhay-Adithya/neopat-mcp server?
io.github.Udhay-Adithya/neopat-mcp is listed in the public MCP registry as io.github.Udhay-Adithya/neopat-mcp. Browse campus placement drives and apply, with confirmation. This page covers its PyPI package (neopat-mcp).
Is the io.github.Udhay-Adithya/neopat-mcp server safe to use?
io.github.Udhay-Adithya/neopat-mcp scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the io.github.Udhay-Adithya/neopat-mcp server still maintained?
io.github.Udhay-Adithya/neopat-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.