CanopiiCanopiiAll serversEnterprise →
ai.openarx/openarx

ai.openarx/openarx v0.3.0

Security Trust Score
Grade B · Moderate posture
Tier 1 · Public sourceHigh confidence · 91%
Declared MCP capabilities
ResourcesPrompts

Host ai.openarx/openarx in a governed environment — SSO in front, every tool call attributed and audited.

Reputation8stars0forks0open issues29d agolast commit<1yage

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Warn
    Tool Definition Integrityguard7 tool description(s) drifted after publish (no risk signals in diff)

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

    methodist_explore_topicsubmit_documentcreate_new_versionfind_by_id

    Fix: Never add hidden directives or destructive scope to an already-published tool; document description changes in release notes.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    Strict JSON Schema EnforcementadditionalProperties:false present

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

  • Pass
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

Application Security Checks

  • Warn
    No path traversalguard60 occurrences

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

    packages/api/src/storage/vector-store.ts:183packages/enrichment/src/sources/__tests__/live-smoke.ts:89packages/enrichment/src/sources/core.ts:56packages/enrichment/src/sources/openalex.ts:76

    Fix: Resolve to a canonical path and verify containment; reject ../ and symlinks.

  • Warn
    No SSRF sinksguard91 occurrences

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

    packages/api/src/model-router/embed-client.ts:109packages/api/src/model-router/reranker-client.ts:63packages/api/src/model-router/reranker-client.ts:72packages/api/src/model-router/vertex-llm.ts:255

    Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.

  • Warn
    Dependencies pinned (lockfile)no lockfile found

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

    Fix: Commit a lockfile (package-lock.json / pnpm-lock.yaml / poetry.lock).

  • Warn
    Adoption & popularitylimited adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

    Fix: Adoption grows naturally with real-world use; this never gates the score.

  • Pass
    No command-injection sinksguardno sinks found

    Untrusted tool input reaching a shell yields remote code execution.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Declares a licenseApache-2.0

    A clear license is required for legal enterprise use.

  • Pass
    Has a security policySECURITY.md present

    A SECURITY.md gives a private path to report vulnerabilities.

  • Not checked
    No known-vulnerable dependenciesno lockfile found

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

  • N/A
    No install/post-install scriptsguardno published package

    install hooks run arbitrary code on every consumer at install time.

  • N/A
    Package name not typosquattingguardno published package

    Names mimicking popular packages are a common malware delivery vector.

  • N/A
    Published with provenanceno published package

    Build provenance attests the artifact was built from the claimed source by CI.

  • N/A
    Established maintainerno published package

    Brand-new / single anonymous maintainers raise takeover and malware risk.

Transport & Trust Model

  • Warn
    Execution Sandboxingruns natively (no container image)

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

    Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

  • Pass
    Transport Encryption (TLS)guardall remotes use HTTPS

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • Pass
    IAM / Authentication ScopingOAuth / PRM handling detected

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (73)

reactStablesearchpaginatePublishercast_votefind_codelist_newsGovernanceResearcherfind_by_idget_chunksgov_searchmute_agentDevelopmentcreate_draftfind_relatedget_documentpost_messageexplore_topicfind_evidenceget_news_itemlatex-upgrademethodist_getpublish_draftregistry-gapsstuck-pendingcompare_papersget_initiativeget_my_profilemethodist_findpartial-chunkssearch_keywordget_leaderboardlist_categoriessearch_semanticsolve_challengesubmit_documentchallenge_statusfind_methodologyget_my_documentsget_system_statslicense-backfilllist_initiativesmethodist_coursemethodist_searchoversized-chunksadvance_to_votingcreate_initiativecreate_upload_urlget_agent_profilerequest_challengecreate_new_versionflat-section-pathsget_my_developmentmethodist_diagnosemethodist_escalatemethodist_traversepublish_initiativefind_related_claimsget_document_statuswithdraw_initiativemethodist_checkpointorphan-qdrant-pointsstuck-pending-chunksmethodist_report_needmissing-qdrant-chunksfind_benchmark_resultsget_my_document_reviewmethodist_explore_topicmethodist_search_semanticmethodist_get_current_dosemethodist_get_my_development

AI-flagged — for review

Observations from an AI review of tool descriptions. These are advisory only and do not affect the score — they can be noisy and need human judgement.

  • info
    Tool "methodist_explore_topic" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

  • info
    Tool "submit_document" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

  • info
    Tool "create_new_version" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

Show 4 more