agentseal-mcp-intel
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agentseal-mcp-intel Check if server-filesystem is safe to install"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
agentseal-mcp-intel
Security scanner for MCP servers. Check any MCP server for supply-chain threats before you install it -- directly from Claude, Cursor, or Windsurf.
The problem
MCP servers can read your files, run commands, and call APIs on your behalf. Before you install one, you should know:
Does it exfiltrate data to external servers?
Does it contain prompt injection or jailbreak payloads?
Does it request excessive permissions?
Has it been independently tested?
Most people install MCP servers blindly. This tool changes that.
Related MCP server: tooltrust-mcp
What it does
agentseal-mcp-intel connects your AI assistant to the AgentSeal security registry -- 3,400+ MCP servers each tested with 265+ adversarial security probes. Your assistant can look up any server, scan your environment, and flag risks before you install anything.
Quick start
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"agentseal": {
"command": "npx",
"args": ["-y", "agentseal-mcp-intel"]
}
}
}Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"agentseal": {
"command": "npx",
"args": ["-y", "agentseal-mcp-intel"]
}
}
}Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"agentseal": {
"command": "npx",
"args": ["-y", "agentseal-mcp-intel"]
}
}
}Restart your AI tool. That's it.
Tools
Tool | What it does | Network |
Find safe MCP servers by use case | API call | |
Check a specific server's security score before installing | API call | |
Scan all servers installed in your AI tools | API call (names only) | |
Analyze an AI config file for hidden threats | 100% local | |
Submit an unknown server for scanning | API call |
search_registry
Find MCP servers by what you need. Results include trust scores so you can pick a safe option.
"Find me a PostgreSQL MCP server"
"Search for web scraping MCP servers with a score above 70"Parameter | Type | Required | Description |
| string | Yes | What you need, e.g. "PostgreSQL", "web scraping", "send email" |
| string | No | Filter by category |
| boolean | No | Only return servers scoring 70+ |
| number | No | Max results (default: 10, max: 20) |
check_server
Check the security of a specific MCP server before installing it. Accepts package names, slugs, or GitHub URLs.
"Is @modelcontextprotocol/server-github safe?"
"Check the security of https://github.com/crystaldba/postgres-mcp"
"Check mcp-server-postgres before I install it"Returns:
Trust score (0-100) with risk level
Score breakdown across 5 dimensions (description safety, schema safety, capability risk, auth & permissions, stability)
Security findings with severity ratings
Install links and metadata
Risk level | Score | Meaning |
EXCELLENT | 85-100 | No significant issues found |
HIGH | 70-84 | Minor issues, generally safe |
MEDIUM | 50-69 | Review findings before installing |
LOW | 30-49 | Significant concerns, use with caution |
CRITICAL | 0-29 | Do not install |
check_environment
Scan all MCP servers currently installed in Claude Desktop, Cursor, and Windsurf. Checks each one against the registry and groups results by risk level.
"Scan my installed MCP servers for security issues"
"Check my Cursor MCP setup"Parameter | Type | Required | Description |
| string | No | Which tool to scan: |
| boolean | No | Preview what would be scanned without making API calls |
Privacy: Only server names are sent to the API. Config file paths, environment variables, API keys, and credentials never leave your machine.
check_file
Analyze an AI config file for hidden security threats. Runs entirely locally -- zero data is sent anywhere.
"Check my .cursorrules file for threats"
"Scan CLAUDE.md for prompt injection"Detects:
Prompt injection and jailbreak patterns
Invisible Unicode characters (zero-width joiners, Unicode tags, BiDi overrides)
Data exfiltration instructions (URL variable interpolation, fetch + secrets)
Base64-encoded payloads
Unsafe auto-approve permissions
Supported files |
|
|
|
|
|
check_fileonly accepts known AI config file patterns. Requests for arbitrary files (e.g./etc/passwd,~/.ssh/id_rsa) are rejected.
submit_server
Submit an MCP server that's not in the registry for security scanning. AgentSeal fetches it, runs 265+ probes, and publishes results.
"Submit mcp-server-postgres for scanning"
"Scan https://github.com/org/repo and add it to the registry"Parameter | Type | Required | Description |
| string | Yes | Package name or GitHub URL |
| string | Yes |
|
| boolean | Yes | Must be |
Requires explicit confirmation. Your AI assistant cannot submit servers without you approving it first.
Example session
You: Check if the GitHub MCP server is safe to install.
Claude: [calls check_server("@modelcontextprotocol/server-github")]
[AgentSeal] server-github ~ HIGH -- 82/100
████████████████░░░░ 82/100
TypeScript . MIT . 18 tools . by modelcontextprotocol
SCORE BREAKDOWN
Desc Safety ▪▪▪▪▪▪▪▪▪▪ 95
Schema Safety ▪▪▪▪▪▪▪▪·· 80
Capability ▪▪▪▪▪▪▪··· 72
Auth & Perms ▪▪▪▪▪▪▪▪·· 78
Stability ▪▪▪▪▪▪▪▪▪▪ 100
FINDINGS
0 critical . 1 high . 1 medium
You: Scan all my installed MCP servers.
Claude: [calls check_environment()]
ENVIRONMENT SCAN -- 4 servers across 2 config files
SAFE
server-github 82/100 HIGH
server-filesystem 78/100 HIGH
REVIEW
mcp-server-browserbase 54/100 MEDIUM (1 finding)
UNKNOWN
some-custom-mcp NOT IN REGISTRY
ACTION REQUIRED
Run check_server("some-custom-mcp") or submit it for scanning.Privacy and data handling
Action | What is read locally | What is sent to agentseal.org | What stays on your machine |
| Nothing | Search query | -- |
| Nothing | Server name/slug | -- |
| AI tool config files | Server names only | File paths, env vars, API keys, all config values |
| The specified config file | Nothing | Full file contents |
| Nothing | Package name + type | -- |
No telemetry. No usage tracking, no analytics, no background network calls.
Credentials never leave your machine. Config parsing extracts only server names.
check_fileis 100% local. File contents are never transmitted.External content is isolated. API responses are wrapped in
<agentseal:external>delimiters so your AI assistant treats them as data, not instructions.Source code is fully auditable. You're looking at it.
Configuration
Environment variable | Default | Description |
| -- | Pro API key for unlimited access and full findings detail |
|
| Override API base URL |
|
| Set to |
| -- | Extra config file path for |
Free vs Pro
Free | Pro | |
Requests | 50/day | Unlimited |
Trust scores | Yes | Yes |
Finding counts | Yes | Yes |
Finding details (evidence, remediation) | -- | Yes |
Priority scanning | -- | Yes |
Get a Pro key at agentseal.org/pricing.
Requirements
Node.js 18 or later
An MCP-compatible host: Claude Desktop, Cursor, Windsurf, or any MCP client
Development
git clone https://github.com/agentseal/agentseal-mcp-intel.git
cd agentseal-mcp-intel
npm install
npm run build
npm test # 133 tests
npm run typecheck # strict TypeScriptHow it works
Your AI assistant agentseal-mcp-intel AgentSeal API
| | |
|-- "check postgres-mcp" --------->| |
| |-- GET /api/v1/mcp/intel/... ->|
| |<-- trust score + findings ----|
|<-- formatted security report ----| |
| | |
|-- "scan my .cursorrules" ------->| |
| |-- [local analysis only] |
|<-- findings (no network call) ---| |The MCP server is a thin, auditable client. All scoring intelligence lives in the AgentSeal API. Local analysis (check_file) runs entirely on your machine with zero network calls.
Security
If you find a security vulnerability, please email hello@agentseal.org instead of opening a public issue.
License
FSL-1.1-Apache-2.0 -- Functional Source License 1.1.
You may use and modify this software, but you cannot offer it as a competing commercial service. After 4 years, the license converts to Apache 2.0. The AgentSeal registry, probe suite, and scoring engine are proprietary. See fsl.software for details.
Available Tools
5 toolscheck_environmentA
Scan MCP servers currently installed in your AI tools (Claude Desktop, Cursor, Windsurf) and check each one against the AgentSeal registry. Shows trust scores and flags risky or unknown servers. Only server names are sent to the API - credentials and config values stay local.
Inputs: scope, dry_run.
check_fileA
Analyze an AI config file for hidden security threats: prompt injection, invisible characters, data exfiltration instructions, jailbreak patterns. Supported files: .cursorrules, CLAUDE.md, .github/copilot-instructions.md, .windsurfrules, .mcp.json. Runs entirely locally.
Inputs: path (required).
check_serverA
Check the security of a specific MCP server. Returns a trust score (0-100), risk level, score breakdown, and security findings from 265+ automated probes. Useful before installing or recommending an MCP server.
Inputs: name (required).
search_registryA
Search the AgentSeal security registry of 3,400+ scanned MCP servers. Returns trust scores (0-100) and security ratings from 265+ automated probes. Useful when the user asks to find, discover, or recommend MCP servers.
Inputs: query (required), category, safe_only, limit.
submit_serverA
Submit an MCP server that's not in the AgentSeal registry for security scanning. AgentSeal will fetch it, run 265+ security probes, and add results to the public registry. Requires confirmed=true to prevent accidental submissions.
Inputs: name (required), package_type (required), confirmed (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct operation: scanning environments, files, specific servers, registry search, and submissions. No functional overlap exists.
All tools follow a consistent 'verb_noun' pattern (check_environment, check_file, check_server, search_registry, submit_server) with clear, action-oriented names.
Five tools precisely cover the core workflows of security scanning: environment audit, file analysis, server checks, registry search, and submission. Neither too few nor too many.
The tool set provides complete lifecycle coverage for the domain: check existing servers (environment, file, server), discover new ones (search_registry), and add missing ones (submit_server). No obvious gaps.
Maintenance
Related MCP Connectors
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Audit your MCP servers for poisoned tools and leaked secrets, and check AI-generated code for flaws.
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
Scan AI agent skills, MCP server packages and MCP configs before you install them. Static analysis.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceSecurity scanner for MCP servers and AI-generated code. Detects leaked API keys, PII, prompt injection, and MCP misconfigs with A-F security grades.MIT
- AlicenseNot gradedqualityBmaintenanceScans MCP servers for prompt injection, supply chain attacks, excessive permissions, and code execution risks. Includes an offline blacklist that catches known-compromised packages like LiteLLM 1.82.7/1.82.8 and Trivy with zero latency.19MIT
- AlicenseNot gradedqualityCmaintenanceScans MCP servers, AI agent skills, and plugins for 68+ malicious patterns including credential exfiltration, prompt injection, and code execution.65 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables scanning MCP server configurations for security risks like prompt injection, hardcoded secrets, and dangerous commands, providing risk scores and detailed reports before connecting to an AI coding assistant.16 npmMIT