Home / MCP registry index / io.github.Project-Gifted1/pg1-threat-intel

PG1 Sovereign Threat Intelligence

io.github.Project-Gifted1/pg1-threat-intel in the official MCP registry. Endpoint https://pg1-ai-agent.vercel.app/api/mcp. Source: github.com/Project-Gifted1/pg1-ai-agent.

The registry describes it as: Preflight for AI agents, signed: one call; wallet, domain, IP abuse, package checks and CVEs.

We read its 21 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http pg1-threat-intel https://pg1-ai-agent.vercel.app/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "pg1-threat-intel": {
      "url": "https://pg1-ai-agent.vercel.app/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"pg1-threat-intel","type":"http","url":"https://pg1-ai-agent.vercel.app/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

preflight_check check_x402_endpoint check_agent_card check_agent_message verify_result hosting_advisor get_threat_indicators get_cve_details get_ioc_context get_cve_batch get_ioc_batch get_threat_actor_profile get_cve_by_product get_usage_status submit_indicator check_wallet_sanctions check_domain_age check_hostname_reputation check_wallet_age check_ip_abuse check_package

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-project-gifted1-pg1-threat-intel/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-project-gifted1-pg1-threat-intel)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Crypto and Web3 MCP servers · Security MCP servers