updated 2026-11-10 04:07 UTC

Pulsemcp MCP Servers

Repository

MCP (Model Context Protocol) Servers authored and maintained by the PulseMCP team. We build reliable servers thoughtfully designed specifically for MCP Client-powered workflows.

MCP Servers TypeScript Listed MIT

Is Pulsemcp MCP Servers safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.6 / 10
Provenance None
Signed commits 100%
Last push 32d ago
Compare Pulsemcp MCP Servers

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Pulsemcp MCP Servers scores 50.4/100 (Grade C), ranked #994 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 3.6/10; 100% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pulsemcp MCP Servers 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 Pulsemcp MCP Servers 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 Signed

    github.com/pulsemcp/mcp-servers, MIT, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Weak

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

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

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 4.3/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 Pulsemcp MCP Servers’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 Pulsemcp MCP Servers compares in MCP Servers

  1. #558 MacOS MCP 50.7 +0.3
  2. #559 SearXNG HTTP MCP 50.6 +0.2
  3. #560 Pulsemcp MCP Servers 50.4 this agent
  4. #561 MCP Server for Binge-watch 50.4 ±0
  5. #562 Word MCP Live 50.3 −0.1

Bars show each HVTrust score; the tick marks Pulsemcp MCP Servers’s 50.4.

Where the 50.4 comes from

HVTrust dimensions vs the MCP Servers average

50.4 / 100 · 100.0% confidence

Pulsemcp MCP Servers MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.5 / 25
1.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.6 / 17
0.7 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
9.9 / 20
2.3 below avg 12.2
AdoptionLog-scaled stars · package downloads
7.6 / 20
in line with avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-22
Rank Moved
Rank dropped 10 spots (#975 → #985)
2026-10-16
Rank Moved
Rank dropped 10 spots (#946 → #956)
2026-10-12
Rank Moved
Rank dropped 11 spots (#917 → #928)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/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.
Refresh maintenance signals The repo was last pushed 32 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
37.0
Activity sub-score · out of 100
#560
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 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-11-10 04:07 UTC · Repo last pushed 32 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
81
Forks
10
Last Push
2026-10-09
32 days ago
Commits (4 wk)
0
Downloads (7d)
172
npm
HN mentions (30d)
—
Open Issues
27
Rank Change
▲3
was #997

Analysis

Activity Inputs

37.0 / 100
StarsRepository reach
11.5 / 30
FreshnessLast push recency
20.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.8 / 20

Common questions about Pulsemcp MCP Servers

Public trust evidence for Pulsemcp MCP Servers 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 Pulsemcp MCP Servers publish package provenance?
No published build provenance is currently detected for Pulsemcp MCP Servers. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Pulsemcp MCP Servers have an OpenSSF Scorecard?
Pulsemcp MCP Servers has an OpenSSF Scorecard score of 3.6/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 Pulsemcp MCP Servers actively maintained?
Slowing down. Last push was 32 days ago — keep an eye on whether activity resumes.
What license does Pulsemcp MCP Servers use?
Pulsemcp MCP Servers ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Pulsemcp MCP Servers's commits signed?
100% of the last 100 commits to Pulsemcp MCP Servers 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
Pulsemcp MCP Servers appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Pulsemcp MCP Servers'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 Pulsemcp MCP Servers?

For maintainers

HVTrust scores Pulsemcp MCP Servers 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 23HVTrust 4Grade 4Score 2Scorecard 1Delisted 1Listed 1MCP 1
2026-10-22
Rank Moved
Rank dropped 10 spots (#975 → #985)
2026-10-16
Rank Moved
Rank dropped 10 spots (#946 → #956)
2026-10-12
Rank Moved
Rank dropped 11 spots (#917 → #928)
2026-10-09
Grade Changed
Trust grade D → C
2026-10-09
Rank Moved
Rank rose 69 spots (#973 → #904)
2026-10-09
HVTrust Changed
HVTrust up 3.0pts (49.4 → 52.4)
2026-10-09
Activity Score Changed
Activity score up 5pts (36 → 41)
2026-10-05
Grade Changed
Trust grade C → D
2026-10-05
Rank Moved
Rank dropped 41 spots (#924 → #965)
2026-09-30
Rank Moved
Rank dropped 15 spots (#900 → #915)
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 184 spots (#1031 → #847)
2026-09-23
HVTrust Changed
HVTrust up 28.9pts (24.1 → 53.0)
2026-09-22
Newly Listed
First tracked at rank #1031
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 16 spots (#786 → #802)
2026-09-09
Rank Moved
Rank dropped 11 spots (#774 → #785)
2026-09-08
Rank Moved
Rank dropped 13 spots (#761 → #774)
2026-09-07
Rank Moved
Rank dropped 30 spots (#731 → #761)
2026-09-06
Rank Moved
Rank dropped 12 spots (#719 → #731)
2026-09-05
Rank Moved
Rank dropped 74 spots (#645 → #719)
2026-09-04
Rank Moved
Rank dropped 23 spots (#622 → #645)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 464 spots (#1086 → #622)
2026-09-03
HVTrust Changed
HVTrust up 19.3pts (35.0 → 54.3)
2026-09-02
Rank Moved
Rank dropped 48 spots (#1038 → #1086)
2026-09-01
Rank Moved
Rank dropped 38 spots (#1000 → #1038)
2026-08-31
Rank Moved
Rank dropped 30 spots (#970 → #1000)
2026-08-30
Scorecard Added
OSSF Scorecard: 4.3/10
2026-08-30
Rank Moved
Rank rose 306 spots (#1276 → #970)
2026-08-30
HVTrust Changed
HVTrust up 18.7pts (16.4 → 35.1)
2026-08-30
Activity Score Changed
Activity score up 8pts (37 → 45)
2026-08-29
Rank Moved
Rank dropped 11 spots (#1265 → #1276)
2026-08-26
Rank Moved
Rank dropped 27 spots (#1223 → #1250)
2026-08-20
Rank Moved
Rank dropped 16 spots (#1204 → #1220)
2026-08-16
Rank Moved
Rank dropped 27 spots (#1180 → #1207)
GitHub → npm: @pulsemcp/pulse-fetch

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

Data sources
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