Skip to main content
Glama

cyberpulse

Access global cybersecurity intelligence: CVE briefs, vulnerability scanning, CISA KEV, OSINT, threat intel, ransomware tracking, breach checks, compliance gap analysis, dark web monitoring, and attack surface assessment.

Instructions

CyberPulse: Global cybersecurity intelligence API — CVE briefs, vulnerability scanning, CISA KEV, OSINT, threat intelligence, ransomware tracking, breach checks, compliance gap analysis, dark web monitoring, and

Coverage: Global

Endpoints: • cve-brief ($0.10): CVE deep-dive — CVSS, exploitation status, patch urgency, remediation • vuln-scan ($0.10): Vulnerability scan — all known CVEs for any software + version • cisa-kev ($0.10): CISA KEV — Known Exploited Vulnerabilities catalog search • osint ($0.10): OSINT — domain and IP intelligence for authorized defensive use • threat-intel ($0.10): Threat intelligence — global threat actors and campaigns by sector and region • ransomware-intel ($0.10): Ransomware intelligence — group profiles, victim patterns, TTPs, defensive playbook • breach-check ($0.10): Breach check — domain breach history and credential exposure intelligence • compliance-gap ($0.10): Compliance gap analysis — global security frameworks (SOC2, ISO27001, GDPR, NIS2, PDPA, POPIA, LGPD...) • dark-web-monitor ($0.10): Dark web monitor — brand and domain underground intelligence (ethical OSINT) • attack-surface ($0.10): Attack surface assessment — external risk analysis for authorized defensive use

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: cve-brief | vuln-scan | cisa-kev | osint | threat-intel | ransomware-intel | breach-check | compliance-gap | dark-web-monitor | attack-surface
langNoResponse language: en|es|fr|de|ja|zh|ko|pt|ar|hi (default: en)
cveNoCVE ID — e.g. CVE-2024-3400 | CVE-2023-44487 | CVE-2021-44228
softwareNoSoftware name — e.g. Apache Log4j | OpenSSL | Spring Boot | Ivanti Connect Secure
versionNoVersion string — e.g. 2.14.0 | 3.0.8
ecosystemNoPackage ecosystem — npm | PyPI | Maven | Go | crates.io | NuGet
vendorNoVendor/product name — e.g. Cisco | Ivanti | Microsoft | Palo Alto | Fortinet
daysNoEntries added in last N days (default: 90)
filterNoransomware | recent (alternative to vendor search)
targetNoDomain or public IP — e.g. example.com | 8.8.8.8
industryNoSector — e.g. healthcare | finance | energy | manufacturing | government | education
regionNoRegion — e.g. North America | Europe | Southeast Asia | MENA | Sub-Saharan Africa | Global (default: Global)
groupNoRansomware group name — e.g. LockBit | ALPHV | Cl0p | RansomHub (omit for landscape overview)
domainNoDomain to check — e.g. example.com
frameworkNoCompliance framework
sectorNoIndustry sector — e.g. healthcare | finance | SaaS | e-commerce
brandNoBrand name or domain — e.g. acme.com | MyCompany
companyNoCompany name — e.g. Acme Corporation
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It mentions costs per call and 'authorized defensive use' for OSINT, but lacks details on authentication, rate limits, data sources, or limitations of the API, which are critical for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very long and unstructured, mixing marketing language with endpoint details. Key information is not front-loaded, and the block of text reduces readability for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 18 parameters and no output schema, the description should explain when to use each action and which parameters apply. It lists endpoints but fails to provide conditional logic or usage patterns, leaving gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds some context (e.g., specific CVE examples) but does not substantially enhance parameter meaning beyond schema descriptions. It does not clarify parameter relationships per action.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it's a global cybersecurity intelligence API with listed endpoints, clearly indicating it provides CVE briefs, vulnerability scanning, etc. It distinguishes from sibling 'pulse' tools by focusing on cybersecurity, but the verb 'cyberpulse' is not a single action, making it slightly less specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus other 'pulse' siblings. The description lists endpoints but does not provide decision criteria or mention alternatives, leaving the agent without explicit usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server