MCP/Risk

Scan report

com.agishub/mcp

npm, scanned 2026-11-08, tool surface via remote-tools-list

This page reports an automated security scan of com.agishub/mcp (npm), scanned 2026-11-08. It rates trust (provenance, transport, known vulnerabilities, instruction integrity) as grade B and capability risk (what the tools can do) separately at high. It does not certify the server is safe to connect; it reports what could be checked from outside.

Automated checks

StatusCheckPolicyResult
WARN Listed on the official MCP registry §1.1

Not found on the official MCP registry. Not disqualifying, but listed servers carry namespace-verified provenance.

PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 57 days ago
  • Stars: 0
  • License: MIT
  • Security policy (SECURITY.md): absent
WARN Published package is consistent and attested §1.3
Minor integrity gaps: no npm provenance attestation. 6 findings
  • Package: @agishub/mcp@3.0.1 ↗
  • Ecosystem: npm
  • Age: 105 days
  • Weekly downloads: 20
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
34 tool(s) enumerated. Capabilities detected: network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 4 findings
  • Tools exposed: 34
  • send: network-egress
  • status: network-egress
  • Detected capabilities: network-egress
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://api.agishub.com/mcp
UNVERIFIABLE Authentication required §3.2

Endpoint rejected the probe (HTTP 400); whether it requires authentication could not be determined.

WARN OAuth protected-resource metadata published §3.3
No protected-resource metadata found - clients cannot discover the authorization server per spec. 1 finding
  • Checked: https://api.agishub.com/.well-known/oauth-protected-resource
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for @agishub/mcp @3.0.1 (npm).

PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 68 server-supplied text item(s).

Verify manually - the scoring model can’t judge these for you

  • §2.3 - Is the tool surface no broader than the server’s stated purpose requires?
  • §3.4 - For stdio servers: which environment credentials does it read, and are they scoped rather than org-wide tokens?
  • §6.1 - Cross this server’s capabilities with your already-connected servers: any read-capability × send-capability pairs need explicit sign-off.
  • §6.2 - Run the connecting agent with sandboxing and egress controls sized to the combined tool surface, not just this server’s.

Methodology: MCP Server Security Policy. Checks and scoring weights are open source. Unfamiliar term? See the glossary.