
Copilot Mcp
io.github.Apex-FoundationPublished by GitHub account Apex-Foundationv0.11.5Updated Oct 24, 2026
Web3 founder diligence: code audit, jurisdiction, fund matching, portfolio, scoring.
Overview
A local MCP server that gives an assistant Web3 founder diligence tools: code audit, jurisdiction checks, fund matching, portfolio review, and scoring.
- What you can do
- This server exposes diligence-oriented capabilities for Web3 founders, covering code audit, jurisdiction questions, fund matching, portfolio review, and scoring. It runs as a local stdio process started from the npm package @apexfdn/copilot-mcp, and it talks to an Apex Copilot API endpoint. The manifest does not list individual tool names, so the exact tool set is not documented here.
- When to use it
- Consider it when an assistant needs to help with Web3 founder diligence work such as reviewing a project's code, checking jurisdictional considerations, matching with funds, or producing a score. It is a desktop-only local process, so it suits a developer or analyst machine rather than a hosted or browser environment.
- Requirements
- Runs locally over stdio from the npm package @apexfdn/copilot-mcp, so Node.js and npm are needed. It requires the environment variable APEX_COPILOT_API_BASE for the Apex Copilot API endpoint and the required secret APEX_COPILOT_PAT, a personal access token obtained from the provider's dashboard. Network access to that API is implied.
Installation
In SourceWeft
- Open Copilot Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.11.5LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.