ArcGIS MCP Bridge

Secure, local-first MCP server exposing ArcGIS Pro's ArcPy engine over stdio JSON-RPC.

MCP Servers Python Listed Apache-2.0

Is ArcGIS MCP Bridge safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.2 / 10
Provenance None
Signed commits 44%
Last push yesterday
Compare ArcGIS MCP Bridge
Suggest a correction

In detail: ArcGIS MCP Bridge scores 59.5/100 (Grade C), ranked #647 of 1325 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 6.2/10; 44% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How ArcGIS MCP Bridge compares in MCP Servers

  1. #357 MCP Imagenate 59.6 +0.1
  2. #358 Funplay Cocos MCP 59.6 +0.1
  3. #359 ArcGIS MCP Bridge 59.5 this agent
  4. #360 Buildkite MCP Server 59.5 ±0
  5. #361 Laravel MCP Companion 59.4 −0.1

Bars show each HVTrust score; the tick marks ArcGIS MCP Bridge’s 59.5.

Where the 59.5 comes from

HVTrust dimensions vs the MCP Servers average

59.5 / 100 · 100.0% confidence

ArcGIS MCP Bridge MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.9 / 25
in line with avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
1.6 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.9 / 20
0.8 above avg 12.1
AdoptionLog-scaled stars · package downloads
6.1 / 20
1.1 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-26
Rank Moved
Rank rose 29 spots (#676 → #647)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
40.2
Activity sub-score · out of 100
#359

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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
19
Forks
1
Last Push
2026-09-25
yesterday
Commits (4 wk)
2?
Downloads (7d)
161
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▲29
was #676

Analysis

Activity Inputs

40.2 / 100
StarsRepository reach
7.8 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
1.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.2 / 10
OpenSSF Scorecard · scanned Sep 15, 2026
Signed Commits
44%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 10
Security-Policy 4
Signed-Releases 0
Token-Permissions 9
Vulnerabilities 10

Common questions about ArcGIS MCP Bridge

ArcGIS MCP Bridge has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does ArcGIS MCP Bridge publish package provenance?
No published build provenance is currently detected for ArcGIS MCP Bridge. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does ArcGIS MCP Bridge have an OpenSSF Scorecard?
ArcGIS MCP Bridge has an OpenSSF Scorecard score of 6.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is ArcGIS MCP Bridge actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does ArcGIS MCP Bridge use?
ArcGIS MCP Bridge ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ArcGIS MCP Bridge's commits signed?
43% of the last 100 commits to ArcGIS MCP Bridge are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
high confidence
Implemented
ArcGIS MCP Bridge appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to ArcGIS MCP Bridge'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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain ArcGIS MCP Bridge?

For maintainers

HVTrust scores ArcGIS MCP Bridge 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
Rank 24HVTrust 4Listed 2Score 2Grade 2Scorecard 1Delisted 1MCP 1
2026-09-26
Rank Moved
Rank rose 29 spots (#676 → #647)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 245 spots (#908 → #663)
2026-09-23
HVTrust Changed
HVTrust up 31.8pts (26.6 → 58.4)
2026-09-22
Newly Listed
First tracked at rank #908
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 115 spots (#766 → #651)
2026-09-19
HVTrust Changed
HVTrust up 3.5pts (55.2 → 58.7)
2026-09-19
Activity Score Changed
Activity score up 10pts (28 → 38)
2026-09-16
Rank Moved
Rank rose 12 spots (#775 → #763)
2026-09-12
Rank Moved
Rank rose 48 spots (#808 → #760)
2026-09-11
Rank Moved
Rank dropped 12 spots (#796 → #808)
2026-09-09
Rank Moved
Rank dropped 13 spots (#783 → #796)
2026-09-07
Rank Moved
Rank dropped 36 spots (#739 → #775)
2026-09-06
Rank Moved
Rank dropped 51 spots (#688 → #739)
2026-09-05
Rank Moved
Rank dropped 87 spots (#601 → #688)
2026-09-04
Grade Changed
Trust grade D → C
2026-09-04
Rank Moved
Rank rose 483 spots (#1084 → #601)
2026-09-04
HVTrust Changed
HVTrust up 18.1pts (37.4 → 55.5)
2026-09-03
Rank Moved
Rank dropped 55 spots (#1029 → #1084)
2026-09-02
Rank Moved
Rank dropped 42 spots (#987 → #1029)
2026-09-01
Scorecard Added
OSSF Scorecard: 5.4/10
2026-09-01
Rank Moved
Rank rose 236 spots (#1223 → #987)
2026-09-01
HVTrust Changed
HVTrust up 17.1pts (20.4 → 37.5)
2026-08-31
Rank Moved
Rank dropped 22 spots (#1201 → #1223)
2026-08-30
Rank Moved
Rank dropped 22 spots (#1179 → #1201)
2026-08-29
Rank Moved
Rank dropped 42 spots (#1137 → #1179)
2026-08-29
Activity Score Changed
Activity score down 5pts (38 → 33)
2026-08-28
Rank Moved
Rank dropped 26 spots (#1111 → #1137)
2026-08-27
Rank Moved
Rank dropped 13 spots (#1098 → #1111)
2026-08-26
Rank Moved
Rank dropped 74 spots (#1024 → #1098)
2026-08-24
Rank Moved
Rank dropped 12 spots (#1010 → #1022)
2026-08-19
Rank Moved
Rank dropped 23 spots (#991 → #1014)
2026-08-16
Rank Moved
Rank dropped 28 spots (#963 → #991)
2026-08-10
Rank Moved
Rank dropped 57 spots (#900 → #957)
2026-08-08
Newly Listed
First tracked at rank #892

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 59.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/arcgis-mcp-bridge.svg)](https://hvtracker.net/agents/arcgis-mcp-bridge)
HTML:
<a href="https://hvtracker.net/agents/arcgis-mcp-bridge"><img src="https://hvtracker.net/badge/arcgis-mcp-bridge.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON