A
licenseA
qualityD
maintenanceDependency security & health auditing for AI agents with no account or API key required.
2
2
MIT
Security Intel MCP
Server Details
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- datakoot/security-intel-mcp
- GitHub Stars
- 0
- Server Listing
- Security Intel MCP
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
5 tool updates
- Changed
audit_dependencies5 fields changed- added
Input schema / properties / dependenciesAdded value: +{ + "description": "[{name, version}] entries", + "items": { + "type": "object" + }, + "type": "array" +} - added
Input schema / properties / ecosystemAdded value: +{ + "description": "Default npm", + "type": "string" +} - removed
Input schema / properties / formatRemoved value: -{ - "description": "Optional: npm | pypi | go. Auto-detected if omitted.", - "type": "string" -} - changed
Input schema / properties / manifest / descriptionPrevious value: -"Full contents of a package.json, requirements.txt, or go.mod file"New value: +"Raw package.json contents" - changed
Input schema / requiredPrevious value: -[ - "manifest" -]New value: +[]
- Changed
cve_lookup2 fields changed- changed
Input schema / properties / cve_id / descriptionPrevious value: -"CVE identifier, e.g. CVE-2021-44228"New value: +"e.g. CVE-2021-44228" - removed
Input schema / properties / cve_id / patternRemoved value: -"^CVE-\\d{4}-\\d{4,}$"
- Removed
ip_reputation - Changed
package_vulnerabilities3 fields changed- removed
Input schema / properties / ecosystem / descriptionRemoved value: -"Package ecosystem: npm, PyPI, Go, Maven, crates.io, RubyGems, Packagist, NuGet, Hex, Pub, Debian, Alpine" - removed
Input schema / properties / name / descriptionRemoved value: -"Package name, e.g. lodash or org.apache.logging.log4j:log4j-core" - changed
Input schema / properties / version / descriptionPrevious value: -"Exact version to check (optional; omit to list all known vulns)"New value: +"Optional; if given, only vulns affecting that version are returned"
- Removed
url_check
1 tool update
- Added
audit_dependencies
4 tool updates
- First observed
cve_lookup - First observed
ip_reputation - First observed
package_vulnerabilities - First observed
url_check
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
31Trust-check any dependency for agents: OpenSSF Scorecard, licenses, CVEs, deps. 7 ecosystems.
Pay-per-call cybersecurity for AI agents: vuln scans, threat intel, compliance, code security.
Defensive vulnerability intelligence search across public CVE/NVD and GitHub advisory APIs with CVSS
1
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides CVE lookup, search, and exploit intelligence from public vulnerability sources (NVD, CISA KEV, EPSS) for AI agents to produce remediation guidance without consuming LLM tokens for data fetching.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides security checks for AI agents, including secret scanning, CVE lookup, and dependency vulnerability scanning, all running locally except for CVE lookups.MIT
Fetter MCPofficial
FlicenseNot gradedqualityDmaintenanceProvides real-time Python package vulnerability data, enabling AI agents to check CVEs, CVSS scores, and safe versions for informed dependency decisions.1-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
The three tools have clearly distinct purposes: auditing a dependency manifest, looking up a specific CVE by ID, and listing vulnerabilities for a particular package. No overlaps or ambiguous boundaries exist.
Naming Consistency3/5
Tool names are readable but not consistently patterned. 'audit_dependencies' uses verb_noun, 'cve_lookup' is noun_verb, and 'package_vulnerabilities' is a noun phrase, mixing conventions without being chaotic.
Tool Count4/5
Three tools is on the smaller side but appropriate for a focused security intelligence server. Each tool provides a distinct and necessary function, and the count feels lean rather than insufficient.
Completeness4/5
The domain of vulnerability intelligence is well-covered with manifest auditing, CVE details, and package lookups. Minor gaps exist (e.g., no search or advisory listing), but core workflows are supported without dead ends.