Is Licinexus MCP safe to use?

Licinexus MCP has an HVTrust score of 56.1/100 (Grade C), ranked #748 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Licinexus MCP?

Licinexus MCP scores 56.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 78 GitHub stars and is categorized under MCP Servers.

Licinexus MCP

Licinexus/licinexus-mcp

MCP server for Brazilian public procurement data (PNCP + Receita Federal). Maintained by Licinexus.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 5.5 / 10

Provenance None

Signed commits 33%

Last push 18d ago

Compare Licinexus MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

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

How Licinexus MCP compares in MCP Servers

#413 Lumino MCP Server 56.1 ±0
#414 Opencage Geocoding MCP 56.1 ±0
#415 Licinexus MCP 56.1 this agent
#416 Paparats – Local Semantic Code Search MCP 56.1 ±0
#417 Apollo.io 56.1 ±0

Bars show each HVTrust score; the tick marks Licinexus MCP’s 56.1.

Where the 56.1 comes from

HVTrust dimensions vs the MCP Servers average

56.1 / 100 · 100.0% confidence

Licinexus MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.5 / 25

1.8 below 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.2 / 17

1.0 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

10.8 / 20

1.3 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.8 / 20

in line with 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-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 (#973 → #728)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/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 Get email alerts for Licinexus MCP View MCP Servers Report missing data

41.4

Activity sub-score · out of 100

#415

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-08

18 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼5

was #743

Analysis

Activity Inputs

41.4 / 100

StarsRepository reach

11.4 / 30

FreshnessLast push recency

22.5 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

33%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 9

CII-Best-Practices 0

Code-Review 1

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 2

Packaging -1

Pinned-Dependencies 4

SAST 9

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Licinexus MCP

Licinexus MCP 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 Licinexus MCP publish package provenance?

No published build provenance is currently detected for Licinexus 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 Licinexus MCP have an OpenSSF Scorecard?

Licinexus MCP has an OpenSSF Scorecard score of 5.5/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 Licinexus MCP actively maintained?

Maintained. Last push was 18 days ago.

What license does Licinexus MCP use?

Licinexus MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Licinexus MCP's commits signed?

32% of the last 100 commits to Licinexus 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

Licinexus MCP 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 Licinexus 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 Licinexus MCP?

For maintainers

HVTrust scores Licinexus 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

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 (#973 → #728)

2026-09-23

HVTrust Changed

HVTrust up 31.0pts (25.4 → 56.4)

2026-09-22

Newly Listed

First tracked at rank #973

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank rose 10 spots (#720 → #710)

2026-09-18

Rank Moved

Rank dropped 12 spots (#708 → #720)

2026-09-15

Rank Moved

Rank dropped 12 spots (#703 → #715)

2026-09-11

Rank Moved

Rank dropped 19 spots (#674 → #693)

2026-09-09

Rank Moved

Rank dropped 12 spots (#660 → #672)

2026-09-07

Rank Moved

Rank rose 30 spots (#681 → #651)

2026-09-06

Rank Moved

Rank dropped 14 spots (#667 → #681)

2026-09-05

Rank Moved

Rank dropped 79 spots (#588 → #667)

2026-09-04

Rank Moved

Rank dropped 18 spots (#570 → #588)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 463 spots (#1033 → #570)

2026-09-03

HVTrust Changed

HVTrust up 18.4pts (37.4 → 55.8)

2026-09-02

Rank Moved

Rank dropped 54 spots (#979 → #1033)

2026-09-01

Rank Moved

Rank dropped 41 spots (#938 → #979)

2026-08-31

Scorecard Added

OSSF Scorecard: 5.8/10

2026-08-31

Rank Moved

Rank rose 269 spots (#1207 → #938)

2026-08-31

HVTrust Changed

HVTrust up 17.6pts (20.2 → 37.8)

2026-08-30

Rank Moved

Rank dropped 25 spots (#1182 → #1207)

2026-08-29

Rank Moved

Rank dropped 25 spots (#1157 → #1182)

2026-08-28

Rank Moved

Rank dropped 21 spots (#1136 → #1157)

2026-08-27

Rank Moved

Rank dropped 19 spots (#1117 → #1136)

2026-08-26

Rank Moved

Rank dropped 62 spots (#1055 → #1117)

2026-08-19

Rank Moved

Rank dropped 12 spots (#1043 → #1055)

2026-08-17

Rank Moved

Rank rose 16 spots (#1062 → #1046)

2026-08-16

Rank Moved

Rank dropped 37 spots (#1025 → #1062)

2026-08-12

Rank Moved

Rank rose 10 spots (#1027 → #1017)

2026-08-10

Rank Moved

Rank dropped 60 spots (#965 → #1025)

2026-08-09

Activity Score Changed

Activity score down 8pts (50 → 43)

2026-08-08

Newly Listed

First tracked at rank #938

GitHub → npm: @licinexusbr/mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/licinexus-mcp.svg)](https://hvtracker.net/agents/licinexus-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/licinexus-mcp"><img src="https://hvtracker.net/badge/licinexus-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.3 · Raw JSON