Gti MCP Server

gti-mcp PyPI v0.1.3

Published by google — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Google Threat Intelligence MCP server

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 36

Each tool and what it can reach — statically extracted from the published source.

  • get_collection_timeline_eventsingests untrusted input
  • analyse_fileno sensitive capability
  • create_collectionno sensitive capability
  • get_collection_feature_matchesno sensitive capability
  • get_collection_mitre_treeno sensitive capability
  • get_collection_reportno sensitive capability
  • get_collection_rulesno sensitive capability
  • get_collections_commonalitiesno sensitive capability
  • get_domain_reportno sensitive capability
  • get_entities_related_to_a_collectionno sensitive capability
Show 26 more tools ↓
  • get_entities_related_to_a_domainno sensitive capability
  • get_entities_related_to_a_fileno sensitive capability
  • get_entities_related_to_a_hunting_rulesetno sensitive capability
  • get_entities_related_to_an_ip_addressno sensitive capability
  • get_entities_related_to_an_urlno sensitive capability
  • get_file_behavior_reportno sensitive capability
  • get_file_behavior_summaryno sensitive capability
  • get_file_reportno sensitive capability
  • get_hunting_rulesetno sensitive capability
  • get_ip_address_reportno sensitive capability
  • get_threat_profileno sensitive capability
  • get_threat_profile_associations_timelineno sensitive capability
  • get_threat_profile_recommendationsno sensitive capability
  • get_url_reportno sensitive capability
  • list_threat_profilesno sensitive capability
  • search_campaignsno sensitive capability
  • search_digital_threat_monitoringno sensitive capability
  • search_iocsno sensitive capability
  • search_malware_familiesno sensitive capability
  • search_software_toolkitsno sensitive capability
  • search_threat_actorsno sensitive capability
  • search_threat_reportsno sensitive capability
  • search_threatsno sensitive capability
  • search_vulnerabilitiesno sensitive capability
  • update_collection_attributesno sensitive capability
  • update_iocs_in_collectionno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.3 latest A 96/100 0 1.13.0 2026-08-28
v0.1.2 A 96/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/gti-mcp/badge.svg)](https://mcptrustchecker.com/registry/gti-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/gti-mcp"><img src="https://mcptrustchecker.com/registry/gti-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/gti-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan gti-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools