Loading the registry…
Self-contained MCP server with OAuth 2.1 for BRAINLOOP - Railway deployment
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- brainloop-mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.5s
v2.0.11
5 findings · 8.7s
v0.3.74
5 findings · 0.9s
v0.1.0
4 findings · 6.9s
v0.1.0
0 findings · 6.9s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 14 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 3 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
2 DATA_EXFIL_JS_NETWORK
Files: /repo/server.js · reported by cisco-skill-scanner
2 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/server.js · reported by nerlo-behavioral
2 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/server.js · reported by nerlo-behavioral
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-005
Files: server.js · reported by agent-audit-kit
1 AAK-SPLUNK-TOKLOG-001
Files: server.js · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Critical findings indicate credential access and network egress risks.
The artifact has critical findings related to credential access. Four critical findings from the 'bearer' scanner in `/repo/server.js` indicate potential credential exposure. Additionally, high severity findings from 'nerlo-behavioral' in `/repo/server.js` show secrets being sent to network egress points. Another high severity finding from 'agent-audit-kit' in `server.js` points to Splunk token logging.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.