mcp server
ARGUS-3 MCP Server
ARGUS-3 stdio MCP with WARDEN firewall: argus_ask, argus_status, argus_capabilities.
Description as published by the maintainer. Source
- version 0.2.5
- active
active — Most recent push to the repository was 2026-08-06.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.2.5 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-23 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-23 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
FlowCastle
— last commit 2026-07-25, shares telegram-bot
Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform.
-
io.github.0xSoftBoi/suwappu
— last commit 2026-08-06, shares telegram-bot
Cross-chain DEX for AI agents. Swap tokens across 7+ chains.
-
AIMarket MCP Gateway
— last commit 2026-08-05, shares aimarket
Stdio + Streamable-HTTP MCP gateway: SSRF-hardened web_fetch, web_search, metis_verify.
-
AIMarket Oracle Gateway
— last commit 2026-08-03, shares aimarket
Stdio MCP: 17 verifiable AIMarket oracles, 35 pay-per-call tools for AI agents.
-
AIMarket MCP Packager
— last commit 2026-08-03, shares aimarket
Stdio MCP packager: AIMarket hub plugins into self-hosted MCP server products.
-
io.github.axiosdevs/agentpump-mcp
— last commit 2026-07-11, shares telegram-bot
Launch & trade tokens on AgentPump, a Solana bonding-curve launchpad, from your AI agent.
-
MCPower Security Proxy
— last commit 2025-12-22, shares mcp-security, security
Security proxy that wraps MCP servers with real-time monitoring and policy enforcement
-
Defenter Proxy
— last commit 2025-12-22, shares mcp-security, security
Real-time semantic security for AI coding agents and MCP tools
-
agenttool
— last commit 2026-08-05, shares agent-economy
Where agents arrive as themselves: DID identity, memory, wallet, inbox, covenants, jokes.
-
dev.charliemorrison/agent-web-reader
— last commit 2026-06-26, shares agent-economy
Pay-per-call data tools for AI agents: crypto signal, web reader, SEO audit. x402 USDC on Base.
These share tags the maintainers applied themselves, such as telegram-bot, aimarket, mcp-security, security. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: agent-economy, ai-agent, aimarket, argus, mcp, mcp-security, nodejs, security, telegram-bot, typescript, warden.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab