updated 2026-11-10 04:07 UTC

Jotform MCP Server

Repository
MCP Servers Listed MIT

Is Jotform MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.4 / 10
Provenance None
Signed commits 64%
Last push 7d ago
Compare Jotform MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Jotform MCP Server scores 48.2/100 (Grade D), ranked #1061 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.4/10; 64% of recent commits are signed; last pushed 2026-11-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Jotform 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Jotform MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

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

  2. Review and release Weak

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

    • Code Review2
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 2
    Contributors 3
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 5
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10

  3. Published packages None

    No registry package. Jotform MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 3.0/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Jotform 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.

Signed credential (JSON) How to verify

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

  1. #596 Nouz 48.3 +0.1
  2. #597 MCPSpend 48.2 ±0
  3. #598 Jotform MCP Server 48.2 this agent
  4. #599 MCP Unity 48.1 −0.1
  5. #600 Druid MCP Server 48.0 −0.2

Bars show each HVTrust score; the tick marks Jotform MCP Server’s 48.2.

Where the 48.2 comes from

HVTrust dimensions vs the MCP Servers average

48.2 / 100 · 100.0% confidence

Jotform MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.5 / 25
3.3 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
0.9 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
15.8 / 20
3.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
3.5 / 20
4.1 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-03
Rank Moved
Rank rose 28 spots (#1071 → #1043)
2026-10-31
Rank Moved
Rank rose 33 spots (#1104 → #1071)
2026-10-30
Rank Moved
Rank rose 20 spots (#1124 → #1104)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/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.
Compare with another agent
View MCP Servers Report missing data
50.2
Activity sub-score · out of 100
#598
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 7 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
29
Forks
5
Last Push
2026-11-03
7 days ago
Commits (4 wk)
11
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #1061

Analysis

Activity Inputs

50.2 / 100
StarsRepository reach
8.9 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
13.5 / 25
CommunityFork signal
3.6 / 20

Common questions about Jotform MCP Server

Public trust evidence for Jotform MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Jotform MCP Server publish package provenance?
No published build provenance is currently detected for Jotform MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Jotform MCP Server have an OpenSSF Scorecard?
Jotform MCP Server has an OpenSSF Scorecard score of 3.4/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 Jotform MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
What license does Jotform MCP Server use?
Jotform MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Jotform MCP Server's commits signed?
64% of the last 100 commits to Jotform 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 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
N/A
No package source configured
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 Jotform 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-10-22
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-22
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-10-22
Mcp Status Changed
Detected MCP server support changed: implemented → none
2026-10-22
Activity Resumed
Activity resumed
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Jotform MCP Server?

For maintainers

HVTrust scores Jotform 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 19HVTrust 3MCP 2Surface 2Scorecard 1Delisted 1Listed 1Score 1Fresh 1Surface 1
2026-11-03
Rank Moved
Rank rose 28 spots (#1071 → #1043)
2026-10-31
Rank Moved
Rank rose 33 spots (#1104 → #1071)
2026-10-30
Rank Moved
Rank rose 20 spots (#1124 → #1104)
2026-10-22
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-22
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-10-22
Mcp Status Changed
Detected MCP server support changed: implemented → none
2026-10-22
Activity Resumed
Activity resumed
2026-10-22
Rank Moved
Rank rose 190 spots (#1302 → #1112)
2026-10-22
HVTrust Changed
HVTrust up 11.1pts (34.5 → 45.6)
2026-10-22
Activity Score Changed
Activity score up 36pts (12 → 49)
2026-10-09
Rank Moved
Rank dropped 10 spots (#1269 → #1279)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 100 spots (#1149 → #1249)
2026-09-23
HVTrust Changed
HVTrust up 13.9pts (20.6 → 34.5)
2026-09-22
Newly Listed
First tracked at rank #1149
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-08
Rank Moved
Rank dropped 11 spots (#1220 → #1231)
2026-09-07
Rank Moved
Rank dropped 13 spots (#1207 → #1220)
2026-09-06
Rank Moved
Rank dropped 18 spots (#1189 → #1207)
2026-09-05
Rank Moved
Rank dropped 32 spots (#1157 → #1189)
2026-09-04
Rank Moved
Rank dropped 14 spots (#1143 → #1157)
2026-09-03
Rank Moved
Rank dropped 44 spots (#1099 → #1143)
2026-09-02
Rank Moved
Rank dropped 45 spots (#1054 → #1099)
2026-09-01
Rank Moved
Rank dropped 37 spots (#1017 → #1054)
2026-08-31
Rank Moved
Rank dropped 34 spots (#983 → #1017)
2026-08-30
Rank Moved
Rank dropped 50 spots (#933 → #983)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.0/10
2026-08-29
Rank Moved
Rank rose 355 spots (#1288 → #933)
2026-08-29
HVTrust Changed
HVTrust up 19.4pts (15.1 → 34.5)
2026-08-26
Rank Moved
Rank dropped 18 spots (#1261 → #1279)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1231 → #1257)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 48.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/jotform-mcp-server.svg)](https://hvtracker.net/agents/jotform-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/jotform-mcp-server"><img src="https://hvtracker.net/badge/jotform-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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