Google Knowledge Graph MCP
Website
MCP server for Google's free public Knowledge Graph Search API - search for structured entity information about people, places, organizations, and concepts
Is Google Knowledge Graph MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Google Knowledge Graph MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Google Knowledge Graph MCP scores 55.5/100 (Grade C), ranked #838 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.6/10; 8% of recent commits are signed; no published advisory affects its latest release (@houtini/google-knowledge-graph-mcp); last pushed 2026-11-07. Every point is earned from checkable signals — never paid placement. How scoring works →
How Google Knowledge Graph MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 70.2 B · #222 of 778
- Raise the OSSF Scorecard from 5.6 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +7.1 → 62.6 C · #342 of 778
- Sign every commit8% signed today +4.6 → 60.1 C · #380 of 778
Chain of custody
Scanners check what the code says. This traces who ships Google Knowledge Graph MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/houtini-ai/google-knowledge-graph-mcp, MIT, last pushed 2026-11-07. 8% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 0CII-Best-Practices 0Code-Review 0Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 10Vulnerabilities 10 -
Published packages Linked, not attested
- npm @houtini/google-knowledge-graph-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: @houtini/google-knowledge-graph-mcp 1.0.10. No published advisory affects it (OSV, checked 2026-11-10).
Changes to this chain
- 2026-08-28 OSSF Scorecard: 3.4/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Google Knowledge Graph MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Google Knowledge Graph MCP compares in MCP Servers
- #459 Blender MCP 55.6 +0.1
- #460 MCP For Stata 55.5 ±0
- #461 Google Knowledge Graph MCP 55.5 this agent
- #462 MCP NixOS 55.5 ±0
- #463 Kernel MCP Server 55.2 −0.3
Bars show each HVTrust score; the tick marks Google Knowledge Graph MCP’s 55.5.
Where the 55.5 comes from
HVTrust dimensions vs the MCP Servers average
55.5 / 100 · 100.0% confidenceGoogle Knowledge Graph MCP MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
44.6 / 100Common questions about Google Knowledge Graph MCP
Does Google Knowledge Graph MCP publish package provenance?
Does Google Knowledge Graph MCP have an OpenSSF Scorecard?
Is Google Knowledge Graph MCP actively maintained?
What license does Google Knowledge Graph MCP use?
Are Google Knowledge Graph MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Google Knowledge Graph MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Google Knowledge Graph MCP?
For maintainers
HVTrust scores Google Knowledge Graph MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/google-knowledge-graph-mcp)
<a href="https://hvtracker.net/agents/google-knowledge-graph-mcp"><img src="https://hvtracker.net/badge/google-knowledge-graph-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON