ServiceNow MCP Server

ServiceNow MCP server for Claude Code, GitHub Copilot, Codex and any MCP client: Table API, CMDB, schema, aggregates and update sets, plus four guided skills. Read-only identities see read-only tools; OAuth client credentials for headless use. Free, MIT, works on a free developer instance.

MCP Servers Python Listed MIT

Is ServiceNow MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.2 / 10
Provenance Attested
Signed commits 7%
Last push 3d ago
Advisories None known
Compare ServiceNow MCP Server
Suggest a correction

In detail: ServiceNow MCP Server scores 79.9/100 (Grade B), ranked #185 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.2/10; 7% of recent commits are signed; no published advisory affects its latest release (mcp-server-servicenow); last pushed 2026-11-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How ServiceNow MCP Server 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.

Chain of custody

Scanners check what the code says. This traces who ships ServiceNow MCP Server 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.

  1. Source Partly signed

    github.com/jschuller/mcp-server-servicenow, MIT, last pushed 2026-11-07. 7% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.2/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 4
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 5
  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: mcp-server-servicenow 0.9.3. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-06 OSSF Scorecard: 5.5/10
  • 2026-09-02 Package provenance attestation detected

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 ServiceNow MCP Server’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 ServiceNow MCP Server compares in MCP Servers

  1. #97 Search1API 80.1 +0.2
  2. #98 Reddit MCP Buddy 80.1 +0.2
  3. #99 ServiceNow MCP Server 79.9 this agent
  4. #100 Substack MCP Server 79.9 ±0
  5. #101 Memorylens MCP 79.9 ±0

Bars show each HVTrust score; the tick marks ServiceNow MCP Server’s 79.9.

Where the 79.9 comes from

HVTrust dimensions vs the MCP Servers average

79.9 / 100 · 100.0% confidence

ServiceNow MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
15.6 / 25
4.8 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
1.5 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.8 / 20
7.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.0 / 20
0.6 below avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-10
Grade Changed
Trust grade A → B
2026-11-10
Rank Moved
Rank dropped 13 spots (#172 → #185)
2026-10-30
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
63.2
Activity sub-score · out of 100
#99

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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-11-10 04:07 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
27
Forks
10
Last Push
2026-11-07
3 days ago
Commits (4 wk)
131
Downloads (7d)
410
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▼13
was #172

Analysis

Activity Inputs

63.2 / 100
StarsRepository reach
8.7 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
4.8 / 20

Common questions about ServiceNow MCP Server

Public supply-chain signals for ServiceNow MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but ServiceNow MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does ServiceNow MCP Server publish package provenance?
Yes. ServiceNow MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does ServiceNow MCP Server have an OpenSSF Scorecard?
ServiceNow MCP Server 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 ServiceNow MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does ServiceNow MCP Server use?
ServiceNow MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ServiceNow MCP Server's commits signed?
7% of the last 100 commits to ServiceNow MCP Server 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
ServiceNow MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 ServiceNow MCP Server'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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-02
Provenance Added
Package provenance attestation detected

Maintain ServiceNow MCP Server?

For maintainers

HVTrust scores ServiceNow MCP Server 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 31Grade 7HVTrust 5Provenance 2Score 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-11-10
Grade Changed
Trust grade A → B
2026-11-10
Rank Moved
Rank dropped 13 spots (#172 → #185)
2026-10-30
Grade Changed
Trust grade B → A
2026-10-30
Rank Moved
Rank rose 34 spots (#186 → #152)
2026-10-27
Grade Changed
Trust grade A → B
2026-10-27
Rank Moved
Rank dropped 18 spots (#167 → #185)
2026-10-24
Grade Changed
Trust grade B → A
2026-10-24
Rank Moved
Rank rose 27 spots (#182 → #155)
2026-10-22
Rank Moved
Rank rose 12 spots (#192 → #180)
2026-10-15
Rank Moved
Rank rose 24 spots (#220 → #196)
2026-10-13
Rank Moved
Rank rose 36 spots (#261 → #225)
2026-10-12
Rank Moved
Rank rose 193 spots (#454 → #261)
2026-10-12
HVTrust Changed
HVTrust up 8.1pts (66.4 → 74.5)
2026-10-12
Activity Score Changed
Activity score up 23pts (34 → 57)
2026-10-09
Rank Moved
Rank dropped 15 spots (#435 → #450)
2026-10-05
Rank Moved
Rank dropped 34 spots (#391 → #425)
2026-10-01
Rank Moved
Rank dropped 20 spots (#359 → #379)
2026-09-25
Rank Moved
Rank dropped 19 spots (#328 → #347)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 662 spots (#986 → #324)
2026-09-23
HVTrust Changed
HVTrust up 44.8pts (25.2 → 70.0)
2026-09-22
Newly Listed
First tracked at rank #986
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 10 spots (#317 → #327)
2026-09-13
Rank Moved
Rank dropped 11 spots (#306 → #317)
2026-09-12
Rank Moved
Rank dropped 57 spots (#249 → #306)
2026-09-12
HVTrust Changed
HVTrust down 3.1pts (73.7 → 70.6)
2026-09-12
Activity Score Changed
Activity score down 8pts (49 → 41)
2026-09-11
Rank Moved
Rank dropped 41 spots (#208 → #249)
2026-09-07
Rank Moved
Rank dropped 12 spots (#208 → #220)
2026-09-06
Scorecard Added
OSSF Scorecard: 5.5/10
2026-09-06
Grade Changed
Trust grade C → B
2026-09-06
Rank Moved
Rank rose 246 spots (#454 → #208)
2026-09-06
HVTrust Changed
HVTrust up 11.5pts (63.1 → 74.6)
2026-09-05
Rank Moved
Rank dropped 38 spots (#416 → #454)
2026-09-04
Rank Moved
Rank dropped 14 spots (#402 → #416)
2026-09-03
Rank Moved
Rank dropped 24 spots (#378 → #402)
2026-09-02
Provenance Added
Package provenance attestation detected
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 701 spots (#1079 → #378)
2026-09-02
HVTrust Changed
HVTrust up 28.4pts (33.5 → 61.9)
2026-09-01
Rank Moved
Rank dropped 45 spots (#1034 → #1079)
2026-08-31
Rank Moved
Rank dropped 33 spots (#1001 → #1034)
2026-08-30
Rank Moved
Rank dropped 51 spots (#950 → #1001)
2026-08-29
Rank Moved
Rank dropped 49 spots (#901 → #950)
2026-08-28
Rank Moved
Rank dropped 34 spots (#867 → #901)
2026-08-27
Rank Moved
Rank dropped 23 spots (#844 → #867)
2026-08-26
Rank Moved
Rank dropped 108 spots (#736 → #844)
2026-08-16
Rank Moved
Rank dropped 15 spots (#710 → #725)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 79.9 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/servicenow-mcp-server.svg)](https://hvtracker.net/agents/servicenow-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/servicenow-mcp-server"><img src="https://hvtracker.net/badge/servicenow-mcp-server.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.4 · Raw JSON