More screenshots
Works with the AI Agents you already use
mcp audit
Audits a live MCP server the way a real client would, then scans its repo for leaked credentials.
$20
mcp audit
Example session with this skill installed
Audit my local filesystem MCP server. Check for tool health and scan the repo for any leaked credentials or path issues.
- Read your context and instructions
- Compiled the mcp audit
I have completed the audit of the local filesystem MCP server. The server was initialized over stdio, and all 4 advertised tools were probed for health and schema consistency. I also performed a fingerprint scan across the git history and environment files. ## MCP Audit Results ### Tool Health Summary | Total Tools | Healthy | Degraded | Failed | | :--- | :--- | :--- | :--- | | 4 | 3 | 1 | 0 | ### Detailed Findings | Category | Tool / Location | Severity | Issue | Recommended Fix | | :--- | :--- | :--- | :--- | :--- | | **Dispatcher** | `read_file` | High | `inputSchema` defines `encoding` but function signature lacks the parameter. | Add `encoding: str = "utf-8"` to function signature. | | **Path** | `server.py:42` | Medium | Hard-coded path `/etc/zypp/` found; fails on non-SUSE environments. | Use `os.path.join` and verify via `shutil.which`. | | **Leak** | `.env.backup` | Critical | `PUBLISHED`: Found `ghp_` prefix fingerprint in git history. | Rotate GitHub token and update `.gitignore`. | | **Dependency** | `search_grep` | Low | Uses `which grep` shell-out; risk of false negatives. | Replace with `shutil.which('grep')`. | ### Summary - **Overall Risk:** Critical (Credential leak detected in history) - **Remediation:** Immediate rotation of the identified GitHub token is required. The `read_file` dispatcher drift is causing runtime `TypeError` exceptions for clients attempting to specify encoding. **Next steps** 1. Run `git filter-repo` to purge the identified secret fingerprint from history. 2. Synchronize the `read_file` function signature with its advertised JSON schema. 3. Update path references to use dynamic resolution for cross-platform support.
Connects securely to your tools. The creator never sees your data.
About this skill
Most MCP servers are never exercised the way an actual client would exercise them. Tool schemas are declared in one location and dispatched to handlers in another, and nothing enforces that the two stay in sync — that disconnect is exactly where MCP servers fail without warning. This skill evaluates an MCP server by acting as a live client, then inspects its repository for credentials that shouldn't be exposed. It provides two working shell scripts alongside the methodology behind them — the same approach that produced real upstream fixes (three broken tools repaired with regression tests during a live SUSE MCP server audit).
Read-only by default. Does not perform network exfiltration tests. Does not classify correctness bugs as security CVEs. Fingerprint scan is limited to known secret shapes and env variables.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago