Pulsedive MCP — threat-intelligence IOC enrichment (pulsedive.com)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 33 tools
Most tools have distinct targets and the heavily documented descriptions clarify boundaries, but there is genuine overlap: ask_pipeworx, ask_pipeworx_beta (explicitly identical to ask_pipeworx today), and ask_pipeworx_grounded are three variants of the same router; deep_research also overlaps with ask_pipeworx; polymarket_edges and polymarket_arbitrage both emit partition-overround signals; entity_profile and recent_changes both profile a company. An agent can usually pick correctly from the prose, but the surface invites misselection.
Nearly everything is snake_case with a clean domain-prefix scheme (polymarket_*, pulsedive_*, ask_pipeworx*) and verb_noun patterns (compare_entities, resolve_entity, validate_claim, discover_tools, list_subscriptions). Minor deviations exist where noun-first forms appear (entity_profile, recent_alerts, polymarket_edges) alongside verb-first ones, but the convention is predictable overall.
33 tools is heavy for any single server and includes several near-duplicates (three ask_pipeworx variants, five polymarket tools, overlapping entity/research tools). While the underlying gateway scope is broad, the count far exceeds a well-scoped set and adds selection cost without proportional capability.
Core lifecycle surfaces are covered: memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list_subscriptions/recent_alerts), research and comparison, entity resolution, and threat-intel search+lookup via the two pulsedive tools. Gaps are minor — no per-subscription edit/get, no threat/feed enumeration beyond explore, and some packages are marked experimental/sunset — but agents can work around them.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."entity_profile3 fields changedInput schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."Input schema / properties / type / enumPrevious value: -[
- "company"
-]New value: +[
+ "company",
+ "ticker"
+]Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."Enrich, search, assess, and manage threat intelligence through 80+ typed MCP tools.
ThreatFox MCP — abuse.ch indicator-of-compromise feed (free, key required)
VirusTotal MCP — file / URL / domain / IP reputation (BYO key)
AlienVault OTX MCP — Open Threat Exchange (free with key)
Add one secure layer between your agents and this server.
