updated 2026-11-10 04:07 UTC

Apideck Libraries MCP

Repository Website

MCP server for Apideck Unified APIs — Accounting, File Storage, HRIS, Vault, Proxy

MCP Servers Dockerfile Listed MIT

Is Apideck Libraries MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.3 / 10
Provenance None
Signed commits 0%
Last push 7d ago
Advisories None known
Compare Apideck Libraries MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Apideck Libraries MCP scores 53.4/100 (Grade C), ranked #902 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 4.3/10; recent commits are unsigned; no published advisory affects its latest release (@apideck/mcp); last pushed 2026-11-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Apideck Libraries 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Apideck Libraries 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.

  1. Source Unsigned

    github.com/apideck-libraries/mcp, MIT, last pushed 2026-11-03. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 9
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages Linked, not attested

    • npm @apideck/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.

  4. What you install today No known advisories

    Latest release checked: @apideck/mcp 0.28.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 4.7/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 Apideck Libraries 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.

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 Apideck Libraries MCP compares in MCP Servers

  1. #497 Stealth Browser MCP 53.5 +0.1
  2. #498 Licinexus MCP 53.4 ±0
  3. #499 Apideck Libraries MCP 53.4 this agent
  4. #500 fastctx 53.4 ±0
  5. #501 Serial MCP Server 53.4 ±0

Bars show each HVTrust score; the tick marks Apideck Libraries MCP’s 53.4.

Where the 53.4 comes from

HVTrust dimensions vs the MCP Servers average

53.4 / 100 · 100.0% confidence

Apideck Libraries MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.4 / 25
5.4 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
12.2 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
6.7 / 20
0.9 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-08
Rank Moved
Rank dropped 11 spots (#885 → #896)
2026-11-07
Rank Moved
Rank dropped 16 spots (#869 → #885)
2026-11-03
Rank Moved
Rank rose 10 spots (#876 → #866)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/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.
Compare with another agent
View MCP Servers Report missing data
46.4
Activity sub-score · out of 100
#499
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 7 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
21
Forks
3
Last Push
2026-11-03
7 days ago
Commits (4 wk)
7?
Downloads (7d)
417
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▼1
was #901

Analysis

Activity Inputs

46.4 / 100
StarsRepository reach
8.1 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
2.8 / 20

Common questions about Apideck Libraries MCP

Public trust evidence for Apideck Libraries MCP 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 Apideck Libraries MCP publish package provenance?
No published build provenance is currently detected for Apideck Libraries MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Apideck Libraries MCP have an OpenSSF Scorecard?
Apideck Libraries MCP has an OpenSSF Scorecard score of 4.3/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 Apideck Libraries MCP actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
What license does Apideck Libraries MCP use?
Apideck Libraries MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Apideck Libraries MCP's commits signed?
0% of the last 100 commits to Apideck Libraries MCP 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
Apideck Libraries MCP 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
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 Apideck Libraries 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.

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

Maintain Apideck Libraries MCP?

For maintainers

HVTrust scores Apideck Libraries 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 37HVTrust 3Grade 3Scorecard 1Delisted 1Listed 1MCP 1Score 1
2026-11-08
Rank Moved
Rank dropped 11 spots (#885 → #896)
2026-11-07
Rank Moved
Rank dropped 16 spots (#869 → #885)
2026-11-03
Rank Moved
Rank rose 10 spots (#876 → #866)
2026-10-28
Rank Moved
Rank dropped 11 spots (#872 → #883)
2026-10-25
Rank Moved
Rank dropped 10 spots (#856 → #866)
2026-10-22
Rank Moved
Rank rose 19 spots (#869 → #850)
2026-10-15
Rank Moved
Rank dropped 11 spots (#849 → #860)
2026-10-12
Rank Moved
Rank rose 15 spots (#859 → #844)
2026-10-09
Rank Moved
Rank dropped 11 spots (#837 → #848)
2026-10-05
Rank Moved
Rank rose 32 spots (#854 → #822)
2026-09-28
Rank Moved
Rank rose 23 spots (#855 → #832)
2026-09-27
Rank Moved
Rank rose 16 spots (#871 → #855)
2026-09-26
Rank Moved
Rank dropped 19 spots (#852 → #871)
2026-09-25
Grade Changed
Trust grade D → C
2026-09-25
Rank Moved
Rank rose 136 spots (#988 → #852)
2026-09-25
HVTrust Changed
HVTrust up 5.0pts (48.1 → 53.1)
2026-09-25
Activity Score Changed
Activity score up 12pts (30 → 42)
2026-09-24
Rank Moved
Rank dropped 24 spots (#964 → #988)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 144 spots (#1108 → #964)
2026-09-23
HVTrust Changed
HVTrust up 27.0pts (21.9 → 48.9)
2026-09-22
Newly Listed
First tracked at rank #1108
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 10 spots (#935 → #945)
2026-09-18
Rank Moved
Rank rose 10 spots (#947 → #937)
2026-09-13
Rank Moved
Rank dropped 11 spots (#928 → #939)
2026-09-12
Grade Changed
Trust grade C → D
2026-09-12
Rank Moved
Rank dropped 10 spots (#918 → #928)
2026-09-09
Rank Moved
Rank dropped 57 spots (#852 → #909)
2026-09-08
Rank Moved
Rank dropped 15 spots (#837 → #852)
2026-09-07
Rank Moved
Rank dropped 39 spots (#798 → #837)
2026-09-06
Rank Moved
Rank dropped 11 spots (#787 → #798)
2026-09-05
Rank Moved
Rank dropped 57 spots (#730 → #787)
2026-09-04
Rank Moved
Rank dropped 29 spots (#701 → #730)
2026-09-03
Rank Moved
Rank dropped 41 spots (#660 → #701)
2026-09-02
Rank Moved
Rank dropped 30 spots (#630 → #660)
2026-09-01
Scorecard Added
OSSF Scorecard: 4.7/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 451 spots (#1081 → #630)
2026-09-01
HVTrust Changed
HVTrust up 21.7pts (30.3 → 52.0)
2026-08-31
Rank Moved
Rank dropped 28 spots (#1053 → #1081)
2026-08-30
Rank Moved
Rank dropped 55 spots (#998 → #1053)
2026-08-29
Rank Moved
Rank dropped 48 spots (#950 → #998)
2026-08-28
Rank Moved
Rank dropped 35 spots (#915 → #950)
2026-08-27
Rank Moved
Rank dropped 26 spots (#889 → #915)
2026-08-26
Rank Moved
Rank dropped 117 spots (#772 → #889)
2026-08-18
Rank Moved
Rank rose 15 spots (#767 → #752)
2026-08-16
Rank Moved
Rank dropped 12 spots (#756 → #768)
GitHub → Website → npm: @apideck/mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 53.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/apideck-libraries-mcp.svg)](https://hvtracker.net/agents/apideck-libraries-mcp)
HTML:
<a href="https://hvtracker.net/agents/apideck-libraries-mcp"><img src="https://hvtracker.net/badge/apideck-libraries-mcp.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