Repo Security Scanner — Malicious Code & Supply Chain

io.github.eltociearPublished by GitHub account eltociearv0.1.0Updated Oct 24, 2026

Audit GitHub repos for malicious and supply-chain code before you depend on them.

The publisher's own server: Agent.chain.tokyo Address Contracts

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant audit GitHub repositories for malicious code and supply-chain risk before you depend on them.

What you can do
This server lets an assistant audit GitHub repositories for malicious code and supply-chain risk before you depend on them. It is offered as a remote endpoint, with the scanning work run by an Actor on Apify. The manifest does not list individual tools.
When to use it
Use it when you are about to depend on a GitHub project and want a check for malicious or supply-chain risk first.
Requirements
A remote endpoint reached over OAuth; requests must carry an Authorization header holding an Apify API token as a Bearer value. The endpoint returns 401 without one. An Apify account is also needed.
Before you install
You must supply an Apify API token in the Authorization header, so keep it private. Each run is billed to your own Apify account at the Actor's pay-per-event price, with no free tier, so using it spends money.

Installation

In SourceWeft

  1. Open Repo Security Scanner — Malicious Code & Supply Chain in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.eltociear%2Frepo-security-scanner/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "repo-security-scanner-malicious-code-sup": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=eltociear/mcp-server-security-scanner"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Chain integrations