Loading the registry…
MCP server for integrating multiple AI APIs
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.
npm: @physics91org/ai-api-mcp @ 0.2.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @physics91org/ai-api-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 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.9s
v2.0.11
6 findings · 11.0s
v0.3.74
27 findings · 2.6s
v0.1.0
0 findings · 4.9s
v0.1.0
1 finding · 4.9s
v0.1.0
0 findings · 9.2s
v0.71.0
0 findings · 0.3s
v2.3.8
0 findings · 8.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged91 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
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 34 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 27 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
3 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/publish.yml · reported by agent-audit-kit
3 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, opt.nerlo-rules.nerlo-install-run-bundled-artifact, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md, /repo/docs/TROUBLESHOOTING.md · reported by cisco-skill-scanner, nerlo-install-instruction
The model could have called any of these a false positive and did not.
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
27 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-MCP-003, AAK-SECRET-007, AAK-MCP-ATTEST-001 and 7 more · Files: mcp_config_example.json, claude_mcp_config.json, /repo/repo/CONTRIBUTING.md and 3 more · reported by agent-audit-kit, cisco-skill-scanner
High-severity configuration issues require attention.
The artifact contains multiple high-severity findings related to configuration within `claude_mcp_config.json` and `mcp_config_example.json`. These findings, identified by rule AAK-MCP-003, indicate potential for significant security impact if not addressed. Reviewing these configuration files is critical before deployment.
Concern level assessed by the review: High. 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.