MCP servers observed by Lowdown
io.github.Project-Gifted1/pg1-threat-intel MCP server: daily status and tool changes
No successful response on the last 3 consecutive checks (2026-11-13 to 2026-11-19) (Lowdown checks this server every 3 days). Checked from one network location. 3 of 4 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Project-Gifted1/pg1-threat-intel
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Project-Gifted1/pg1-threat-intel?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server did not respond.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 1
- Required authentication: 0
- No response: 3
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
What tools does it list?
21 tools on 2026-11-10:
check_agent_cardcheck_agent_messagecheck_domain_agecheck_hostname_reputationcheck_ip_abusecheck_packagecheck_wallet_agecheck_wallet_sanctionscheck_x402_endpointget_cve_batchget_cve_by_productget_cve_detailsget_ioc_batchget_ioc_contextget_threat_actor_profileget_threat_indicatorsget_usage_statushosting_advisorpreflight_checksubmit_indicatorverify_result
MCP Registry declaration
- Registry name:
io.github.Project-Gifted1/pg1-threat-intel - Declared version: 1.21.1
- Status: active
- Declared hosts:
pg1-ai-agent.vercel.app
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.Project-Gifted1/pg1-threat-intel", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Project-Gifted1/pg1-threat-intel?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).