agentaegis

Tools

28 tools: 26 read-only, 2 change data, 0 high risk (delete, pay, send or run code).

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 7,906 tokens of tool definitions and a 116 ms handshake.

• changes datavuln_scan_networkDiscover open ports, running services and known vulnerabilities on an IP or domain (nmap). SENDS REAL TRAFFIC to the target and may trigger intrusion detection - only run against hosts the caller owns or is explicitly authorized to test, and confirm that first. Pass async:true to get a job_id to ...
• changes datavuln_scan_web_appScan a web application for OWASP Top 10 issues and known CVEs (Nuclei). SENDS REAL TRAFFIC to the target - authorized targets only, confirm before calling. Pass async:true to get a job_id to poll instead of blocking. Costs $5 per call.
• read-onlycompliance_framework_checkAssess an organization's security posture against a compliance framework (SOC 2, ISO 27001, HIPAA, PCI-DSS, NIST CSF) and report per-control status. Use this FIRST when asked whether the org is audit-ready; control_gap_analysis builds on its output. Costs $2 per call.
• read-onlyevidence_collectBuild an evidence-collection plan for specific compliance controls: what artifact each control needs, where it comes from, and what makes it sufficient. Use when preparing for a real audit, after the gaps are known. Plans the collection; does not gather evidence for you. Costs $1 per call.
• read-onlycontrol_gap_analysisTurn unmet compliance controls into a prioritized remediation roadmap with effort estimates. Use after compliance_framework_check to answer 'what do we fix first'. Costs $2 per call.
• read-onlyaudit_report_generateSynthesize findings into an audit-ready compliance report. Use at the END of an engagement, once gaps are closed. If the user only wants to know where they currently stand, run compliance_framework_check instead - it costs less and answers that question directly. Costs $5 per call.
• read-onlypolicy_generateGenerate a tailored written security policy (incident response, access control, encryption, vendor management, remote work, and similar). Use when a control gap specifically calls for documented policy. Costs $2 per call.
• read-onlyvuln_prioritizeRank vulnerabilities you already have by exploitability and business impact, and group them into remediation actions. Analyzes findings you supply; it discovers nothing on its own. Costs $1 per call.
• read-onlycve_lookupLook up one CVE by identifier: CVSS score and vector, affected products, patch availability and references. Use when a specific CVE ID is already known. Costs $1 per call.
• read-onlyssl_tls_auditAudit a domain's TLS configuration (sslyze): certificate validity and expiry, protocol versions, cipher suites, and known TLS weaknesses. Passive - safe against any host. Costs $1 per call.
• read-onlysast_scanStatic analysis of source code or an https git repo for security flaws (Semgrep): injection, unsafe deserialization, path traversal, crypto misuse. Python, JS/TS, Java, Go, Ruby, PHP, C/C++. For code LOGIC flaws - use secret_scan for hardcoded credentials and dependency_audit for vulnerable packa...
• read-onlysecret_scanDetect hardcoded credentials, API keys and tokens in source code or an https git repo (trufflehog), verified against the issuing provider where supported. Use when the question is 'did we commit a secret'. Costs $2 per call.
• read-onlydependency_auditAudit a dependency manifest or https git repo for known-vulnerable packages (trivy): npm, pip, Go, Ruby, Java, Cargo. The cheapest, highest-signal first step when assessing an unfamiliar repository. Costs $2 per call.
• read-onlyincident_triageClassify a security incident and produce severity, likely category, containment steps and a response plan. Use when something has already happened. If all you have is a suspicious IP or domain, run threat_intel_lookup first - it is cheaper and may settle the question. Costs $3 per call.
• read-onlythreat_intel_lookupReputation and indicator lookup for an IP or domain across AbuseIPDB, AlienVault OTX and abuse.ch. The cheapest way to check whether an indicator is known-bad. Interpret with care: large CDN, cloud and payment infrastructure routinely returns reputation hits, so only a curated active-malware hit ...
• read-onlydns_security_checkCheck a domain's DNS security records - SPF, DKIM, DMARC, DNSSEC - and grade the configuration. Passive. Covers the records themselves; for full spoofability posture use email_security_audit. Costs $1 per call.
• read-onlyemail_security_auditFull email-security posture for a domain: whether mail from it can be spoofed, with DMARC/SPF/DKIM alignment and policy strength. A superset of dns_security_check for the email question specifically. Costs $2 per call.
• read-onlyaccess_reviewReview user and role assignments you supply against least-privilege, flagging excessive, stale or orphaned access. Analyzes data the caller provides; it does not connect to an identity provider. Costs $1 per call.
• read-onlymfa_auditAssess MFA coverage and factor strength across a user or configuration set you supply, flagging unenrolled accounts and weak factors such as SMS. Analyzes data the caller provides; it does not connect to an identity provider. Costs $1 per call.
• read-onlycredential_checkCheck whether an email address or domain appears in known credential-breach corpora (Have I Been Pwned), with the breaches and data classes exposed. Use when assessing account-takeover exposure. Costs $2 per call.
• read-onlyvet_endpointComposite trust verdict (PROCEED/CAUTION/BLOCK) for an endpoint an agent is about to call or pay - combines TLS/cert health, DNS hygiene, threat-intel reputation, and domain age into one decision with reasons. Prefer this over running ssl_tls_audit + dns_security_check + threat_intel_lookup separ...
• read-onlyscan_mcp_pluginScan an MCP server (git repo or code) for supply-chain risk BEFORE trusting it - exfiltration (secrets/env to the network), prompt-injection sinks, dangerous capabilities, npm install hooks, obfuscation, plus Semgrep + secret scanning → a PROCEED/CAUTION/BLOCK verdict with findings. Costs $5 per ...
• read-onlyscan_skillScan an agent SKILL (git repo or SKILL.md) for supply-chain risk BEFORE trusting it - prompt-injection / hidden-unicode in the instructions (hard block), over-broad allowed-tools grants, plus exfiltration, dangerous capabilities, secrets and obfuscation in bundled scripts → a PROCEED/CAUTION/BLOC...
• read-onlyaccount_balanceReturns the calling API key's prepaid balance, monthly limit, current month usage, and a breakdown of how many of each tool the customer can still afford. Free to call.
• read-onlyhelpReturns AgentAegis FAQ - authentication, balance/billing, tool catalog, async jobs, error codes, x402, rate limits, security. Optional topic filter. Free to call.
• read-onlyagent_whoamiReturns your persistent AgentAegis agent identity (agent_id), how you're identified (API key / wallet / anonymous session), and lifetime call count + spend. Free to call.
• read-onlyagent_historyLists your recent scans (scan_id, tool, target, status, time) so you can retrieve or chain from a prior result. Optional limit/tool/target/since filters. Free to call.
• read-onlyagent_scan_getRetrieves one of your prior scans by scan_id, including the stored full output, so you can build on earlier results without re-paying. Free to call.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-05, 116 ms.

From one check a day over the last 4 days. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-062026-10-05

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Developer tools and code, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/agentaegis-mcp-production.up.railway.app/mcp.svg)](https://7it.co.il/7maps/s/agentaegis-mcp-production.up.railway.app/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=agentaegis-mcp-production.up.railway.app%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/agentaegis-mcp-production.up.railway.app/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/agentaegis-mcp-production.up.railway.app/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=agentaegis-mcp-production.up.railway.app%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.